From: "Drew Adams" <drew.adams@oracle.com>
To: "'Tim Cross'" <theophilusx@gmail.com>,
"'Jan Djärv'" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org
Subject: RE: Modify menu-bar help
Date: Fri, 25 Feb 2011 07:29:08 -0800 [thread overview]
Message-ID: <2D4F96D07F354C7AAC0E39370A2536E3@us.oracle.com> (raw)
In-Reply-To: <AANLkTimW5CH9RaMMUtNordOETMv18q6=3C8SmzMLG5-p@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
This strikes me as something that should be in the manual. Would everyone agree
it would be worth lodging a bug report to have this information added as a
footnote or reference i.e. that you cannot add menu actions/buttons to the top
level menu when using gtk_?
Yes, sounds like useful info to me. And info that it might not be easy to
discover otherwise (modulo writing to emacs-devel as you did). Even if this is
not Emacs-specific but is general to GTK, an Emacs user thinks of the menus as
Emacs menus, not necessarily as GTK menus.
[-- Attachment #2: Type: text/html, Size: 1154 bytes --]
next prev parent reply other threads:[~2011-02-25 15:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 23:16 Modify menu-bar help Tim Cross
2011-02-25 0:52 ` Drew Adams
2011-02-25 5:14 ` Tim Cross
2011-02-25 7:15 ` Drew Adams
2011-02-25 9:31 ` Eli Zaretskii
2011-02-25 9:30 ` Eli Zaretskii
2011-02-25 10:03 ` Jan Djärv
2011-02-25 14:49 ` Tim Cross
2011-02-25 15:29 ` Drew Adams [this message]
2011-02-25 15:31 ` Eli Zaretskii
2011-02-25 15:38 ` Drew Adams
2011-02-25 15:54 ` Eli Zaretskii
2011-02-25 17:08 ` Jan Djärv
2011-02-25 17:22 ` Drew Adams
2011-02-25 9:27 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2011-02-25 20:33 Ben Key
2011-02-25 23:58 ` Tim Cross
2011-02-26 1:04 ` Tim Cross
2011-02-26 10:21 ` Jan Djärv
2011-02-26 10:22 ` Jan Djärv
2011-02-26 22:27 ` Tim Cross
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=2D4F96D07F354C7AAC0E39370A2536E3@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=theophilusx@gmail.com \
/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.