[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#5386: 23.1.91;
From: |
Dirk-Jan C . Binnema |
Subject: |
bug#5386: 23.1.91; |
Date: |
Fri, 15 Jan 2010 21:41:57 +0200 |
User-agent: |
Wanderlust/2.15.6 (Almost Unreal) Emacs/23.1 Mule/6.0 (HANACHIRUSATO) |
>>>>> "CYD" == 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.
CYD> How about issuing a warning when a new GTK frame is created?
Maybe this could be combined with your idea to auto-kill emacs, but behind
some --exit-with-session command-line parameter?
Anyhow, reading the GTK bug, I can really see how that could lead to an emacs
instance taking so much CPU, that seems like an emacs bug or?
Best wishes,
Dirk,
--
Dirk-Jan C. Binnema Helsinki, Finland
e:djcb@djcbsoftware.nl w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C
bug#5386: 23.1.91;, Jan Djärv, 2010/01/15