emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-orgmode@gnu.org
Subject: Re: MacOS (emacsformacosx) c-spc, does not run set-mark-command
Date: Thu, 25 Mar 2021 08:24:14 +0100	[thread overview]
Message-ID: <87czvnofvl.fsf@mat.ucm.es> (raw)
In-Reply-To: 87ft0k2m8v.fsf@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

>>> "TC" == Tim Cross <theophilusx@gmail.com> writes:

> Diego Zamboni <diego@zzamboni.org> writes:

>> 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.
>> 

> Normally, you need to disable those 'shortcuts' at the OS level i.e.
> under the keyboard shortucts item in macOS preferences panel. Problem is
> any macOS shortcut will grab the keys before Emacs sees them. Not sure
> how the emacs-plus version gets around this. 

Right, it seems and issue of the OS shortcuts as C-space is for
switching keyboards (US->spanish>etc etc).[1]

Do you know how to change or disable them?

Uwe 



Footnotes:
[1]  the same happens on Linux/KDE


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2021-03-25  7:28 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
2021-03-24 22:54     ` Tim Cross
2021-03-25  7:24       ` Uwe Brauer [this message]
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=87czvnofvl.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --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).