From: "Jan D." <jan.h.d@swipnet.se>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 4843@emacsbugs.donarmstrong.com
Subject: bug#4843: creating menus
Date: Mon, 02 Nov 2009 09:20:18 +0100 [thread overview]
Message-ID: <4AEE9642.7060401@swipnet.se> (raw)
In-Reply-To: <87hbtdpuo8.fsf@stupidchicken.com>
On 2009-11-02 02:44, Chong Yidong wrote:
>> It can be because you are now using a newer Gtk+ version. Please use
>> report-emacs-bug so we can see that at once instead of having to ask.
>>
>> If indeed you are using Gtk+, it is due to the introduction of native windows.
>> To see if this is the case, start emacs with
>> % GDK_NATIVE_WINDOWS=1 emacs
>> and try again.
>
> I don't have any recollection of this problem. Could you elaborate? If
> the menus don't work properly unless GDK_NATIVE_WINDOWS=1, maybe we
> should set it unconditionally.
Native windows is Gtk having internal windows that map to the same X
window. This confuses Emacs, mostly when it tries to map X events for
windows to frames. I.e. there might not be separate X windows in the
menu that is children to the frame X window. See bug #4122.
I'd rather not set GDK_NATIVE_WINDOWS as it disables the optimizations
that native windows give. It may also be removed in a future Gtk+
release, so it isn't a good solution.
It isn't hard to fix emacs 22 as well, but does this bug warrant a new
22 release? Maybe, as distributions like Ubuntu still ships 22 (see the
linked Ubuntu bug in #4122). A 23-release soonish is not wrong though :-)
Jan D.
next prev parent reply other threads:[~2009-11-02 8:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 1:44 bug#4843: creating menus Chong Yidong
2009-11-02 8:20 ` Jan D. [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-31 22:29 Daniel Carvalho
2009-11-01 12:45 ` Jan Djärv
2009-11-01 12:58 ` Daniel Carvalho
2009-11-02 8:08 ` Jan D.
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=4AEE9642.7060401@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=4843@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.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).