Subject: bug#53452: 29.0.50; C-<arrow> selection broken by translate-upper-case-key-bindings

From: Eli Zaretskii <[email-masked]>
Date: Tue, 25 Jan 2022 14:45:09 +0200

> From: Robert Pluim <[email-masked]>
> Cc: [email-masked],  [email-masked]
> Date: Tue, 25 Jan 2022 13:37:13 +0100
> 
> >>>>> On Tue, 25 Jan 2022 14:29:56 +0200, Eli Zaretskii <[email-masked]> said:
> 
>     >> From: Robert Pluim <[email-masked]>
>     >> 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.