> So there's no way to work around this?
I can think of three:
- You have two Shift keys and most likely two Mod4 keys. This gives you
three more possibilities to enter the same combination. If any of
this combinations works and is sufficiently convenient to type, that
would be the
also sprach wetts...@gmail.com [2016-09-29 21:00 +0200]:
> I do not know, but I do not see the benefit of doing that. It
> certainly would not fix your problem, which I still think is
> hardware.
I think you are right. I just noticed that this only happens with my
USB
> Long story short: do you see any chance in making this bit of
> legacy (nostalgia?) code configurable, or remove it altogether?
I do not know, but I do not see the benefit of doing that. It certainly
would not fix your problem, which I still think is hardware.
Andreas
also sprach wetts...@gmail.com [2016-09-12 18:01 +0200]:
> > And moments after clicking send, I realized this is really just hardcoding
> > US keyboard layout & ASCII encoding - Shift-2 is '@' and Ctrl-@ is '\0'.
>
> Oh, yes. And Ctrl+3-7 get mapped to 0x1b-0x1f, the control
> And moments after clicking send, I realized this is really just hardcoding
> US keyboard layout & ASCII encoding - Shift-2 is '@' and Ctrl-@ is '\0'.
Oh, yes. And Ctrl+3-7 get mapped to 0x1b-0x1f, the control codes beyond
Ctrl-Z. Ctrl+8 becomes 0x7f, that is, ASCII DEL. So the full ASCII
On 09/12/16 08:40 AM, Alan Coopersmith wrote:
So Control-Shift-2 maps to the NULL character because someone three decades
ago thought it useful to emulate a text terminal popular in that decade.
And moments after clicking send, I realized this is really just hardcoding
US keyboard layout &
On 09/12/16 08:25 AM, wetts...@gmail.com wrote:
Do you have any idea what might be going on?
In libX11, file KeyBind.c, function _XTranslateKeySym, there is the
following piece of code:
/* only apply Control key if it makes sense, else ignore it */
if (modifiers & ControlMask) {