From: Samuel Wales <samologist@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode@gnu.org
Subject: Re: [Bug] isearch errors when org-fold-core-style is 'overlays
Date: Thu, 29 Dec 2022 22:59:47 -0700 [thread overview]
Message-ID: <CAJcAo8t=RxpX--6B+hyvARU0PULTrWDtij8sGrRc0FhV62Jqyg@mail.gmail.com> (raw)
In-Reply-To: <875yduwnx1.fsf@localhost>
more below.
On 12/29/22, Ihor Radchenko <yantar92@posteo.net> wrote:
> Samuel Wales <samologist@gmail.com> writes:
>
>> possibly related: are links still not searchable with iserch without
>> being in reveal mode or similar? [9.4 here.)
>
> Unrelated.
> The reported issue is related to the new org-fold implementation.
ok didn't men to lower s/n.
tanks for your patience.
>
> The old issue with searching links is known. It is simply because
> isearch does not support searching inside invisible text. And links are
> abbreviated by applying invisible text property to the hidden parts.
>
> You either upgrade or set isearch-invisible to t.
i look forward to it if it is fixed. fwiw i vaguely thought the issue
was overlays or so, as the default value is 'open. but it sounds like
you are saying this was fixed in emacs or org. i do have a vague
inkling that it was fixed in future emacs or org.
>
> --
> 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>
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next prev parent reply other threads:[~2022-12-30 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 19:00 [Bug] isearch errors when org-fold-core-style is 'overlays Matt Lundin
2022-12-28 10:43 ` Ihor Radchenko
2022-12-29 2:21 ` Samuel Wales
2022-12-29 9:37 ` Ihor Radchenko
2022-12-30 5:59 ` Samuel Wales [this message]
2022-12-29 13:26 ` Ihor Radchenko
2023-01-16 9:32 ` 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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJcAo8t=RxpX--6B+hyvARU0PULTrWDtij8sGrRc0FhV62Jqyg@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.org \
--cc=yantar92@posteo.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/org-mode.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).