From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ergus <spacibba@aol.com>, 53452@debbugs.gnu.org
Subject: bug#53452: 29.0.50; C-<arrow> selection broken by translate-upper-case-key-bindings
Date: Mon, 24 Jan 2022 11:54:19 +0100 [thread overview]
Message-ID: <87czkhjtes.fsf@gmail.com> (raw)
In-Reply-To: <834k5vmvf0.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Jan 2022 21:18:11 +0200")
>>>>> On Sat, 22 Jan 2022 21:18:11 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> Date: Sat, 22 Jan 2022 19:26:35 +0100
>> From: Ergus via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> When translate-upper-case-key-bindings is nil; the shift-arrow selection
>> does not work
>>
>> emacs -Q
>> M-: (setq translate-upper-case-key-bindings nil)
>> S-<right> // says it is not bound... somehow expected.
>>
>> M-: (keymap-global-set "S-<right>" #'right-char)
>> S-<right> // Now moves point but with no selection
>>
>> I don't know where/how emacs recognizes the Shift in this case, but
>> somehow it is not working
Eli> It sounds like it cannot work in that case, because shift-select
Eli> _requires_ that a key was shift-translated, and setting
Eli> translate-upper-case-key-bindings to nil disables that translation.
The docstring says:
"If non-nil, interpret upper case keys as lower case (when applicable)."
which strongly implies that this only applies to letters, not keys
like <right>
Robert
--
next prev parent reply other threads:[~2022-01-24 10:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220122182635.hi7i2alow4ishyz5.ref@Ergus>
2022-01-22 18:26 ` bug#53452: 29.0.50; C-<arrow> selection broken by translate-upper-case-key-bindings Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 19:18 ` Eli Zaretskii
2022-01-24 10:54 ` Robert Pluim [this message]
2022-01-24 12:38 ` Eli Zaretskii
2022-01-24 13:19 ` Robert Pluim
2022-01-24 12:40 ` Eli Zaretskii
2022-01-24 13:21 ` Robert Pluim
2022-01-24 13:39 ` Eli Zaretskii
2022-01-25 10:19 ` Robert Pluim
2022-01-25 12:29 ` Eli Zaretskii
2022-01-25 12:37 ` Robert Pluim
2022-01-25 12:45 ` Eli Zaretskii
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=87czkhjtes.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=53452@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=spacibba@aol.com \
/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).