From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
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 14:45:09 +0200 [thread overview]
Message-ID: <83h79shtm2.fsf@gnu.org> (raw)
In-Reply-To: <878rv4htza.fsf@gmail.com> (message from Robert Pluim on Tue, 25 Jan 2022 13:37:13 +0100)
> From: Robert Pluim <rpluim@gmail.com>
> Cc: spacibba@aol.com, 53452@debbugs.gnu.org
> Date: Tue, 25 Jan 2022 13:37:13 +0100
>
> >>>>> On Tue, 25 Jan 2022 14:29:56 +0200, Eli Zaretskii <eliz@gnu.org> said:
>
> >> From: Robert Pluim <rpluim@gmail.com>
> >> 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.
>
> Eli> My point was that the behavior is probably okay, and the documentation
> Eli> should be amended if it could confuse.
>
> Itʼs only ok if weʼre ok with shift-selection being broken by it. Are
> we?
Like I said: I don't see how shift-selection could NOT be broken by
disabling shift-translation, because it DEPENDS on it.
prev parent reply other threads:[~2022-01-25 12:45 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
2022-01-25 12:29 ` Eli Zaretskii
2022-01-25 12:37 ` Robert Pluim
2022-01-25 12:45 ` Eli Zaretskii [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=83h79shtm2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53452@debbugs.gnu.org \
--cc=rpluim@gmail.com \
--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).