From: Augusto Stoffel <arstoffel@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, 62250@debbugs.gnu.org
Subject: bug#62250: 29.0.60; Allow context menu from text properties to not override everything
Date: Sat, 18 Mar 2023 19:44:38 +0100 [thread overview]
Message-ID: <878rftrjah.fsf@gmail.com> (raw)
In-Reply-To: <86fsa1or67.fsf@mail.linkov.net> (Juri Linkov's message of "Sat, 18 Mar 2023 20:10:40 +0200")
On Sat, 18 Mar 2023 at 20:10, Juri Linkov wrote:
>> Note that currently a member of context-menu-functions cannot override
>> the menu,
>
> Actually, a member of context-menu-functions can override the
> previous menu it receives as an argument. And the last member
> always wins by overriding the whole menu. So it's just a question
> of ordering the members of context-menu-functions.
Right. What I suggested would make the overriding independent of the
ordering of the members, which also (typically) influences the order of
the menu items. But maybe overriding the menu is not such a common
use-case anyway, and either mechanism is sufficient.
The really interesting feature would be to be able to add to the context
menu with a text property.
next prev parent reply other threads:[~2023-03-18 18:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 7:51 bug#62250: 29.0.60; Allow context menu from text properties to not override everything Augusto Stoffel
2023-03-18 8:31 ` Eli Zaretskii
2023-03-18 11:19 ` Augusto Stoffel
2023-03-18 11:24 ` Eli Zaretskii
2023-03-18 11:29 ` Augusto Stoffel
2023-03-18 11:33 ` Eli Zaretskii
2023-03-18 18:10 ` Juri Linkov
2023-03-18 18:44 ` Augusto Stoffel [this message]
2023-03-19 17:40 ` Juri Linkov
2023-03-19 18:10 ` Augusto Stoffel
2023-03-20 18:29 ` Juri Linkov
2023-03-18 18:08 ` Juri Linkov
2023-03-18 18:39 ` Augusto Stoffel
2023-03-19 17:43 ` Juri Linkov
2023-03-19 18:21 ` Augusto Stoffel
2023-03-20 18:34 ` Juri Linkov
2023-04-02 16:35 ` Juri Linkov
2024-03-05 16:51 ` 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
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=878rftrjah.fsf@gmail.com \
--to=arstoffel@gmail.com \
--cc=62250@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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).