From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: hariharanrangasamy@gmail.com, 26710@debbugs.gnu.org
Subject: bug#26710: Fwd: 25.2; project-find-regexp makes emacs use 100% cpu
Date: Wed, 03 May 2017 05:34:47 +0300 [thread overview]
Message-ID: <83wp9yhdmg.fsf@gnu.org> (raw)
In-Reply-To: <5d72a20b-30b5-51fd-fbc0-ca5fa95573f7@yandex.ru> (message from Dmitry Gutov on Wed, 3 May 2017 03:14:52 +0300)
> Cc: hariharanrangasamy@gmail.com, 26710@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Wed, 3 May 2017 03:14:52 +0300
>
> On 02.05.2017 20:26, Eli Zaretskii wrote:
>
> > The sentinel/filter won't be called at all if keyboard/mouse input is
> > available. Once they are called, if each call takes a long processing
> > time, the UI could feel sluggish, yes.
>
> Hmm, and if we're in "many calls, each of them fairly fast" situation?
Then there should be no problem with UI responsiveness.
> Sounds like the UI might be quite usable (but doing anything with it
> would slow down the processing of search results).
Correct.
prev parent reply other threads:[~2017-05-03 2:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a86zu3gf.fsf@hari-laptop.i-did-not-set--mail-host-address--so-tickle-me>
2017-04-29 8:55 ` bug#26710: Fwd: 25.2; project-find-regexp makes emacs use 100% cpu Hariharan Rangasamy
2017-04-29 17:00 ` Dmitry Gutov
2017-04-29 17:37 ` Eli Zaretskii
2017-04-30 4:13 ` Hariharan Rangasamy
2017-04-30 10:35 ` Dmitry Gutov
2017-04-30 18:47 ` Eli Zaretskii
2017-05-01 2:42 ` Dmitry Gutov
2017-05-01 7:20 ` Eli Zaretskii
2017-05-01 21:46 ` Dmitry Gutov
2017-05-02 7:15 ` Eli Zaretskii
2017-05-02 10:00 ` Dmitry Gutov
2017-05-02 17:26 ` Eli Zaretskii
2017-05-02 17:41 ` Eli Zaretskii
2017-05-03 0:14 ` Dmitry Gutov
2017-05-03 2:34 ` Eli Zaretskii [this message]
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=83wp9yhdmg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=26710@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=hariharanrangasamy@gmail.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.