From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jan Djärv'" <jan.h.d@swipnet.se>, "'Eli Zaretskii'" <eliz@gnu.org>
Cc: theophilusx@gmail.com, emacs-devel@gnu.org
Subject: RE: Modify menu-bar help
Date: Fri, 25 Feb 2011 09:22:56 -0800 [thread overview]
Message-ID: <C981D977BA49432A9BF32C809998EE0C@us.oracle.com> (raw)
In-Reply-To: <4D67E1FC.2040408@swipnet.se>
> It is a deliberate limitation imposed on menu bars. I doubt
> that Gtk+ people will consider this as a bug.
>
> >> Bugs and bug workarounds generally should not be documented in the
> >> manual (but could be documented in release notes etc.).
> >
> > We could put it in etc/PROBLEMS, I guess, if we think GTK will not
> > solve this soon enough.
>
> As they probably don't think anything is wrong, they will
> never "solve" this.
In that case I think it has to be considered a design limitation/choice for
Emacs.
IOW, as long as Emacs (on some platforms) is designed to use GTK, which has this
limitation (deliberate design, apparently), this is not an Emacs bug but is part
of the Emacs design. In that case, it should perhaps be documented in the
manual.
In general, users should be able to easily find out whether some known behavior
is considered a bug (which has some hope of being fixed) or is part of the
design.
next prev parent reply other threads:[~2011-02-25 17:22 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
2011-02-25 15:54 ` Eli Zaretskii
2011-02-25 17:08 ` Jan Djärv
2011-02-25 17:22 ` Drew Adams [this message]
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
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=C981D977BA49432A9BF32C809998EE0C@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 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).