unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9918@debbugs.gnu.org
Subject: bug#9918: 24.0.90; lazy-highlighting in Info mode
Date: Thu, 03 Nov 2011 21:56:20 +0200	[thread overview]
Message-ID: <87sjm5f09n.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0gA38VLUJuExL3U5xz3Ld1ubzEee8kqwV3i43yOAHaDiw@mail.gmail.com> (Dani Moncayo's message of "Thu, 3 Nov 2011 20:24:13 +0100")

> * "Isearch: foo"
> * "Isearch: foo [failing]"
> * "Isearch: foo [failing, overwrapped]"
> * "Isearch: foo [failing, initial node]"

Yes, moving all prefixes into suffixes and always displaying the
search string at the fixed position in the message avoids this problem
where prefixes shift the search string to the right in the message, so
its position jumps left and right during Isearch depending on the length
of the composite prefix that makes more difficult to concentrate on
the search string displayed in the message.

> This approach raises a question: how to show the _error_ flags to make
> them distinguishable from the _informative_ flags?
>
> One possibility is to show all the flags the same way.  After all, the
> fact that the errors deactivate the Isearch should be enough for the
> user to know what's going on, I think.

I think to show all the flags the same way is better.

Of course, this should be postponed for 24.2.  But now I'd like to fix
the original problem you reported.  I think we should remove
`(not isearch-error)' from `isearch-lazy-highlight-new-loop'.
This is over-optimization.  It can't know for sure beforehand
whether lazy-highlighting will be able to highlight matches
even when isearch-error is non-nil.

=== modified file 'lisp/isearch.el'
--- lisp/isearch.el	2011-10-30 01:56:03 +0000
+++ lisp/isearch.el	2011-11-03 19:55:07 +0000
@@ -2674,7 +2721,6 @@ (defun isearch-lazy-highlight-new-loop (
     ;; something important did indeed change
     (lazy-highlight-cleanup t) ;kill old loop & remove overlays
     (setq isearch-lazy-highlight-error isearch-error)
-    (when (not isearch-error)
       (setq isearch-lazy-highlight-start-limit beg
 	    isearch-lazy-highlight-end-limit end)
       (setq isearch-lazy-highlight-window       (selected-window)
@@ -2692,7 +2738,7 @@ (defun isearch-lazy-highlight-new-loop (
       (unless (equal isearch-string "")
 	(setq isearch-lazy-highlight-timer
 	      (run-with-idle-timer lazy-highlight-initial-delay nil
-				   'isearch-lazy-highlight-update))))))
+				   'isearch-lazy-highlight-update)))))
 
 (defun isearch-lazy-highlight-search ()
   "Search ahead for the next or previous match, for lazy highlighting.






  reply	other threads:[~2011-11-03 19:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 14:46 bug#9918: 24.0.90; lazy-highlighting in Info mode Dani Moncayo
2011-10-31 20:43 ` Eli Zaretskii
2011-10-31 21:00   ` Drew Adams
2011-10-31 21:08   ` Dani Moncayo
2011-10-31 21:13     ` Drew Adams
2011-10-31 21:30       ` Dani Moncayo
2011-10-31 21:39         ` Drew Adams
2011-10-31 23:15 ` Juri Linkov
2011-11-01  9:39   ` Dani Moncayo
2011-11-01 10:21     ` Dani Moncayo
2011-11-01 23:07     ` Juri Linkov
2011-11-02  7:54       ` Dani Moncayo
2011-11-03  9:07         ` Juri Linkov
2011-11-03  9:44           ` Dani Moncayo
2011-11-03 19:24             ` Dani Moncayo
2011-11-03 19:56               ` Juri Linkov [this message]
2011-11-03 20:43                 ` Dani Moncayo
2011-11-03 21:11                   ` Juri Linkov
2011-12-01  7:45                     ` Juri Linkov
2011-11-19 21:04                 ` Juri Linkov

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=87sjm5f09n.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=9918@debbugs.gnu.org \
    --cc=dmoncayo@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 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).