From: Diego Zamboni <diego@zzamboni.org>
To: Tim Cross <theophilusx@gmail.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: MacOS (emacsformacosx) c-spc, does not run set-mark-command
Date: Wed, 24 Mar 2021 23:38:15 +0100 [thread overview]
Message-ID: <CAGY83Ed6PPCtw1uOOWMYJBZT1xnMBGz3Mcg-oveMNy-NVmUf-A@mail.gmail.com> (raw)
In-Reply-To: <875z1gkzi8.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
I have seen differences in this behavior depending on the Emacs build. The
emacs-mac port (https://github.com/railwaycat/homebrew-emacsmacport) seems
to intercept certain Mac-specific keybindings such as C-space and C-M-space
and gives them their "Mac meaning", e.g. to bring up Spotlight or the
symbol chooser. I could never figure out how to disable this behavior.
Now I use emacs-plus (https://github.com/d12frosted/homebrew-emacs-plus)
and this no longer happens.
--Diego
On Wed, Mar 24, 2021 at 10:34 PM Tim Cross <theophilusx@gmail.com> wrote:
>
> Uwe Brauer <oub@mat.ucm.es> writes:
>
> > Hi
> >
> > Does anybody know how to achieve the traditional binding of
> > C-space to set-mark-command on MacOS (for emacsformacos)?
> >
> > Shift arrow down works, but will not work for a lot of features in org
> > mode.
> >
>
> Have you verified c-space is not being used by the macOS UI as a
> shortcut for something like spotlight search?
>
> I now use spacemacs, but when I used my own setup, I don't recall having
> to do anything special to get this behaviour apart from disabling macOS
> shortcuts.
>
> --
> Tim Cross
>
>
[-- Attachment #2: Type: text/html, Size: 1788 bytes --]
next prev parent reply other threads:[~2021-03-24 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 21:18 MacOS (emacsformacosx) c-spc, does not run set-mark-command Uwe Brauer
2021-03-24 21:32 ` Tim Cross
2021-03-24 22:38 ` Diego Zamboni [this message]
2021-03-24 22:54 ` Tim Cross
2021-03-25 7:24 ` Uwe Brauer
2021-03-25 8:00 ` Diego Zamboni
2021-03-25 8:30 ` 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=CAGY83Ed6PPCtw1uOOWMYJBZT1xnMBGz3Mcg-oveMNy-NVmUf-A@mail.gmail.com \
--to=diego@zzamboni.org \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@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 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).