unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Dani Moncayo <dmoncayo@gmail.com>,
	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 13:14:04 -0700 (PDT)	[thread overview]
Message-ID: <bb40ba34-eec2-4dba-b650-42ba56deb658@default> (raw)
In-Reply-To: <CAH8Pv0gVbHuA=b3QapO6swEin9B7Kx1fZdKnSP2kkfBiGZVxew@mail.gmail.com>

> > 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.

Dani, the point of having potentially different names is that there are
different uses of a given menu, including the popup case that Stefan
described and which is fairly rare.

But yes, nothing prevents someone from using the same name for all
three uses.  IOW, you *can* use different names for different uses,
but nothing requires you to.





  reply	other threads:[~2013-10-10 20:14 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
2013-10-10 20:14         ` Drew Adams [this message]
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

  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=bb40ba34-eec2-4dba-b650-42ba56deb658@default \
    --to=drew.adams@oracle.com \
    --cc=15576@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --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 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).