From: Dan Nicolaescu <dann@ics.uci.edu>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: "Dirk-Jan C. Binnema" <djcb@djcbsoftware.nl>, 5386@debbugs.gnu.org
Subject: bug#5386: 23.1.91;
Date: Fri, 15 Jan 2010 10:13:31 -0800 (PST) [thread overview]
Message-ID: <201001151813.o0FIDV0S017779@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87k4vjjl7i.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 15 Jan 2010 13:07:29 -0500")
Chong Yidong <cyd@stupidchicken.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> > Given that we get this bug report all the time, how about adding a
> > printf when using --daemon when using the Gtk toolkit that describes
> > the problem, and gives a pointer to the bug report? This will make
> > people aware something might happen at the time they start emacs
> > --daemon.
>
> But the user may only want to use terminal clients.
That is fine, it's just a warning.
And it has the added benefit that users are aware of what might go on,
and it also adds a bit of pressure on the Gtk people to fix the bug.
> Another idea for a workaround---assuming a GTK frame has been created,
> maybe we could use the X session code (emacs-save-session-functions) to
> kill Emacs when the X session ends. Opinions? (Admittedly this won't
> cover all use cases, and is a bit of a hack, but it's something...)
That would be very bad: most of the time the session works just fine
using emacsclient -t. Losing state in that case would be very bad.
next prev parent reply other threads:[~2010-01-15 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 20:45 bug#5386: 23.1.91; Dirk-Jan C. Binnema
2010-01-15 16:50 ` Chong Yidong
2010-01-15 17:37 ` Dan Nicolaescu
2010-01-15 18:07 ` Chong Yidong
2010-01-15 18:13 ` Dan Nicolaescu [this message]
2010-01-15 19:21 ` Chong Yidong
2010-01-15 19:31 ` Dan Nicolaescu
2010-01-15 19:41 ` Dirk-Jan C. Binnema
2010-01-15 17:11 ` Jan Djärv
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=201001151813.o0FIDV0S017779@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=5386@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=djcb@djcbsoftware.nl \
/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).