unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 62962@debbugs.gnu.org, Eric Blood <winkywooster@gmail.com>
Subject: bug#62962: 28.2; blocked key combinations in macos
Date: Wed, 06 Sep 2023 22:22:25 +0200	[thread overview]
Message-ID: <m2fs3r6ohq.fsf@Pro.fritz.box> (raw)
In-Reply-To: <CADwFkmn=KRnC2d9HSbJ8oFhdqhu5p0T=R77hnDrDcmn=qPtrRw@mail.gmail.com> (Stefan Kangas's message of "Wed, 6 Sep 2023 11:34:09 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

> Eric Blood <winkywooster@gmail.com> writes:
>
>>> If this is a third-party build, so I'd suggest reporting this to the
>>> Emacs for MacOSX developers first.
>>
>> to be clear https://www.gnu.org/software/emacs/download.html does
>> point to https://emacsformacosx.com/ which would indicate it's
>> official in some manner. even the `brew install --cask emacs` (which
>> the download page instructs) points to these builds. i didn't realize
>> it's not considered an offical build.
>
> Aha, I wasn't aware.  It seems like they actually just build a stock
> Emacs, so I suppose that is fine, then.
>
>>> Alternatively, you could try building Emacs from source and see if
>>> you can reproduce the issue.
>>
>> ok, i just built it from source (haven't done that in years, not as
>> painful as it once was), but still the same issue.
>
> Thanks for testing.
>
>>> Does Emacs have support for this?
>>
>> i would think that any unbound key combinations should be passed to
>> the operating system, and with the *unofficial* railwaycat build, it
>> works.
>
> Is your suspicion here that the keys never reach Emacs, or is it that
> the special feature of the "Magnet" program that doesn't work like it
> should?
>
>>> What is the "railwaycat build"?
>>
>> https://github.com/railwaycat/homebrew-emacsmacport
>
> Noted, thanks.

Eric, maybe do a M-x customize-group RET ns RET, and look at the various
"modifier" choices in the customize buffer.  There are 2 for the two
Option keys on the left and right side of the keyboard.






  parent reply	other threads:[~2023-09-06 20:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 21:53 bug#62962: 28.2; blocked key combinations in macos Eric Blood
2023-09-05 16:31 ` Stefan Kangas
2023-09-06 15:41   ` Eric Blood
2023-09-06 16:11     ` Stefan Kangas
2023-09-06 16:49       ` Eric Blood
2023-09-06 18:34         ` Stefan Kangas
2023-09-06 19:01           ` Gerd Möllmann
2023-09-06 20:22           ` Gerd Möllmann [this message]
2023-09-09 23:27           ` Eric Blood
2023-09-10  5:15             ` Eli Zaretskii
2023-09-06 20:49         ` Alan Third

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=m2fs3r6ohq.fsf@Pro.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=62962@debbugs.gnu.org \
    --cc=stefankangas@gmail.com \
    --cc=winkywooster@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.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).