From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: OT: M-S-$ Not Working
Date: Sat, 06 Feb 2021 17:28:52 +1100 [thread overview]
Message-ID: <87zh0hwvd7.fsf@gmail.com> (raw)
In-Reply-To: <878s8167wm.fsf@mbork.pl>
Marcin Borkowski <mbork@mbork.pl> writes:
> Hi Bo,
>
> I know your problem is resolved now, but in case you don't know, check
> also what `C-h c' does (and `C-h k' is also useful at times). In
> general, spending 20 minutes on looking through what `C-h C-h' says
> might save you some trouble later;-).
>
This is good advice. I would add that if you find that Emacs does not
respond, even to say that the key is not bound or defined, it is
typically a sign that something in the environment e.g. window manager
or X (or Wayland) layer is not passing the key press through. These are
layers which are often overlooked and I've seen people spend hours
inside Emacs trying to work out what the issue is, only to later find it
is at a different layer (OS, windowing environment, window manager,
etc).
In general, standard Emacs key bindings are robust and reliable. If a
standard key binding like M-S $ doesn't work, first step is to try emacs
-Q. If that still does not work, odds are high it is an issue outside of
Emacs. Most common causes are WM shortcuts, modified input device
definitions (as seems to be the culprit here) and modified modmap
settings. Utilities like 'xev' can be useful here (not sure what wayland
has).
When I install a new system (regardless of platform, linux, mac,
windows), my first task is usually to remove or remap shortcuts. These
days, most environments use super, alt, meta and control based
shortcuts, many of which interfere with my Emacs. I rarely use super in
my Emacs key bindings, so often I remap useful WM shortcuts to use
super.
--
Tim Cross
next prev parent reply other threads:[~2021-02-06 6:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 23:25 OT: M-S-$ Not Working Bo Grimes
2021-02-05 3:20 ` Tim Cross
2021-02-05 14:34 ` Bo Grimes
2021-02-05 14:40 ` Maxim Nikulin
2021-02-05 17:38 ` [Resolved]Re: " Bo Grimes
2021-02-06 15:52 ` Maxim Nikulin
2021-02-06 19:18 ` Bo Grimes
2021-02-08 14:31 ` Robert Pluim
2021-02-06 6:13 ` Marcin Borkowski
2021-02-06 6:28 ` Tim Cross [this message]
2021-02-06 15:53 ` Bo Grimes
2021-02-06 16:14 ` Maxim Nikulin
2021-02-06 17:18 ` Tim Cross
2021-02-10 17:15 ` Maxim Nikulin
2021-02-10 18:42 ` Tim Cross
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh0hwvd7.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).