all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>, Vladimir Sedach <vas@oneofus.la>
Cc: help-gnu-emacs@gnu.org
Subject: RE: Modifier Keys and the Archaic Meta Key
Date: Sun, 25 Oct 2020 14:41:09 -0700 (PDT)	[thread overview]
Message-ID: <92845a2c-7726-4bce-9411-0b0585c509b6@default> (raw)
In-Reply-To: <trinity-4ca4287d-2b5d-43b1-8d3d-f4e60bb33829-1603661533963@3c-app-mailcom-bs14>

There's nothing wrong with discussing this in this
mailing list, AFAIK.  But this list is more for
questions from Emacs users.

If you'd like to affect Emacs development or engage
more users who are interested in Emacs development,
then the mailing list emacs-devel@gnu.org might be
more appropriate.

(In any case, please don't send to more than one list.)



  reply	other threads:[~2020-10-25 21:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-25 10:05 Modifier Keys and the Archaic Meta Key Christopher Dimech
2020-10-25 11:35 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-10-25 12:49   ` Christopher Dimech
2020-10-25 19:57     ` Francis Belliveau
2020-10-25 21:07       ` Christopher Dimech
2020-10-26 14:37         ` Modifier Keys and the Archaic Meta Key, term keyboard becoming archaic soon Jean Louis
2020-10-26 16:14           ` Christopher Dimech
2020-10-25 12:45 ` Modifier Keys and the Archaic Meta Key Jean Louis
2020-10-25 13:46   ` Christopher Dimech
2020-10-25 20:12     ` Francis Belliveau
2020-10-25 21:30       ` Christopher Dimech
2020-11-08 22:15         ` pillule
2020-11-14 21:51         ` pillule
2020-10-25 20:40 ` Vladimir Sedach
2020-10-25 21:32   ` Christopher Dimech
2020-10-25 21:41     ` Drew Adams [this message]
2020-10-25 21:53       ` Christopher Dimech

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=92845a2c-7726-4bce-9411-0b0585c509b6@default \
    --to=drew.adams@oracle.com \
    --cc=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=vas@oneofus.la \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.