From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Joe Wells <jbw@macs.hw.ac.uk>, 631@emacsbugs.donarmstrong.com
Cc: xah lee <xah@xahlee.org>, Yavor Doganov <yavor@gnu.org>
Subject: bug#631: the M- notation suggestion
Date: Mon, 04 Aug 2008 13:38:10 +0200 [thread overview]
Message-ID: <4896EA22.1050407@gmail.com> (raw)
In-Reply-To: <86ej55ujaf.fsf@macs.hw.ac.uk>
Joe Wells wrote:
> xah lee <xah@xahlee.org> writes:
>
>> The proposed change doesn't actually effect elisp code. It is primarly
>> esthetic in nature.
>
> This is not true. There are many places in the Emacs Lisp code which
> recognize the M- and C- notation.
Thanks Joe for this list.
I am thinking about the possibility to just change what is shown in
menus and help texts (see my earlier reply to Xah's bug report). Such a
change would of course be optional, but might help new users.
With such a change there would of course be a steop for new users when
they are just frustrated because they do not understand how to do key
bindings, "why does not (kbd "Alt-<down>") work?", etc.
And the manual would probably better still use the current notation
(with a note about the new notation) because it is static and is read on
different platform. So everything would not be better, but the initial
treshold would probably be lower.
Can you see any technical trouble with the changes I am suggesting could
be done?
> First, there is the read syntax (I'm using Emacs 22.1):
>
> ?\M-A ⇒ 134217793
> ?\M-\C-b ⇒ 134217730
>
> "\M-A" ⇒ "\301" (yes, this is a bit different behavior for M-A)
>
> Then, there is the convention of making symbol names with prefixes for
> use in key bindings:
>
> M-f3
> M-mouse-1
> M-drag-mouse-2
> M-double-mouse-2
>
> Then, there is the lovely kbd macro for use in key bindings:
>
> (kbd "C-M-<down>") ⇒ [C-M-down]
>
> Then, there is the use of the M- and C- notation by edit-kbd-macro.
>
> Then, there are the key-description, single-key-description, and
> read-kbd-macro functions:
>
> (key-description [?\M-3 delete]) ⇒ "M-3 <delete>"
>
> There is also the text-char-description function.
>
prev parent reply other threads:[~2008-08-04 11:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 8:49 bug#631: the M- notation suggestion xah lee
2008-07-31 1:59 ` Richard M Stallman
2008-07-31 2:53 ` xah lee
2008-07-31 22:01 ` Richard M Stallman
2008-08-01 2:10 ` xah lee
2008-08-01 6:53 ` xah lee
2008-07-31 22:01 ` Richard M Stallman
2008-08-01 2:07 ` xah lee
2008-07-31 17:30 ` Lennart Borgman (gmail)
2008-08-01 6:39 ` Yavor Doganov
2008-08-01 7:42 ` xah lee
2008-08-01 8:37 ` Lennart Borgman (gmail)
[not found] ` <mailman.15692.1217578047.18990.bug-gnu-emacs@gnu.org>
2008-08-04 11:11 ` Joe Wells
2008-08-04 11:33 ` xah lee
2008-08-04 11:38 ` Lennart Borgman (gmail) [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4896EA22.1050407@gmail.com \
--to=lennart.borgman@gmail.com \
--cc=631@emacsbugs.donarmstrong.com \
--cc=jbw@macs.hw.ac.uk \
--cc=xah@xahlee.org \
--cc=yavor@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).