GNU bug report logs - #17293
24.4.50; C-g often fails in minibuffer under X

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 17293 in the body.
You can then email your comments to 17293 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: raman <tv.raman.tv <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.4.50; C-g often fails in minibuffer under X
Date: Fri, 18 Apr 2014 09:04:50 -0700

I remember Stefan addressing this a while ago, but it appears to
bite me only when running under X.

Specifically:
When running under X (Ubuntu Precise) and using StumpWM  as the
window manager (neither of those specific bits might be relevant) 
often, if I have a minibuffer completion  up, hitting C-g does
not dismiss the minibuffer, I actually have to switch away from
the minibuffer and type M-x top-level to get emacs back to being normal.

Message #8 received at 17293 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: raman <tv.raman.tv <at> gmail.com>
Cc: 17293 <at> debbugs.gnu.org, "T. V. Raman" <raman <at> google.com>
Subject: Re: bug#17293: 24.4.50; C-g often fails in minibuffer under X
Date: Thu, 24 Apr 2014 16:05:31 -0400

> often, if I have a minibuffer completion  up, hitting C-g does
> not dismiss the minibuffer, I actually have to switch away from

If you're in the minibuffer, then C-g should normally dismiss the
minibuffer, yes.  Of course, we have the problem that C-g only does that
if it runs keyboard-quit (i.e. if Emacs was idle), and not if it signals
"quit" (i.e. Emacs was busy with something).

So apparently, there's been more cases where Emacs is "busy" (probably
just waiting in a sit-for or something).  So to fix this, we need to
figure out what that C-g interrupts.


        Stefan

Message #11 received at 17293 <at> debbugs.gnu.org (full text, mbox):

From: raman <at> google.com (T.V Raman)
To: monnier <at> iro.umontreal.ca
Cc: tv.raman.tv <at> gmail.com, 17293 <at> debbugs.gnu.org, raman <at> google.com
Subject: Re: bug#17293: 24.4.50; C-g often fails in minibuffer under X
Date: Thu, 24 Apr 2014 14:06:56 -0700

Stefan, Makes sense.

I've been chasing a separate problem in emacs  at work that is
keeping emacs busy --see below.

I run emacs-jabber to connect to Google Talk. 

I have a large number of contacts there -- order of magnitude
100s  -- many of whom constantly keep changing status.

emacs-jabber uses a continues fsm ping mechanism and if I leave
emacs idle ie dont touch the keyboard, profiler shows that emacs
is permanently busy in that handler.  I've been trying various
advice tricks to keep that fsm tick from happening except  when
jabber  roster is selected, and surprize surprize that got the
c-g problem to diminish -- I could not figure out why till I saw
your note today.

Stefan Monnier writes:
 > > often, if I have a minibuffer completion  up, hitting C-g does
 > > not dismiss the minibuffer, I actually have to switch away from
 > 
 > If you're in the minibuffer, then C-g should normally dismiss the
 > minibuffer, yes.  Of course, we have the problem that C-g only does that
 > if it runs keyboard-quit (i.e. if Emacs was idle), and not if it signals
 > "quit" (i.e. Emacs was busy with something).
 > 
 > So apparently, there's been more cases where Emacs is "busy" (probably
 > just waiting in a sit-for or something).  So to fix this, we need to
 > figure out what that C-g interrupts.
 > 
 > 
 >         Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.