From: Christopher Dimech <dimech@gmx.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: luangruo@yahoo.com, 64699@debbugs.gnu.org, uzibalqa@proton.me
Subject: bug#64699: Invalid key definition for keymap-set-after
Date: Tue, 18 Jul 2023 14:34:41 +0200 [thread overview]
Message-ID: <trinity-2d6323b7-c9e4-4cdf-b7db-60b20f5df78e-1689683681490@3c-app-mailcom-bs07> (raw)
In-Reply-To: <87h6q1pgce.fsf@gmail.com>
> Sent: Wednesday, July 19, 2023 at 12:13 AM
> From: "Robert Pluim" <rpluim@gmail.com>
> To: 64699@debbugs.gnu.org
> Cc: luangruo@yahoo.com, uzibalqa@proton.me
> Subject: bug#64699: Invalid key definition for keymap-set-after
>
> >>>>> On Tue, 18 Jul 2023 18:29:08 +0800, Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> said:
>
> Po Lu> The documentation does not mention or imply that `keymap-set-after'
> Po Lu> accepts the same key sequence format as `define-key-after'. And indeed
> Po Lu> it does not.
>
> To be fair, we could probably do with some words about non-key events,
> explaining that you need to write stuff like "<menu-bar> <mcp-topm>" - Robert
Indeed, we should. Vectors for menu items has a rather sketchy description,
requiring references that point to things all over the manual.
next prev parent reply other threads:[~2023-07-18 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 10:00 bug#64699: Invalid key definition for keymap-set-after uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 10:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 12:13 ` Robert Pluim
2023-07-18 12:34 ` Christopher Dimech [this message]
2023-07-18 12:37 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 12:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 13:03 ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=trinity-2d6323b7-c9e4-4cdf-b7db-60b20f5df78e-1689683681490@3c-app-mailcom-bs07 \
--to=dimech@gmx.com \
--cc=64699@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.com \
--cc=uzibalqa@proton.me \
/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.