Re: [dev] [st] Unable to map Ctrl+$NUMBER

From: Gary Allen Vollink <gary_AT_vollink.com>
Date: Mon, 9 Oct 2017 21:22:30 -0400

Hi Eric,

This might not help at all, but ... without any modifications at all,
Ctrl + 1 prints a 1, but interestingly ... Ctrl + 2 through 9 are
fully unresponsive (no input). Seems like something else is up here.

That said, I still was unable to get XK_2 to do anything special on my
terminal either. I didn't put a huge amount of time, but I'm hoping
my observation might help you trace this.

Thanks,
Gary

On Mon, Oct 9, 2017 at 1:32 PM, Eric Pruitt <eric.pruitt_AT_gmail.com> wrote:
> I would like to create custom mappings for pressing Control with a
> digit. I added this binding for Ctrl+1 to the top of the "key" array:
>
> /* keysm mask string appkey appcursor crlf */
> { XK_1, ControlMask, "\033OP", 0, 0, 0 },
>
> When I press Ctrl+1, a "1" is printed instead of the escape sequence. I
> added a similar mapping to the "shortcuts" array:
>
> /* mask mask string argument */
> { ControlMask, ControlMask, iso14755, {.i = 0} }
>
> When I press Ctrl+1 after making that change, the iso14755 function is
> executed as expected. I looked at the code that's responsible for
> handling key presses in both arrays, but it's not clear to me exactly
> what the problem is. Is there something wrong with the way I'm trying to
> map Ctrl+1 or is this a bug of some sort?
>
> Thanks,
> Eric
>
Received on Tue Oct 10 2017 - 03:22:30 CEST