From: Dani Moncayo <dmoncayo@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 15576@debbugs.gnu.org
Subject: bug#15576: 24.3.50; Some minor issues regarding the new TTY menus
Date: Thu, 10 Oct 2013 21:07:25 +0200 [thread overview]
Message-ID: <CAH8Pv0gVbHuA=b3QapO6swEin9B7Kx1fZdKnSP2kkfBiGZVxew@mail.gmail.com> (raw)
In-Reply-To: <jwva9iihsh7.fsf-monnier+emacsbugs@gnu.org>
> IOW for each submenu, you have 3 more or less equivalent/redundant "names":
> - the text to display in the parent menu (i.e. the only thing usually
> displayed).
> - the "prompt" (which is only displayed if you pass that submenu to
> directly popup-menu, or if you use the non-toolkit version of Emacs,
> or now in the tty-menu code).
> - the event associated with this submenu. It's usually a symbol rather
> than a string (because it's compared with `eq'; and it can also be an
> integer), but it's often just a symbol version of the "menu name".
> Those 3 can all be completely different, but normally/usually
> they're identical.
Well, I still don't see at all the point of that name redundancy,
because as I said, I don't think it makes any sense to show one text
for a menu item (holding a submenu), and show a different text for its
submenu's "prompt". It is just plain confusing to me.
>> That's a pity. It would be nice to have those drop-down text menus
>> also on GUI sessions.
>
> Why?
Text menus have its advantages over the GUI (toolkit) menus. Emacs
has total control over them, so that one can do things such as
navigate through them with C-f, C-b, C-n, C-p. Another advantage is
visual integration: the text menus look like the rest of the buffer
text, which is nice.
>>> I tend to close this as not-a-bug. Any reasons not to?
>> See above, but you are the maintainer, so you decide.
>
> IIUC the issue is that fixing those things can represent a lot of work,
> whereas they fix only "cosmetic" issues, so it's difficult to justify
> the effort.
Fair enough... :)
--
Dani Moncayo
next prev parent reply other threads:[~2013-10-10 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 19:06 bug#15576: 24.3.50; Some minor issues regarding the new TTY menus Dani Moncayo
2013-10-09 19:26 ` Eli Zaretskii
2013-10-09 20:11 ` Dani Moncayo
2013-10-09 20:26 ` Eli Zaretskii
2013-10-11 18:10 ` Dani Moncayo
2013-10-10 0:52 ` Stefan Monnier
2013-10-10 19:07 ` Dani Moncayo [this message]
2013-10-10 20:14 ` Drew Adams
2013-10-10 21:04 ` Stefan Monnier
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='CAH8Pv0gVbHuA=b3QapO6swEin9B7Kx1fZdKnSP2kkfBiGZVxew@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=15576@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.