From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44454@debbugs.gnu.org
Subject: bug#44454: 26.3; Enhancement request: let :help in menus take a FORM arg, i.e., be eval'd
Date: Tue, 10 Nov 2020 09:27:03 -0800 (PST) [thread overview]
Message-ID: <be393c8d-c750-4ef3-b6ef-62a881f9b8ec@default> (raw)
In-Reply-To: <87o8k5iab4.fsf@gnus.org>
> > I have exactly this situation in my `Info' submenu
> > `Toggle/Cycle'. For the toggle commands there, the
> > toggle checkmark suffices to let you know the current
> > (and hence the next) state/value. For cycle commands
> > there's no way to know, except by actually cycling.
>
> Makes sense to me.
BTW, another way to consider this is to look for
similarity with `help-echo'. Not that the two
need to be similar, but that the use cases are
the same or similar for the value to be evaluated
rather than being restricted to a literal string.
(Yes, there's nothing special about the evaluation
for contexts where `help-echo' is used - it has
nothing, per se, to do with `help-echo', which is
just a property. And yes, for menus, using a
FORM that gets evaluated (by the display engine,
IIUC) is a bit special. But the use cases - the
usefulness for users, is of the same order.)
prev parent reply other threads:[~2020-11-10 17:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 21:34 bug#44454: 26.3; Enhancement request: let :help in menus take a FORM arg, i.e., be eval'd Drew Adams
2020-11-09 16:02 ` Lars Ingebrigtsen
2020-11-09 16:26 ` Drew Adams
2020-11-10 13:57 ` Lars Ingebrigtsen
2020-11-10 17:27 ` Drew Adams [this message]
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=be393c8d-c750-4ef3-b6ef-62a881f9b8ec@default \
--to=drew.adams@oracle.com \
--cc=44454@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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.