Re: emacs, GSettings, and gtk3

["Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>]

On Mon, 2012-11-26 at 07:56 -0500, Ken Brown wrote:
> I'm trying to decide whether the benefits of GSettings and gtk3 
> outweigh the annoyances.  I'd like the opinions of emacs users and GNOME 
> experts on this.  Here are the details:
> 
> 1. If emacs is built using 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.
> 
> The warning can safely be ignored but is annoying.

GTK+ warnings aren't uncommon, as GTK+ behaviour gradually changes over
time and programs don't always keep up.  If the program operates
correctly, and upstream says they can be ignored, then I wouldn't worry
about them.

As for choosing between GTK+ 2 vs 3, I would go with the upstream
default.

> 2. If emacs is built with GSettings support and is started without a 
> D-Bus daemon running, the following warning is issued:
> 
> GLib-WARNING **: In call to g_spawn_sync(), exit status of a child 
> process was requested but SIGCHLD action was set to SIG_IGN and ECHILD 
> was received by waitpid(), so exit status can't be returned. This is a 
> bug in the program calling g_spawn_sync(); either don't request the exit 
> status, or don't set the SIGCHLD action.
> 
> In this case there is a simple workaround: Ensure, by a suitable line in 
> ~/.startxwinrc or ~/.bashrc, that a D-Bus daemon is always running 
> before emacs is started.

A D-Bus session daemon is required for most modern desktop software
nowadays, so I wouldn't consider this a setback.

HTH,


Yaakov



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/