From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 52286@debbugs.gnu.org
Subject: bug#52286: 28.0.90; [PATCH] Be consistent in naming of separators in context menu
Date: Sun, 05 Dec 2021 08:45:09 +0200 [thread overview]
Message-ID: <8335n75z4a.fsf@gnu.org> (raw)
In-Reply-To: <7a7d6b5c-ff5e-3d55-bef4-8ce8e163abdb@gmail.com> (message from Jim Porter on Sat, 4 Dec 2021 13:57:31 -0800)
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Sat, 4 Dec 2021 13:57:31 -0800
>
> This is spun off from bug#52237[1]. There's a minor issue with
> `context-menu-mode' where some of the separators are named
> `FOO-separator' and others are named `separator-FOO'. Since these
> separators are partially useful for context menu functions to find the
> right place to insert their items, this inconsistency could be pretty
> confusing for authors of those functions (e.g. in third-party packages).
If you want to introduce a convention that others should follow, this
convention should be documented in the ELisp manual.
> Hopefully this is a small enough change to make it into Emacs 28, since
> otherwise I think we'd just have to live with the names as they are
> forever.
The first pretest of Emacs 28 is already out, so this problem is
already with us, isn't it?
next prev parent reply other threads:[~2021-12-05 6:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-04 21:57 bug#52286: 28.0.90; [PATCH] Be consistent in naming of separators in context menu Jim Porter
2021-12-05 6:45 ` Eli Zaretskii [this message]
2021-12-05 7:44 ` Jim Porter
2021-12-05 10:39 ` Eli Zaretskii
2021-12-06 2:09 ` Jim Porter
2021-12-06 12:55 ` Eli Zaretskii
2021-12-11 20:52 ` Jim Porter
2022-01-15 18:57 ` Juri Linkov
2022-01-15 19:13 ` Eli Zaretskii
2022-01-15 19:19 ` Juri Linkov
2022-01-15 19:23 ` Eli Zaretskii
2022-01-15 19:25 ` Juri Linkov
2021-12-05 9:37 ` Juri Linkov
2021-12-05 17:52 ` Juri Linkov
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=8335n75z4a.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52286@debbugs.gnu.org \
--cc=jporterbugs@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 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.