From: Christopher Dimech <dimech@gmx.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: help-gnu-emacs@gnu.org, goncholden@protonmail.com,
Eric S Fraga <e.fraga@ucl.ac.uk>
Subject: Re: dell laptop cannot access super-key.
Date: Sun, 13 Mar 2022 22:55:36 +0100 [thread overview]
Message-ID: <trinity-1310de13-f449-4c1a-8626-3f8ac67a0146-1647208536793@3c-app-mailcom-bs13> (raw)
In-Reply-To: <trinity-790e774f-4650-42e5-83d7-c114e928d122-1647197908943@3c-app-mailcom-bs08>
The easiest thing you can do is swap the Alt(Meta) with Ctrl,
and use Cops-Lock as your Hyper. You can do this with Trisquel.
System -> Preferences -> Hardware -> Keyboard
Then click on Layouts -> Options
> Sent: Monday, March 14, 2022 at 6:58 AM
> From: "Christopher Dimech" <dimech@gmx.com>
> To: goncholden@protonmail.com
> Cc: help-gnu-emacs@gnu.org, "Eric S Fraga" <e.fraga@ucl.ac.uk>
> Subject: Re: dell laptop cannot access super-key.
>
> T have set up a dvorak-classic using
>
> setxkbmap -layout us -variant dvorak-classic
>
> This gives
>
> 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)
>
>
> keycode 37 = Alt_L Meta_L Alt_R Meta_R
> keycode 64 = Control_L NoSymbol Control_L
> keycode 105 = Alt_L Meta_L Alt_R Meta_R
> keycode 108 = Control_L NoSymbol Control_L
> keycode 133 = Super_L NoSymbol Super_L
> keycode 134 = Super_R NoSymbol Super_R
> keycode 204 = NoSymbol Alt_L NoSymbol Alt_L
> keycode 205 = NoSymbol Meta_L NoSymbol Meta_L
> keycode 206 = NoSymbol Super_L NoSymbol Super_L
> keycode 207 = NoSymbol Hyper_L NoSymbol Hyper_L
>
> Calling xmodmap with the following, gets xev to return the correct keys
>
> clear control
> clear mod1
>
> keycode 37 = Control_L NoSymbol Control_L
> keycode 105 = Control_L NoSymbol Control_L
>
> keycode 64 = Alt_L Meta_L Alt_R Meta_R
> keycode 108 = Alt_L Meta_L Alt_R Meta_R
>
> add control = Alt_L Alt_R Meta_L
> add mod1 = Control_L Control_R
>
> But whilst Emacs-27.2 recognises the control modifier on mod1, it fails to recognise
> the meta modifier on control.
>
>
>
next prev parent reply other threads:[~2022-03-13 21:55 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 [this message]
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=trinity-1310de13-f449-4c1a-8626-3f8ac67a0146-1647208536793@3c-app-mailcom-bs13 \
--to=dimech@gmx.com \
--cc=e.fraga@ucl.ac.uk \
--cc=goncholden@protonmail.com \
--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.
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).