unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Juri Linkov <juri@linkov.net>
Cc: bobf32@gmail.com, 64178@debbugs.gnu.org
Subject: bug#64178: replace-regexp ignoring value of org-search-invisible
Date: Thu, 22 Jun 2023 07:48:02 +0000	[thread overview]
Message-ID: <87ttv0c4zx.fsf@localhost> (raw)
In-Reply-To: <86ttv00z7c.fsf@mail.linkov.net>

Juri Linkov <juri@linkov.net> writes:

>> Ok. Then, it is not an Org mode bug.
>
> Actually, Isearch never supported zero-length invisible matches.
> The following condition was in isearch.el since day 1:
>
>   (defun isearch-range-invisible (beg end)
>     "Return t if all the text from BEG to END is invisible."
>     (when (/= beg end)
>
> So any zero-length match is deemed visible by Isearch.

Which is unexpected.
It is natural to expect that zero-width matches are considered invisible
when the surrounding text is invisible.

Also, is this documented anywhere?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  reply	other threads:[~2023-06-22  7:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 20:15 bug#64178: replace-regexp ignoring value of org-search-invisible bobf32
2023-06-20  8:50 ` Ihor Radchenko
2023-06-20 10:09   ` bobf32
2023-06-20 10:22     ` Ihor Radchenko
2023-06-20 20:48       ` bobf32
2023-06-20 21:02         ` Ihor Radchenko
2023-06-20 21:04           ` bobf32
2023-06-21 10:21             ` Ihor Radchenko
2023-06-21 15:50               ` Juri Linkov
2023-06-22  6:50               ` Juri Linkov
2023-06-22  7:48                 ` Ihor Radchenko [this message]
2023-06-22 16:52                   ` Juri Linkov
2023-06-23 10:46                     ` Ihor Radchenko

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=87ttv0c4zx.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=64178@debbugs.gnu.org \
    --cc=bobf32@gmail.com \
    --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).