[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: emacs C-g C-g
From: |
Roland McGrath |
Subject: |
Re: emacs C-g C-g |
Date: |
Sat, 13 Mar 2004 22:15:12 -0500 (EST) |
One has always seen this from time to time on any system, and I do see it
once in a while on Linux. I believe this happens when a second SIGINT is
received while quit-flag is still set. That may just mean that the whole
path of the first signal getting handled, the quit getting up to Lisp and
being handled, is a bit slower so that it's done all done by the time you
do a second C-c and a second SIGINT interrupts that path. Or it could mean
something else like the original signal is delayed in reaching Emacs for
some reason so that it appears to have taken a long time to process.
- emacs C-g C-g, Marcus Brinkmann, 2004/03/13
- Re: emacs C-g C-g,
Roland McGrath <=
- Re: emacs C-g C-g, Thomas Bushnell, BSG, 2004/03/14
- Re: emacs C-g C-g, Alfred M. Szmidt, 2004/03/14
- Re: emacs C-g C-g, Thomas Bushnell, BSG, 2004/03/14
- Re: emacs C-g C-g, Alfred M. Szmidt, 2004/03/14
- Re: emacs C-g C-g, Thomas Bushnell, BSG, 2004/03/14
- Re: emacs C-g C-g, Alfred M. Szmidt, 2004/03/14
- Re: emacs C-g C-g, Thomas Bushnell, BSG, 2004/03/14
- Re: emacs C-g C-g, Alfred M. Szmidt, 2004/03/14