From: David Caldwell <david@porkrind.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 754@emacsbugs.donarmstrong.com
Subject: bug#754: Can't cancel dabbrev-expand (M-/) with C-g
Date: Fri, 09 Jan 2009 20:41:51 -0800 [thread overview]
Message-ID: <4968270F.4000105@porkrind.org> (raw)
In-Reply-To: <48ADC243.40104@porkrind.org>
David Caldwell wrote:
> Chong Yidong wrote:
>>> If I have many buffers open (284 at the moment) and if I run
>>> dabbrev-expand (M-/) to expand the word under my buffers then it
>>> searches through every buffer and takes an understandably long
>>> time. If I mispelled the word fragment then it never has a hope of
>>> finding it and I'd like to cancel the operation. But C-g does not work
>>> for some reason and so I have to wait a good 5 to 10 seconds for it to
>>> finish scanning all my buffers. This gets very frustrating after the
>>> third or fourth time.
>>
>> I don't see why C-g wouldn't work here.
After further testing, I believe this is not really a bug in dabbrev.
C-g *does* cancel the operation, it's just that sometimes there is a
large lag before it cancels (though in my current tests I've never had
it go beyond 2 seconds). I have a ton of buffers open right this moment
and fulling scan them takes 15 to 20 seconds, so I can definitely tell
that it's canceling.
The 1 to 2 second lag is still a little frustrating, but it's much
better than the originally reported 5 to 10 second lag. I wonder if it
has to do with how the Mac handles the quit signal in windowed mode...
-David
next prev parent reply other threads:[~2009-01-10 4:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 15:48 bug#754: Can't cancel dabbrev-expand (M-/) with C-g Chong Yidong
2008-08-21 19:30 ` David Caldwell
2009-01-10 4:41 ` David Caldwell [this message]
2011-07-06 17:49 ` Lars Magne Ingebrigtsen
2011-07-06 18:05 ` David Caldwell
2011-07-07 17:53 ` Lars Magne Ingebrigtsen
2011-07-07 18:29 ` David Caldwell
-- strict thread matches above, loose matches on Subject: below --
2008-08-20 23:38 David Caldwell
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4968270F.4000105@porkrind.org \
--to=david@porkrind.org \
--cc=754@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.