GNU bug report logs - #53452
29.0.50; C-<arrow> selection broken by translate-upper-case-key-bindings

Previous Next

Full log

Message #38 received at 53452 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: spacibba <at> aol.com, 53452 <at> debbugs.gnu.org
Subject: Re: bug#53452: 29.0.50; C-<arrow> selection broken by
 translate-upper-case-key-bindings
Date: Tue, 25 Jan 2022 14:45:09 +0200

> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: spacibba <at> aol.com,  53452 <at> debbugs.gnu.org
> Date: Tue, 25 Jan 2022 13:37:13 +0100
> 
> >>>>> On Tue, 25 Jan 2022 14:29:56 +0200, Eli Zaretskii <eliz <at> gnu.org> said:
> 
>     >> From: Robert Pluim <rpluim <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.