unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Tim Cross <theophilusx@gmail.com>
Cc: Emacs-devel@gnu.org, Ben Key <bkey76@gmail.com>
Subject: Re: Modify menu-bar help
Date: Sat, 26 Feb 2011 11:21:25 +0100	[thread overview]
Message-ID: <4D68D425.4040602@swipnet.se> (raw)
In-Reply-To: <AANLkTik27XmE3O5KU2KRReOE00NGfrXeaBRN=OThqOC3@mail.gmail.com>



Tim Cross skrev 2011-02-26 02.04:
>
> Just confirming that the test code works fine with emacs when built with the
> Lucid toolkit. So, the issue does seem toolkit specific. I will now see if I
> can find confirmation this is a GTK+ 'feature' from the GTK docs.
>

I don't think this is documented, it is more how assertions in the code are 
placed and how things work that makes this policy explicit.  After all, it 
isn't documented that you can't put tool-bars, file dialogs or other menu bars 
in a menu bar.  But you can't.

	Jan D.



  reply	other threads:[~2011-02-26 10:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 20:33 Modify menu-bar help Ben Key
2011-02-25 23:58 ` Tim Cross
2011-02-26  1:04   ` Tim Cross
2011-02-26 10:21     ` Jan Djärv [this message]
2011-02-26 10:22   ` Jan Djärv
2011-02-26 22:27     ` Tim Cross
  -- strict thread matches above, loose matches on Subject: below --
2011-02-24 23:16 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
2011-02-25  9:27   ` 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=4D68D425.4040602@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=Emacs-devel@gnu.org \
    --cc=bkey76@gmail.com \
    --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).