all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: John Mastro <john.b.mastro@gmail.com>
Cc: 31415@debbugs.gnu.org
Subject: bug#31415: 27.0.50; Strange behavior on Command-$ in MacOS
Date: Sun, 13 May 2018 11:28:10 +0100	[thread overview]
Message-ID: <20180513102810.GD15823@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAOj2CQQaQJoquA5+f0djUa+ZyevK6PfPMw898QsKpJpSQk=3cQ@mail.gmail.com>

On Thu, May 10, 2018 at 06:30:33PM -0700, John Mastro wrote:
> By default, the "command" key in MacOS is bound to "super". If I type
> s-$, Emacs seems to wait for input that it never receives. Anything I
> type afterward appears to be ignored, except `ESC ESC ESC', which gets
> Emacs out of this state. However, even hitting `C-g' repeatedly does
> not.
> 
> The issue seems to be related to the command key rather than to "super"
> or to the command bound to the key. In my configuration, I map command
> to meta, and the same problem happens when I use M-$ to `ispell-word'.
> 
> Using `M-$' with command as meta worked until relatively recently. It
> would be great if it could be brought back or made to fail more
> explicitly.

Hmm, what’s happening is that macOS is going into a screenshot mode.
You can see the shortcuts in system preferences ‐> keyboard ‐>
shortcuts. I don’t know why you’ve not seen this before as I think
it’s been the default in macOS for quite a while now.

I don’t know if we can over‐ride this, and I don’t know that we’d want
to. 
-- 
Alan Third





  reply	other threads:[~2018-05-13 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11  1:30 bug#31415: 27.0.50; Strange behavior on Command-$ in MacOS John Mastro
2018-05-13 10:28 ` Alan Third [this message]
2018-05-13 15:08   ` Eli Zaretskii
2018-05-15 18:52     ` Alan Third
2018-05-15 19:03       ` Eli Zaretskii
2020-01-11 19:21         ` Alan Third
2018-05-13 15:46   ` John Mastro

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=20180513102810.GD15823@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=31415@debbugs.gnu.org \
    --cc=john.b.mastro@gmail.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.
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.