Re: [kbd] ctrl arrow keys not working in linux virtual consoles

Re: [kbd] ctrl arrow keys not working in linux virtual consoles

[Alexey Gladkov]

----- Forwarded message -----

Date: Fri, 11 Nov 2016 13:00:28 +0100
From: Benoît <benoit@neviani.fr>
Subject: Re: ctrl arrow keys not working in linux virtual consoles

Hi Ken and thanks for your reply!

Thanks to your suggestion I found that the problem is not coming from kbd...

In a normal virtual console (linux VT) it is working well (your â test) but I
am using kmscon and now I know the issue is coming from there...

I have tried to import the keymap but it is not working as they use XKB format
so I have to deal with it and I have no clue how, example of the format :

key <AE01>  { [ ampersand,          1,  onesuperior,   exclamdown ] };
key <AE02>  { [    eacute,          2,   asciitilde,    oneeighth ] };
key <AE03>  { [  quotedbl,          3,   numbersign,     sterling ] };

On Thu, Nov 10, 2016 at 08:13:16PM +0100, Benoît wrote:
> Hi,
> 
> Trying my luck here as I don't find a solution after mutiple tries.
> I posted my issue in archlinux forum for reference :
> 
> https://bbs.archlinux.org/viewtopic.php?id=219078
> 
> To summarize, I am unable to make a ctrl arrow combination recognized and
> work under virtual consoles (working in X).
> 
> Pushing ctrl + arrow is giving the same hex as pushing only arrow key.
> I am thinking about remapping keys and use a customizable .map for my
> virtual console but I don't see how to get the right code to put into my
> .map
> 
> I am under an azerty keyboard.
> I would very appreciate if you have any idea :)
> 
> Many thanks
> 

If by 'arrow' you mean 'up arrow', on my keyboard that is keycode
103.  Use 'showkey' to confirm the code in your setup.

Then add a line to your map, something like

       control keycode   103 = acircumflex

and when that gives you an â you will know it works.  Then change it
to whichever key or glyph you wish.

For some reason, the control keycode values in the map from which I
started my own changes are all inset like that after the
corresponding entry - I assume you can just add the control entry
after any included files have been mentioned (in the uk map I used,
the up arrow is only mentioned in one of the included files).

But, if you are starting from fr-latin1 or fr-latin9 there are
already entries for 'plain' keycode 103 and for some neighbouring
codes which show how shift, alt can be given on separate lines (or
commented with '#').

But I can't help with decoding the escape sequences you showed in
that Arch posting.

HTH

ĸen
-- 
`I shall take my mountains', said Lu-Tze. `The climate will be good
for them.'     -- Small Gods
-- 
Benoit


----- End forwarded message -----

-- 
Rgrds, legion