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 11:31:34 -0800 (PST) [thread overview]
Message-ID: <201001151931.o0FJVYGR020661@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87pr5brx7e.fsf@stupidchicken.com> (Chong Yidong's message of "Fri, 15 Jan 2010 14:21:09 -0500")
Chong Yidong <cyd@stupidchicken.com> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
>
> > 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.
>
> How about issuing a warning when a new GTK frame is created?
When?
Every time a GTK frame is created?
That would be very annoying.
After we've had a disconnect? I don't think there's a way to detect
that situation reliably.
Having the warning issued when starting emacs --daemon has the advantage
that it's only done once per session. Sure, it does not cover all cases
(you still run into trouble by doing emacs -nw -f server-start then
create a GTK frame), but it does cover the most frequent use-case.
next prev parent reply other threads:[~2010-01-15 19:31 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
2010-01-15 19:21 ` Chong Yidong
2010-01-15 19:31 ` Dan Nicolaescu [this message]
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=201001151931.o0FJVYGR020661@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).