From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Glenn Morris <rgm@gnu.org>
Cc: ronis@ronispc.chem.mcgill.ca, 4134@emacsbugs.donarmstrong.com
Subject: bug#4134: [Fwd: [Bug 593249] emacs and acroread don't work properly after upgrading to 2.17.9]
Date: Sun, 30 Aug 2009 12:36:14 +0200 [thread overview]
Message-ID: <4A9A561E.3080208@swipnet.se> (raw)
In-Reply-To: <8b63c8hnhz.fsf@fencepost.gnu.org>
Glenn Morris skrev:
> retitle 4134 23.1; Problems with gtk+ >= 2.7.19
> stop
>
> David Ronis wrote:
>
>> Turns out the problem is in gtk+. I've filed a bug report and this is
>> the last (relevant) comment on the bug.
>
> Thanks for forwarding this information. Hopefully it will be useful to
> those Emacs developers who understand these things (Jan?).
>
>> http://bugzilla.gnome.org/show_bug.cgi?id=593249
> [...]
>> --- Comment #3 from Alexander Larsson <alexl@redhat.com> 2009-08-27
> [...]
>> Instead I would recommend adding some code to emacs that calls
>> gdk_x11_drawable_get_xid() on all "toplevel" Gtk+ widgets they put
>> in the buffer window. This will ensure these windows get their own X
>> window and should be totally backwards compat and safe on older
>> versions of Gtk+.
This client side windows Gtk+ is introducing in 2.17 assumes you only do Gtk+
calls. But Emacs does a lot of pure X11 calls on the X11 windows created by
Gtk+. So eihter Emacs must go pure Gtk+ for the Gtk+ build, or we do a
workaround. The workaround seems most likely for now.
I'll get on it when I find some time.
Jan D.
prev parent reply other threads:[~2009-08-30 10:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 15:58 bug#4134: [Fwd: [Bug 593249] emacs and acroread don't work properly after upgrading to 2.17.9] David Ronis
2009-08-27 22:59 ` Glenn Morris
2009-08-27 23:05 ` Processed: " Emacs bug Tracking System
2009-08-30 10:36 ` Jan Djärv [this message]
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=4A9A561E.3080208@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=4134@emacsbugs.donarmstrong.com \
--cc=rgm@gnu.org \
--cc=ronis@ronispc.chem.mcgill.ca \
/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.