public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: Problems with emacs built against gtk3
Date: Sat, 10 Dec 2011 01:40:00 -0000	[thread overview]
Message-ID: <4EDCC6D3.4090100@cornell.edu> (raw)
In-Reply-To: <4EDC21E3.8070704@cornell.edu>

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 `<ctrl-x>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/


  reply	other threads:[~2011-12-05 13:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26  0:39 Ken Brown
2011-11-26 13:40 ` Ken Brown
2011-11-30  3:52   ` Yaakov (Cygwin/X)
2011-11-30 10:25     ` Pavel Holejsovsky
2011-11-30 11:54       ` Yaakov (Cygwin/X)
2011-11-30 12:27         ` Ken Brown
2011-12-10 12:14           ` nyc4bos
2011-12-13 18:51             ` Ken Brown
2011-11-30 14:09     ` Ken Brown
2011-12-02 10:36       ` Ken Brown
2011-12-02 13:01         ` Yaakov (Cygwin/X)
2011-12-03  2:30           ` Ken Brown
2011-12-05  0:22             ` Yaakov (Cygwin/X)
2011-12-05 13:28               ` Ken Brown
2011-12-10  1:40                 ` Ken Brown [this message]
2012-04-03 21:13               ` Ken Brown
2012-04-03 22:30                 ` Yaakov (Cygwin/X)
2012-04-04  1:53                   ` Ken Brown
2012-04-04  3:56                     ` Yaakov (Cygwin/X)
2012-04-04 14:15                       ` Ken Brown
2012-04-04 22:13                         ` Yaakov (Cygwin/X)
2012-04-06 17:22                           ` Problems with emacs built with gsettings support [was: Problems with emacs built against gtk3] Ken Brown
2011-12-05  0:13     ` Problems with emacs built against gtk3 nyc4bos
2011-11-28  8:49 Angelo Graziosi
2011-12-03 15:18 ` Angelo Graziosi
2011-12-05  0:38   ` 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=4EDCC6D3.4090100@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: link
Be 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).