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

Previous Next

Full log

View this message in rfc822 format

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

>>>>> On Mon, 24 Jan 2022 14:38:39 +0200, Eli Zaretskii <eliz <at> gnu.org> said:

    >> From: Robert Pluim <rpluim <at> gmail.com>
    >> Cc: Ergus <spacibba <at> aol.com>,  53452 <at> debbugs.gnu.org
    >> Date: Mon, 24 Jan 2022 11:54:19 +0100
    >> 
    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>

    Eli> That's a wrong impression, the translation applies to all the keys.

Yes, it does, but itʼs unexpected (to me at least), that setting
`translate-upper-case-key-bindings' to nil has the effect of disabling
that translation. Iʼd expect to see that side effect described in the
docstring, but that only talks about upper<->lower case mapping.

Robert
-- 

Previous Next

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