Re: dell laptop cannot access super-key.

[angelomolina--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>]

Mar 14, 2022, 15:52 by tomas@tuxteam.de:

> On Mon, Mar 14, 2022 at 04:04:49PM +0100, Christopher Dimech wrote:
>
>> > Sent: Monday, March 14, 2022 at 5:19 PM
>> > From: "hw" <hw@adminart.net>
>> > To: help-gnu-emacs@gnu.org
>> > Subject: Re: dell laptop cannot access super-key.
>> >
>> >
>> > Maybe this is a BIOS setting which makes it so that the key
>> > you are trying to use is used for a FN key like some laptops
>> > have, or disabled for some reason.
>>
>> It could well be.  Dell could have done this from reading
>>
>> https://www.dell.com/support/kbdoc/en-us/000116152/how-to-enable-the-ubuntu-super-key-on-dell-oem-ubuntu-installations
>>
>> One can set the Keyboard Model to "Generic 104-key PC" using "Keyboard Preferences".
>> This has the Super-Key in place of the Win-Key. But the Win-Key does not seen to
>> communicate the presses when using xev.
>>
>> The Fn-Key is on another key, next to the Win-Key, making me unlikely to think
>> that it is being used as FN.
>>
>
> FWIW, my installation generates X events also for the Fn key:
>

I do not get X events for Fn-Key either.  Am starting to think it is a restriction from Dell.
Could anybody confirm?



>  KeyPress event, serial 36, synthetic NO, window 0x2600001,
>  root 0x167, subw 0x0, time 18886981, (-13,41), root:(437,157),
>  state 0x0, keycode 151 (keysym 0x1008ff2b, XF86WakeUp), same_screen YES,
>  XLookupString gives 0 bytes: 
>  XmbLookupString gives 0 bytes: 
>  XFilterEvent returns: False
>  
>  KeyRelease event, serial 36, synthetic NO, window 0x2600001,
>  root 0x167, subw 0x0, time 18886991, (-13,41), root:(437,157),
>  state 0x0, keycode 151 (keysym 0x1008ff2b, XF86WakeUp), same_screen YES,
>  XLookupString gives 0 bytes: 
>  XFilterEvent returns: False
>
> YMMV.
>
> Cheers
> -- 
> t
>