From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21207 invoked by alias); 5 Dec 2011 13:28:06 -0000 Received: (qmail 21197 invoked by uid 22791); 5 Dec 2011 13:28:05 -0000 X-SWARE-Spam-Status: No, hits=-1.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_NEUTRAL,TW_GT,TW_GV X-Spam-Check-By: sourceware.org Received: from granite1.mail.cornell.edu (HELO authusersmtp.mail.cornell.edu) (128.253.83.141) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 05 Dec 2011 13:27:51 +0000 Received: from [192.168.1.3] (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 pB5DRntF019873 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 5 Dec 2011 08:27:50 -0500 (EST) Message-ID: <4EDCC6D3.4090100@cornell.edu> Date: Sat, 10 Dec 2011 01:40:00 -0000 From: Ken Brown User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin-xfree@cygwin.com Subject: Re: Problems with emacs built against gtk3 References: <4ED03512.7080607@cornell.edu> <4ED0EC50.4090300@cornell.edu> <1322625099.6420.9.camel@YAAKOV04> <4ED6390C.2040708@cornell.edu> <4ED807FA.7050700@cornell.edu> <1322822150.6352.13.camel@YAAKOV04> <4ED8CC12.5050607@cornell.edu> <1323043980.1644.6.camel@YAAKOV04> <4EDC21E3.8070704@cornell.edu> In-Reply-To: <4EDC21E3.8070704@cornell.edu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: 2011-12/txt/msg00021.txt.bz2 On 12/4/2011 8:44 PM, Ken Brown wrote: > On 12/4/2011 7:13 PM, Yaakov (Cygwin/X) wrote: >> On Fri, 2011-12-02 at 08:01 -0500, Ken Brown wrote: >>> This doesn't do it. Emacs still dies after a short time. I don't know >>> if that means that there's something else going on, but I'll retest it >>> after you package gvfs. In the meantime, I'll continue with my >>> workaround of setting GSETTINGS_BACKEND=memory. >>> >>> In case you (or anyone else) wants to experiment with this, you can get >>> my build of the emacs-24 pretest by running >>> >>> setup.exe -K http://www.math.cornell.edu/~kbrown/kbrown.gpg >>> >>> and adding http://www.math.cornell.edu/~kbrown to the list of mirrors. >> >> WJFFM, but I'll get on that gvfs ITP right away. It looks like I also >> need to repackage pango1.0 to remove everyone's old pango.modules file. >> >> But despite your subject line, the binaries there are clearly gtk2 >> based. Was that intended? > > No, I made a mistake in my configure arguments. I put `--with-x=gtk3' > instead of `--with-x-toolkit=gtk3', so emacs used the default gtk2. I'll > rebuild it. I've rebuilt emacs and am now definitely using gtk3. I've also installed the latest Cygwin snapshot. I tried your suggested workaround again (export GIO_USE_VFS=local) and it still doesn't work for me, but the symptoms are different: emacs doesn't die, but it freezes as soon as I try to list a directory with the command `d'. [This runs `ls' in a subprocess.] I then went back to my GSETTINGS_BACKEND=memory workaround and noticed something new: If I run emacs in my normal way, with "emacs.geometry: 82x36+340+40" in .Xdefaults, I get the following error message: 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. But if I remove the geometry setting from .Xdefaults, emacs seems to work fine. It's probably not worth pursuing these new problems until gvfs is ready, but I mentioned them in case they suggest to you that something is going on aside from the missing gvfs. The gtk3 build of emacs is available in the same place as before if you want to try it. Ken -- 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/