From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: chad <yandros@mit.edu>, darren.hoo@gmail.com, emacs-devel@gnu.org
Subject: Re: Input for TTY menus
Date: Fri, 18 Oct 2013 16:04:54 -0400 [thread overview]
Message-ID: <jwvob6mpd5e.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83li1qmoog.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 18 Oct 2013 21:14:39 +0300")
>> Both gui and terminal emacs under NS have a services menu, but only
>> the gui NS emacs is correctly populating it from the system. It
>> seems to be created in nsterm.m:ns_term_init() when the application
>> menu is created (look for svcsMenu).
>> > Also, if you invoke tmm-menubar with M-`, does the Services item
>> > appear there, and if so, can it be selected and used as you'd expect?
>> It tmm-menu does have a Services item, and it's empty there also.
> Thanks for explaining and for testing.
It sounds like there's a bug in the NS code: the menu should probably
either not exist under a tty, or be filled with appropriate elements.
>> At a guess, the NS port is creating a stub for the menubar, and
>> then moving it into the application menu in some NS gui-only code.
> I see something in nsfns.m. Perhaps some NS person could look into
> fixing this.
But the tty-menu code should also correctly handle an empty menu.
E.g. if I do:
emacs -Q -nw
M-: (global-set-key [menu-bar test] '(menu-item "Test" (keymap "Test"))) RET
f10
then f10 just tells me "Empty menu" and doesn't let me move to
another menu.
Stefan
next prev parent reply other threads:[~2013-10-18 20:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 13:38 Input for TTY menus Eli Zaretskii
2013-09-19 13:52 ` Masatake YAMATO
2013-09-19 14:33 ` Stefan Monnier
2013-09-19 15:47 ` Eli Zaretskii
2013-09-19 19:21 ` Stefan Monnier
2013-09-23 13:18 ` Eli Zaretskii
2013-09-23 14:43 ` Stefan Monnier
2013-09-21 14:56 ` Eli Zaretskii
2013-10-17 5:34 ` Darren Hoo
2013-10-17 15:49 ` Eli Zaretskii
2013-10-18 4:55 ` Darren Hoo
2013-10-18 6:49 ` Eli Zaretskii
2013-10-18 7:37 ` Darren Hoo
2013-10-18 9:13 ` Eli Zaretskii
2013-10-18 10:39 ` Darren Hoo
2013-10-18 13:38 ` Eli Zaretskii
2013-10-18 13:40 ` Eli Zaretskii
2013-10-19 18:38 ` Darren Hoo
2013-10-19 18:58 ` Darren Hoo
2013-10-19 19:07 ` Darren Hoo
2013-10-20 9:32 ` Jan Djärv
2013-10-18 14:11 ` Eli Zaretskii
2013-10-18 15:12 ` Stefan Monnier
2013-10-18 15:28 ` Eli Zaretskii
2013-10-18 18:17 ` Stefan Monnier
2013-10-19 8:40 ` Eli Zaretskii
2013-10-19 13:45 ` Stefan Monnier
2013-10-18 17:41 ` chad
2013-10-18 17:43 ` chad
2013-10-18 18:14 ` Eli Zaretskii
2013-10-18 19:26 ` Jan Djärv
2013-10-18 20:04 ` Stefan Monnier [this message]
2013-10-19 7:35 ` Eli Zaretskii
2013-10-19 9:43 ` Eli Zaretskii
2013-10-19 13:40 ` Stefan Monnier
2013-10-19 14:45 ` Eli Zaretskii
2013-10-19 15:25 ` Stefan Monnier
2013-10-19 16:32 ` Eli Zaretskii
2013-10-19 8:58 ` Jan Djärv
2013-10-19 9:01 ` Eli Zaretskii
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=jwvob6mpd5e.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=darren.hoo@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yandros@mit.edu \
/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).