From: "Drew Adams" <drew.adams@oracle.com>
Cc: help-gnu-emacs@gnu.org, Kai Grossjohann <kai@emptydomain.de>,
bug-gnu-emacs@gnu.org, rms@gnu.org,
Emacs-Devel <emacs-devel@gnu.org>
Subject: RE: read-key-sequence(-vector) on Shift left/right gives[left]/[right], not [S-left]/[S-right] ?
Date: Tue, 7 Sep 2004 08:47:07 -0700 [thread overview]
Message-ID: <FDELKNEBLPKKDCEBEJCBGEEDCHAA.drew.adams@oracle.com> (raw)
In-Reply-To: <m1r7pe16wg.fsf-monnier+emacs@gnu.org>
From: Stefan
> > Shouldn't code be able to read user input
> > without paying attention to key bindings?
> When do you stop? After one key, two keys, three?
Point taken.
What I really meant was wrt dropping the Shift modifier. Read-key-* has no
trouble knowing to stop after one key, if that key is undefined. For
example, if C-M-+ is undefined, it returns this: [-67108821]; it doesn't ask
itself when to stop.
Otherwise (a key sequence is defined), it continues to read until it gets
the complete key sequence. I would expect it to have such behavior all the
time, and not make an exception of Shift. That's all.
IMO:
- read-key-* should not drop the Shift modifier: if Shift-* is undefined
and * is defined, it should act as it does with any other undefined key
sequence (return Shift-*), instead of returning *
- if read-key-* does drop the Shift modifier, then this should be
documented
- read-key-* should in any case optionally be able to not drop the Shift
modifier
Drew
next prev parent reply other threads:[~2004-09-07 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-07 0:02 read-key-sequence(-vector) on Shift left/right gives [left]/[right], not [S-left]/[S-right] ? Drew Adams
2004-09-07 11:55 ` Kai Grossjohann
2004-09-07 14:32 ` read-key-sequence(-vector) on Shift left/right gives[left]/[right], " Drew Adams
2004-09-07 14:47 ` Stefan
2004-09-07 15:47 ` Drew Adams [this message]
2004-09-08 0:22 ` Richard Stallman
2004-09-08 0:47 ` Drew Adams
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=FDELKNEBLPKKDCEBEJCBGEEDCHAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=help-gnu-emacs@gnu.org \
--cc=kai@emptydomain.de \
--cc=rms@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).