public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu> To: cygwin-xfree <cygwin-xfree@cygwin.com> Subject: emacs, GSettings, and gtk3 Date: Mon, 26 Nov 2012 12:56:00 -0000 [thread overview] Message-ID: <50B366E1.1060407@cornell.edu> (raw) I am now able to build emacs-X11 with GSettings support, using either gtk2 or gtk3; the problems discussed in http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html have disappeared. Unfortunately, the resulting build produces some annoying Gtk warnings. 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. See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11177 I don't know any good workaround, except perhaps to wrap emacs in a script, or use an alias, that redirects stderr to a file. (This would be similar to the Linux behavior, where I think stderr for programs started under X11 is typically redirected to ~/.xsession-errors.) 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. The warning can usually, but not always, be ignored. See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8855 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. Thanks in advance for any opinions/advice on how I should deal with these issues in the next emacs release. The simplest solution would be to continue to use gtk2 and to disable GSettings support, but I'm open to other suggestions. Ken Brown Cygwin's Emacs maintainer -- 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/
next reply other threads:[~2012-11-26 12:56 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-11-26 12:56 Ken Brown [this message] 2012-11-27 6:51 ` Yaakov (Cygwin/X)
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=50B366E1.1060407@cornell.edu \ --to=kbrown@cornell.edu \ --cc=cygwin-xfree@cygwin.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).