From: Eli Zaretskii <eliz@gnu.org>
To: Augusto Stoffel <arstoffel@gmail.com>
Cc: 62250@debbugs.gnu.org, juri@linkov.net
Subject: bug#62250: 29.0.60; Allow context menu from text properties to not override everything
Date: Sat, 18 Mar 2023 13:24:39 +0200 [thread overview]
Message-ID: <83o7oqb8ug.fsf@gnu.org> (raw)
In-Reply-To: <878rfu1f37.fsf@gmail.com> (message from Augusto Stoffel on Sat, 18 Mar 2023 12:19:56 +0100)
> From: Augusto Stoffel <arstoffel@gmail.com>
> Cc: 62250@debbugs.gnu.org, juri@linkov.net
> Date: Sat, 18 Mar 2023 12:19:56 +0100
>
> On Sat, 18 Mar 2023 at 10:31, Eli Zaretskii wrote:
>
> >> Alternatively, it can return a completely new menu. In
> >> this case, no further functions from `context-menu-functions' are
> >> called.
>
> > What if a Lisp program _does_ want to override the menu specified by
> > context-menu-functions? or what if it wants the menu specified by the
> > text property to be the _last_ entry, not the first?
>
> It's explained in the bit I kept: you ignore the MENU argument and
> return a totally new keymap / not `eq'.
What MENU argument? I see only a CLICK argument.
> Adding things at the beginning or end of a menu is an option that
> easy-menu-add-item etc already offer, right?
I admit I don't see how easy-menu-add-item is related to this.
> Note that currently a member of context-menu-functions cannot override
> the menu, and a context-menu-function cannot _not_ override it. My
> suggestions allows all possibilities.
That part I did understand, but it looked to me that your proposal
stops short of covering all the possible situations.
next prev parent reply other threads:[~2023-03-18 11:24 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 [this message]
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
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=83o7oqb8ug.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62250@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--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).