bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#11177: 24.0.95; gtk_window_parse_geometry warning


From: Ken Brown
Subject: bug#11177: 24.0.95; gtk_window_parse_geometry warning
Date: Sun, 25 Nov 2012 12:40:53 -0500
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0

On 4/6/2012 6:57 AM, Jan Djärv wrote:
Hello.

4 apr 2012 kl. 22:00 skrev Ken Brown:

When emacs is built with gtk3 and the window geometry is specified on the 
command line or in .Xdefaults, the following warning appears in the terminal 
from which emacs was started:

Gtk-WARNING **: gtk_window_parse_geometry() called on a window with no visible 
children; the window should be set up before gtk_window_parse_geometry() is 
called.

To reproduce:

1. Build emacs with the configure option --with-x-toolkit=gtk3.

2. emacs -Q --geometry=80x34+340+40 &

I don't know enough about gtk to know whether this warning can safely be 
ignored, but here's a quote from the source file gtk/gtkwindow.c in which 
gtk_window_parse_geometry is defined:

* Note that for gtk_window_parse_geometry() to work as expected, it has
* to be called when the window has its "final" size, i.e. after calling
* gtk_widget_show_all() on the contents and gtk_window_set_geometry_hints()
* on the window.


This is a false warning. There are known issues with the rows in the geometry 
given to Emacs (you may get less rows than you ask for) but the positions are 
AFAIK more or less correct (i.e. both Gtk and the window manager modifyes it in 
an effort to keep the window onscreen).  I don't know why they added this 
warning in Gtk+ 3, the code is more or less the same as in Gtk+2.

Now, if you have a case where the window position is much different from the 
geometry given, that would be a real bug.

Now that gtk3 is used by default, this warning is likely to annoy more and more users. Is there a way to suppress it? Are other people seeing it and simply ignoring it?

Ken






reply via email to

[Prev in Thread] Current Thread [Next in Thread]