From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25059 invoked by alias); 26 Nov 2012 12:56:29 -0000 Received: (qmail 25049 invoked by uid 22791); 26 Nov 2012 12:56:28 -0000 X-SWARE-Spam-Status: No, hits=-3.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_NO,RP_MATCHES_RCVD,SPF_NEUTRAL,TW_GT X-Spam-Check-By: sourceware.org Received: from orchid.mail.cornell.edu (HELO orchid.mail.cornell.edu) (132.236.56.61) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 26 Nov 2012 12:56:20 +0000 Received: from authusersmtp.mail.cornell.edu (granite2.mail.cornell.edu [128.253.83.142]) by orchid.mail.cornell.edu (8.14.4/8.14.4) with ESMTP id qAQCuINR025391 for ; Mon, 26 Nov 2012 07:56:19 -0500 (EST) Received: from [192.168.1.2] (cpe-67-249-194-47.twcny.res.rr.com [67.249.194.47]) (authenticated bits=0) by authusersmtp.mail.cornell.edu (8.14.4/8.12.10) with ESMTP id qAQCuH4a003034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 26 Nov 2012 07:56:18 -0500 (EST) Message-ID: <50B366E1.1060407@cornell.edu> Date: Mon, 26 Nov 2012 12:56:00 -0000 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0 MIME-Version: 1.0 To: cygwin-xfree Subject: emacs, GSettings, and gtk3 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-CORNELL-SPAM-CHECKED: Pawpaw X-Original-Sender: kbrown@cornell.edu - Mon Nov 26 07:56:18 2012 X-PMX-CORNELL-REASON: CU_White_List_Override X-IsSubscribed: yes Mailing-List: contact cygwin-xfree-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-xfree-owner@cygwin.com Reply-To: cygwin-xfree@cygwin.com Mail-Followup-To: cygwin-xfree@cygwin.com X-SW-Source: 2012-11/txt/msg00030.txt.bz2 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/