unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: help-gnu-emacs@gnu.org, kai@emptydomain.de,
	bug-gnu-emacs@gnu.org, emacs-devel@gnu.org
Subject: Re: read-key-sequence(-vector) on Shift left/right gives[left]/[right], not [S-left]/[S-right] ?
Date: Tue, 07 Sep 2004 20:22:05 -0400	[thread overview]
Message-ID: <E1C4qDt-0004H4-6U@fencepost.gnu.org> (raw)
In-Reply-To: <FDELKNEBLPKKDCEBEJCBCEECCHAA.drew.adams@oracle.com>

    2) Shouldn't it at least be documented in the doc strings of
    read-key-sequence and read-key-sequence-vector?

It already is:

The third (optional) arg DONT-DOWNCASE-LAST, if non-nil, means do not
convert the last event to lower case.  (Normally any upper case event
is converted to lower case if the original event is undefined and the lower
case equivalent is defined.)

    6) This is inconsistent (also) with read-event, which DTRT in this regard.

They are different for good reason.

    7) If this is for the convenience of being able to use the keys with
    caps-lock on, as the manual says, then why not just pre-bind shift-* to the
    same binding as * (*= any key)?

That would be obviously inconvenient if the user rebinds such a key.

  parent reply	other threads:[~2004-09-08  0:22 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
2004-09-08  0:22     ` Richard Stallman [this message]
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=E1C4qDt-0004H4-6U@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=kai@emptydomain.de \
    /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).