From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: dell laptop cannot access super-key.
Date: Mon, 14 Mar 2022 16:52:55 +0100 [thread overview]
Message-ID: <Yi9k13W55MU+Uqio@tuxteam.de> (raw)
In-Reply-To: <trinity-b380040f-a058-474a-851c-097b8343bd0c-1647270289084@3c-app-mailcom-bs13>
[-- Attachment #1: Type: text/plain, Size: 1651 bytes --]
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:
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-03-14 15:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 21:11 dell laptop cannot access super-key goncholden via Users list for the GNU Emacs text editor
2022-03-12 0:19 ` Po Lu
2022-03-12 0:26 ` goncholden
2022-03-12 0:49 ` Po Lu
2022-03-12 11:22 ` goncholden
2022-03-12 16:56 ` goncholden
2022-03-12 17:23 ` goncholden
2022-03-13 0:16 ` Po Lu
2022-03-13 0:47 ` goncholden
2022-03-13 2:18 ` Po Lu
2022-03-13 11:58 ` Eric S Fraga
2022-03-13 12:24 ` goncholden
2022-03-13 18:58 ` Christopher Dimech
2022-03-13 19:02 ` Fw: " Christopher Dimech
2022-03-13 21:55 ` Christopher Dimech
2022-03-14 0:59 ` goncholden
2022-03-14 5:19 ` hw
2022-03-14 15:04 ` Christopher Dimech
2022-03-14 15:52 ` tomas [this message]
2022-03-14 17:14 ` angelomolina--- via Users list for the GNU Emacs text editor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yi9k13W55MU+Uqio@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.