From: Yoichi Nakayama <yoichi.nakayama@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, 74619@debbugs.gnu.org
Subject: bug#74619: macOS: <ns-show-prefs> displayed as keybinding for \\[customize] on emacs -nw
Date: Wed, 4 Dec 2024 22:53:43 +0900 [thread overview]
Message-ID: <CAF5D8-vkJ=9-gHtL-vh19RYt-Qi5kiiXreTSn6Rsw3dLs3DGoQ@mail.gmail.com> (raw)
In-Reply-To: <87bjxufa7d.fsf@gmail.com>
> Right, but OTOH typical terminal setups donʼt allow you to use super
> as a modifier anyway (unless Gerd has a magic recipe).
It's not true. We can run commands that use super with "C-x @ s" instead.
I think there is no way to enter ns-*.
On Mon, Dec 2, 2024 at 11:09 PM Robert Pluim <rpluim@gmail.com> wrote:
>
> >>>>> On Sat, 30 Nov 2024 16:40:53 +0900, Yoichi Nakayama <yoichi.nakayama@gmail.com> said:
>
> Yoichi> I found that bug#55940 (https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55940)
> Yoichi> has not been fixed on Emacs started by "emacs -nw"
>
> Yoichi> (substitute-command-keys "\\[customize]")
> Yoichi> #("<ns-show-prefs>" 0 15 (font-lock-face help-key-binding face
> Yoichi> help-key-binding))
>
> Yoichi> I think this is because make-non-key-event for ns-* is not called
> Yoichi> in this situation.
>
> Right, but OTOH typical terminal setups donʼt allow you to use super
> as a modifier anyway (unless Gerd has a magic recipe). I guess it
> couldnʼt do too much harm to call the ns-specific portion of
> `x-setup-function-keys' even when not in a graphical frame, but Iʼm
> not sure where we could hook that into.
>
> Robert
> --
--
Yoichi NAKAYAMA
next prev parent reply other threads:[~2024-12-04 13:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 7:40 bug#74619: macOS: <ns-show-prefs> displayed as keybinding for \\[customize] on emacs -nw Yoichi Nakayama
2024-12-02 14:09 ` Robert Pluim
2024-12-02 14:49 ` Gerd Möllmann
2024-12-04 13:53 ` Yoichi Nakayama [this message]
2024-12-04 14:38 ` Robert Pluim
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='CAF5D8-vkJ=9-gHtL-vh19RYt-Qi5kiiXreTSn6Rsw3dLs3DGoQ@mail.gmail.com' \
--to=yoichi.nakayama@gmail.com \
--cc=74619@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--cc=rpluim@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).