unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: 33446-done@debbugs.gnu.org
Subject: bug#33446: 26; `isearch-lazy-highlight-update' in MASTER today
Date: Wed, 21 Nov 2018 14:50:56 -0800 (PST)	[thread overview]
Message-ID: <0ba62b0e-d257-405d-a358-cee30725f4c6@default> (raw)
In-Reply-To: <87y39mdpd1.fsf@mail.linkov.net>

> > Yes, I guessed that finally.  Beyond that, I think it's
> > not intended to be invoked outside of search (i.e.,
> > when `isearch-mode' is nil).  That was my mistake:
> > invoking it in a command that can be used during Isearch
> > or not.
> >
> > I know that wasn't intended as part of the Isearch
> > design.  Now I test for it and avoid calling `i-l-h-u'.
> >
> > (But it might not hurt for `i-l-h-u' itself to test and
> > do nothing if `isearch-mode' is nil.  I'm not requesting
> > that, however.)
> 
> isearch-lazy-highlight-update can't test for non-nil
> isearch-mode, because it's also used in non-isearch cases
> like in query-replace where isearch-mode is nil.

Oh, right.  Is there some other state it can test
for?  As you said, it can only be expected to be
used (i.e., to work) when within an appropriate
context (e.g. following xyz).

> > Feel free to close this bug, if you like.  It's not
> > clear to me whether any code change is needed.
> 
> I thought that your request was for using
> isearch-lazy-highlight-window as an argument
> of window functions in isearch-lazy-highlight-update.
> If you need this, then please create a new request,
> and I'm closing this one.

That's fine.  Thx.





      reply	other threads:[~2018-11-21 22:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20 19:47 bug#33446: 26; `isearch-lazy-highlight-update' in MASTER today Drew Adams
2018-11-20 21:10 ` Drew Adams
2018-11-20 23:14   ` Juri Linkov
2018-11-20 23:47     ` Drew Adams
2018-11-21 22:42       ` Juri Linkov
2018-11-21 22:50         ` Drew Adams [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

  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=0ba62b0e-d257-405d-a358-cee30725f4c6@default \
    --to=drew.adams@oracle.com \
    --cc=33446-done@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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).