From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: search-invisible and friends
Date: Thu, 10 Sep 2020 11:03:06 -0400 [thread overview]
Message-ID: <jwvd02titbt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83a6xxk8nj.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 10 Sep 2020 17:29:04 +0300")
>> Ah, yeah, that sounds quite useful and natural. We could even have a
>> standard property like `no-search' that could be part of the default
>> `search-invisible' value, so that modes can easily mark out regions that
>> shouldn't be searched for. In which case, the whole `display' thing
>> becomes moot -- in my mode, I could just slap the `no-search' property
>> on all the image display bits that I want isearch to avoid?
> Yes, those were my thoughts.
It'd be good to have such a `no-search` property, but I think it's also
important to make the `search-invisible` automatically handle text
that's hidden by a `display` property, without having to add an explicit
`no-search`.
OTOH, maybe there could be unusual circumstances where it would make
sense to consider hidden text as "visible" (e.g. if the `display`
property replaces the text with something that looks very much like the
same text, tho maybe rendered a bit differently). So, maybe there
should be a value of `no-search` (or some other property) which says
"please do consider this text as visible even tho it's technically
hidden".
Stefan
next prev parent reply other threads:[~2020-09-10 15:03 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 12:39 search-invisible and friends Lars Ingebrigtsen
2020-09-09 14:43 ` Eli Zaretskii
2020-09-10 12:38 ` Lars Ingebrigtsen
2020-09-10 14:29 ` Eli Zaretskii
2020-09-10 15:03 ` Stefan Monnier [this message]
2020-09-10 18:11 ` Juri Linkov
2020-09-10 20:47 ` Stefan Monnier
2020-09-10 22:10 ` Ihor Radchenko
2020-09-10 22:55 ` Stefan Monnier
2020-09-11 1:03 ` Ihor Radchenko
2020-09-11 1:42 ` Stefan Monnier
2020-09-11 5:35 ` Yuri Khan
2020-09-11 11:46 ` Lars Ingebrigtsen
2020-09-11 12:29 ` Eli Zaretskii
2020-09-11 14:40 ` Lars Ingebrigtsen
2020-09-11 14:50 ` Eli Zaretskii
2020-09-11 14:56 ` Lars Ingebrigtsen
2020-09-11 15:14 ` Eli Zaretskii
2020-09-12 11:48 ` Lars Ingebrigtsen
2020-09-12 15:29 ` Stefan Monnier
2020-09-11 11:41 ` Lars Ingebrigtsen
2020-09-10 18:12 ` Drew Adams
2020-09-09 15:10 ` Stefan Monnier
2020-09-09 15:26 ` Eli Zaretskii
2020-09-09 16:11 ` Stefan Monnier
2020-09-09 16:25 ` Eli Zaretskii
2020-09-10 12:35 ` Lars Ingebrigtsen
2020-09-10 12:42 ` Eli Zaretskii
2020-09-10 13:21 ` Stefan Monnier
2020-09-10 14:42 ` Eli Zaretskii
2020-09-11 11:37 ` Lars Ingebrigtsen
2020-09-11 12:25 ` Eli Zaretskii
2020-09-09 18:48 ` Juri Linkov
2020-09-10 12:01 ` Lars Ingebrigtsen
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=jwvd02titbt.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 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).