From: goncholden <goncholden@protonmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: goncholden via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: dell laptop cannot access super-key.
Date: Sat, 12 Mar 2022 00:26:08 +0000 [thread overview]
Message-ID: <OBa-CgsrfFC44EGpl3QZ-DsGU-lDCPSQ4GetGZ5LpxcTfF2MdzwZK92wynt8cAB0D-d5twg9S2yzRMeBnA8JYxx-QOLFa2Z5oxJ_TcCm0Kk=@protonmail.com> (raw)
In-Reply-To: <87y21gxbsb.fsf@yahoo.com>
------- Original Message -------
On Saturday, March 12th, 2022 at 12:19 AM, Po Lu <luangruo@yahoo.com> wrote:
> goncholden via Users list for the GNU Emacs text editor
> help-gnu-emacs@gnu.org writes:
>
> > Have been using a dell laptop and found out that I cannot access the
> > Super-Key. Wanted to do a key remapping so that I set the position of
> > the Super-Key as tho Alt-Key (Meta-Key).
>
> Please show the output of the command `xmodmap' run without any
> arguments. Thanks.
This is what I get
xmodmap
xmodmap: up to 4 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x69)
mod1 Alt_L (0x40), Alt_R (0x6c), Meta_L (0xcd)
mod2 Num_Lock (0x4d)
mod3
mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf)
mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb)
next prev parent reply other threads:[~2022-03-12 0:26 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 [this message]
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
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='OBa-CgsrfFC44EGpl3QZ-DsGU-lDCPSQ4GetGZ5LpxcTfF2MdzwZK92wynt8cAB0D-d5twg9S2yzRMeBnA8JYxx-QOLFa2Z5oxJ_TcCm0Kk=@protonmail.com' \
--to=goncholden@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=luangruo@yahoo.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).