From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Tim Cross <theophilusx@gmail.com>
Cc: 8176@debbugs.gnu.org
Subject: bug#8176: 24.0.50; GUI toolkit differences
Date: Tue, 05 Jul 2011 16:14:36 +0200 [thread overview]
Message-ID: <m3pqlo7r1v.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <CAC=50j9bMd1FMPyt0AqqaxMvjQpb-3EQzVNp0p8Fg03_iZBzHg@mail.gmail.com> (Tim Cross's message of "Tue, 5 Jul 2011 10:00:57 +1000")
Tim Cross <theophilusx@gmail.com> writes:
> My suggestion would be to add it to the elisp manual, possibly as a
> footnote, in either section 22.17 or possibly 22.17.1. Something along
> the lines that not all GUI toolkits are equal and some features or
> behaviours available in one toolkit may not be available in another.
> For example, GTK will not allow a top level menu button or action,
> while Lucid and NS do.
>
> A tricky part in documenting this is getting consistency of terms. I'm
> not sure if 'top level button or action' is really understood, but
> basically it refers to a menu item on the top level menu bar which
> performs an action other than to open a sub-menu.
Could you suggest a paragraph for 22.17.1 that explains this problem?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-05 14:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 4:13 bug#8176: 24.0.50; GUI toolkit differences Tim Cross
2011-07-04 14:05 ` Lars Magne Ingebrigtsen
2011-07-05 0:00 ` Tim Cross
2011-07-05 5:56 ` Jan Djärv
2011-07-05 6:02 ` Tim Cross
2011-07-05 8:48 ` Jan D.
2011-07-06 7:02 ` Tim Cross
2011-07-05 14:14 ` Lars Magne Ingebrigtsen [this message]
2011-07-06 6:56 ` Tim Cross
2011-07-12 3:34 ` Tim Cross
2011-07-15 16:33 ` Lars Magne Ingebrigtsen
2011-07-15 23:51 ` Tim Cross
2011-07-16 17:47 ` Glenn Morris
2011-07-16 18:04 ` Lars Magne Ingebrigtsen
2011-07-16 18:14 ` Andreas Schwab
2011-07-16 18:32 ` Glenn Morris
2011-07-06 15:12 ` Jason Rumney
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=m3pqlo7r1v.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=8176@debbugs.gnu.org \
--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).