unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Cc: "Jan Djärv" <jan.h.d@swipnet.se>
Subject: Re: daemon mode breakage
Date: Wed, 20 Oct 2010 23:01:22 +0200	[thread overview]
Message-ID: <87sk00d1el.fsf@telefonica.net> (raw)
In-Reply-To: 4CBF578D.4040800@swipnet.se

Jan Djärv <jan.h.d@swipnet.se> writes:

> Chong Yidong skrev 2010-10-20 18.19:
>> Dan Nicolaescu<dann@gnu.org>  writes:
>>
>>>> But if the connection is rudely dropped, then when I attempt to re-connect
>>>> I get a blank window.
>>>
>>> This is a bug in Gtk+.
>>> http://bugzilla.gnome.org/show_bug.cgi?id=85715.  (emacs/etc/PROBLEMS
>>> has a note about this too).
>>> If you intend to use the daemon mode, it's better to compile emacs
>>> using the lucid toolkit.
>>> It doesn't look like the Gtk+ bug will ever be fixed so...
>>
>> Is there any way for us to detect when this happens?  If so, we could
>> make Emacs print an error message with the bugzilla.gnome.org bug url.
>
> I haven't looked into it much, but as Emacs is in daemon mode, chances
> are that nobody will see the output.

IIRC, creating the first frame works fine. It is when closing the frame
or creating a new one when the problem pops out.

Yes, I came to the list with that same problem a few years ago.




  reply	other threads:[~2010-10-20 21:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 12:34 daemon mode breakage Neal Becker
2010-10-20 14:07 ` Dan Nicolaescu
2010-10-20 14:58   ` Scot Becker
2010-10-20 15:27     ` Dan Nicolaescu
2010-10-20 15:32     ` Jan Djärv
2010-10-20 16:13       ` Scot Becker
2010-10-20 16:19   ` Chong Yidong
2010-10-20 20:19     ` Dan Nicolaescu
2010-10-20 20:56     ` Jan Djärv
2010-10-20 21:01       ` Óscar Fuentes [this message]
2010-10-20 23:21       ` Sebastian Rose

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sk00d1el.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).