From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>, "'Tim Cross'" <theophilusx@gmail.com>
Cc: jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: RE: Modify menu-bar help
Date: Fri, 25 Feb 2011 07:38:47 -0800 [thread overview]
Message-ID: <BA2B4A0703674FA6A5FA7B0533C4B6B5@us.oracle.com> (raw)
In-Reply-To: <83zkpkp1ug.fsf@gnu.org>
> > 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_?
>
> No. We don't document bugs, unless they are certain to be more or
> less permanent misfeatures.
Ah, I agree. If this is considered a bug then we should not document it.
In my previous reply I was thinking that Emacs Dev considered this to be part of
the design, with no plan to fix it. Bugs and bug workarounds generally should
not be documented in the manual (but could be documented in release notes etc.).
next prev parent reply other threads:[~2011-02-25 15:38 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
2011-02-25 15:31 ` Eli Zaretskii
2011-02-25 15:38 ` Drew Adams [this message]
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=BA2B4A0703674FA6A5FA7B0533C4B6B5@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--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.