unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: juri@jurta.org, emacs-devel@gnu.org
Subject: Re: isearch highlighting
Date: Tue, 11 Jan 2005 09:30:13 -0500	[thread overview]
Message-ID: <E1CoN2D-0000ke-Hf@fencepost.gnu.org> (raw)
In-Reply-To: <87y8f2gu45.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 09 Jan 2005 16:40:27 -0500)

    > Is it worth doing this now considering that the default value of
    > lazy-highlight-max-at-a-time (20) already provides quite good
    > responsiveness of isearch to key presses.

    If it's responsive enough, then it won't be interrupted by while-no-input.

That is not entirely true.  If it spends even a tiny amount of time
being busy, then it can sometimes be interrupted by while-no-input.
So we would need to do the work to make it use while-no-input
correctly, even if those cases are rather rare.

What does it need to do?  Any input character that triggers
while-no-input will certainly be intepreted by the search command
loop.  Most of the time, this will change the search string.

  reply	other threads:[~2005-01-11 14:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-10  2:06 isearch highlighting Juri Linkov
2004-12-10  3:21 ` Stefan Monnier
2004-12-10  5:22   ` Juri Linkov
2004-12-13 19:51 ` Richard Stallman
2004-12-14 10:27   ` Juri Linkov
2004-12-15 14:58     ` Richard Stallman
2004-12-17 15:29   ` Juri Linkov
2004-12-20 10:56     ` Richard Stallman
2004-12-20 20:57       ` Juri Linkov
2005-01-06  7:54         ` Juri Linkov
2005-01-09  3:23           ` Richard Stallman
2005-01-09 21:40           ` Stefan Monnier
2005-01-11 14:30             ` Richard Stallman [this message]
2005-01-12  1:52               ` Juri Linkov
  -- strict thread matches above, loose matches on Subject: below --
2004-12-10  7:00 klaus.berndl

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1CoN2D-0000ke-Hf@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).