[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] input: allow distinguishing shifted from unshifted Meta keys
From: |
Brand Huntsman |
Subject: |
Re: [PATCH] input: allow distinguishing shifted from unshifted Meta keystrokes |
Date: |
Tue, 10 Dec 2019 17:36:39 -0700 |
On Mon, 9 Dec 2019 20:01:21 +0100
Benno Schulenberg <address@hidden> wrote:
> When the new option 'splitmeta' is set, nano will differentiate
> between Meta+letter and Shift+Meta+letter. In other words, typing
> Alt+a will do something else than typing Alt+A, and binding M-a will
> be different from binding M-A.
I don't agree with adding an option that requires changing all existing meta
binds to lowercase before adding shifted binds. The patch I've been using for a
while adds an S modifier to bind shifted keys, M-S-A is shifted M-A.
Both patches have a couple issues which is why I never released my patch.
Capslock works fine in a linux VT but all binds are flipped in urxvt and xterm.
Vim has the same issue so not a big deal. The other problem is that functions
in implants can "see" the shift key in a linux VT. This is already a problem
with shifted meta punctuation such as M-$.
bind M-$ "XXX{verbatim END key}" main
The XXX is not highlighted, but everything to end of line is. This doesn't
happen when binding the "end" function to M-$.
refactor-key-bind-parsing-and-support-meta-shift-keys.patch
Description: Text Data