From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 8686@debbugs.gnu.org
Subject: bug#8686: 24.0.50; `re-search-backward' does not respect `search-invisible'
Date: Thu, 28 Apr 2016 06:51:51 -0700 (PDT) [thread overview]
Message-ID: <b7b51ab0-8375-439d-80e8-3fd9e926e6f6@default> (raw)
In-Reply-To: <87k2jiovq2.fsf@gnus.org>
> > My impression is that `re-search-backward' and `*-forward' do not
> > respect `search-invisible'. This makes it difficult if not impossible
> > to use them in code to not find matches in hidden text. Why would this
> > variable be respected only in the Isearch Lisp code? What am I missing?
>
> Well, `search-invisible' is documented as only applying to interactive
> searches:
>
> ----
>
> search-invisible is a variable defined in 'isearch.el'.
> Its value is 'open'
>
> Documentation:
> If t incremental search/query-replace can match hidden text.
> A nil value means don't match invisible text.
>
> ----
>
> If you want code not to match invisible text, you have to make your code
> check for the visibility. Closing.
I don't think this is correct. Did you check whether it
truly works only for interactive use? It is a general
test, used in multiple places now (including `perform-replace').
prev parent reply other threads:[~2016-04-28 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 22:09 bug#8686: 24.0.50; `re-search-backward' does not respect `search-invisible' Drew Adams
2011-05-18 0:05 ` Stefan Monnier
2011-05-18 0:38 ` Drew Adams
2011-05-18 0:51 ` Stefan Monnier
2011-05-18 1:15 ` Lennart Borgman
2011-05-18 2:18 ` Drew Adams
2011-05-18 9:57 ` Lennart Borgman
2011-05-18 12:13 ` Stefan Monnier
2011-05-18 13:12 ` Lennart Borgman
2011-05-18 14:32 ` Drew Adams
2016-04-28 10:48 ` Lars Ingebrigtsen
2016-04-28 13:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b7b51ab0-8375-439d-80e8-3fd9e926e6f6@default \
--to=drew.adams@oracle.com \
--cc=8686@debbugs.gnu.org \
--cc=larsi@gnus.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 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.