all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Ed Avis <eda@waniasset.com>
Cc: 28343@debbugs.gnu.org
Subject: bug#28343: 24.5; isearch highlighting slow - suppress for single space character
Date: Sun, 03 May 2020 03:41:08 +0200	[thread overview]
Message-ID: <87zhap23t7.fsf@stefankangas.se> (raw)
In-Reply-To: <863782u6we.fsf@waniasset.com> (Ed Avis's message of "Mon, 4 Sep 2017 10:53:21 +0100")

Ed Avis <eda@waniasset.com> writes:

> Run Emacs in a fairly large terminal, say 200x200 characters.  Go to the
> end of a buffer with some text in it (long enough to fill the screen)
> and do C-r SPACE.  This is an isearch backwards for the space character.
> If you have highlighting turned on, Emacs then starts highlighting
> backwards all the space characters in the buffer.  But this can be slow,
> a noticeable few seconds even on a fast machine.  (I think it depends on
> the vagaries of memory management and possibly Lisp compiling, since
> it's not always quite that bad; a second attempt takes only about half a
> second.  But still it seems a long time.)
>
> A small tweak to isearch would suppress the highlighting when what has
> been typed so far is just a space character.  If the user types space
> and then C-s or C-r again, to indicate that he or she really does want
> to search for single spaces, then you can highlight at that point of
> course.

I'm unable to reproduce this on Emacs 28.0.50 (current master).

Are you still seeing this on a recent version of Emacs?

If I don't hear back from you within a couple of weeks, I'll just
close this bug as unreproducible.  Thanks in advance.

Best regards,
Stefan Kangas





  reply	other threads:[~2020-05-03  1:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-04  9:53 bug#28343: 24.5; isearch highlighting slow - suppress for single space character Ed Avis
2020-05-03  1:41 ` Stefan Kangas [this message]
2020-05-03 21:25   ` Ed Avis
2020-05-03 21:58     ` Stefan Kangas

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=87zhap23t7.fsf@stefankangas.se \
    --to=stefan@marxist.se \
    --cc=28343@debbugs.gnu.org \
    --cc=eda@waniasset.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.