From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: spacibba@aol.com, 53452@debbugs.gnu.org
Subject: bug#53452: 29.0.50; C-<arrow> selection broken by translate-upper-case-key-bindings
Date: Tue, 25 Jan 2022 11:19:33 +0100 [thread overview]
Message-ID: <87czkgi0cq.fsf@gmail.com> (raw)
In-Reply-To: <83r18xjlrj.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 24 Jan 2022 15:39:28 +0200")
>>>>> On Mon, 24 Jan 2022 15:39:28 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> Why not?
Eli> Because people will probably want it applied to any key. There's
Eli> nothing special about letters, except that "upper-case" implicitly
Eli> refers to letters.
Let's start again:
Currently, S-<right> produces S-<right>, but is translated to <right>,
and C-S-a is translated to C-a
If you set translate-upper-case-key-bindings to nil, then S-<right>
produces S-<right>, and C-S-a produces C-S-a
So the effect is as if the option were called
'translate-shift-bindings', but that effect is not called out
anywhere.
So either we fix the behaviour, or the documentation. Would it be that
hard to restrict this to something like [a-z] or !function key? Or we
could always add yet-another-user-option.
Robert
--
next prev parent reply other threads:[~2022-01-25 10:19 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czkgi0cq.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 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.