From: Dan Nicolaescu <dann@gnu.org>
To: Scot Becker <scot.becker@gmail.com>
Cc: Neal Becker <ndbecker2@gmail.com>, emacs-devel@gnu.org
Subject: Re: daemon mode breakage
Date: Wed, 20 Oct 2010 11:27:06 -0400 [thread overview]
Message-ID: <yxqy69sanqt.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTinLuN68GGoNeJQeebwt4hN_qi_qhn4-CQbZP507@mail.gmail.com> (Scot Becker's message of "Wed\, 20 Oct 2010 15\:58\:53 +0100")
Scot Becker <scot.becker@gmail.com> writes:
> Out of curiosity (I experience this bug too) what do you have to give up if you
> compile with Lucid?
The toolbar, scroll bar, dialogs and the menus use different widgets,
so they don't look as spiffy, but no core functionality is lost.
> I assume that anti-aliased fonts would go.
No.
> Do you loose the ability to use proportional fonts as well
No.
>
>
>
> On Wed, Oct 20, 2010 at 3:07 PM, Dan Nicolaescu <dann@gnu.org> wrote:
>
> Neal Becker <ndbecker2@gmail.com> writes:
>
> > emacs-23.2.1 fedora 13 x86_64
> >
> > I start emacs --daemon on a remote
> >
> > If I connect with emacsclient -c , and then cleanly disconnect, (e.g.,
> C-x
> > C-c), I can subsequently re-connect with emacsclient -c.
> >
> > 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...
next prev parent reply other threads:[~2010-10-20 15:27 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxqy69sanqt.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ndbecker2@gmail.com \
--cc=scot.becker@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.