From: Kepa via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Corwin Brust <corwin@bru.st>
Cc: "Help-Gnu-Emacs (help-gnu-emacs@gnu.org)" <help-gnu-emacs@gnu.org>
Subject: Re: I am trying to become an Emacs "super" user on Windows
Date: Wed, 23 Oct 2024 23:37:12 +0200 [thread overview]
Message-ID: <172971943780.6.128535654820852595.472274620@slmails.com> (raw)
In-Reply-To: <CAJf-WoS_uWZNdL06FfPuUnj1eb-fn0prL4O4dGseL3ar9nbBVw@mail.gmail.com>
Hi, Corwin
On 23/10/2024 22:14, corwin at bru.st wrote:
> On Wed, Oct 23, 2024, 14:49 Kepa via Users list for the GNU Emacs text
> editor <help-gnu-emacs@gnu.org> wrote:
>
>
> But..., s-M- works while M-s- doesn't work.
> Is the order of the super modifier important, or shouldn't be?
> Any help would be appreciated.
>
>
> Are you saying the order you depress keys in makes a difference when
> pressing chords involving swapped capslock and super on Windows? If
> so, does it work when you press all three (or just both modifiers) at
> the exact same time?
Super (ex-capslock) must be the leading key. When pressing all three,
super must be the first one, or it is ignored.
If I press Meta or control first, I get this message:
M-<capslock> is undefined, or
C-<capslock> is undefined, or, if all three:
C-M-<capslock> is undefined
If Super is leading, it works, for example:
C-M-s-f
>
> Do you have sticky keys enabled in Windows, by chance?
OFF
Fwd:
next prev parent reply other threads:[~2024-10-23 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 19:49 I am trying to become an Emacs "super" user on Windows Kepa via Users list for the GNU Emacs text editor
2024-10-23 20:14 ` Corwin Brust
2024-10-23 21:37 ` Kepa via Users list for the GNU Emacs text editor [this message]
2024-10-23 21:47 ` Stefan Monnier via Users list for the GNU Emacs text editor
-- strict thread matches above, loose matches on Subject: below --
2024-10-24 2:27 Kepa 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=172971943780.6.128535654820852595.472274620@slmails.com \
--to=help-gnu-emacs@gnu.org \
--cc=corwin@bru.st \
--cc=gnu.cognition199@slmails.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).