From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: search-invisible and friends
Date: Thu, 10 Sep 2020 15:42:50 +0300 [thread overview]
Message-ID: <83een9kdkl.fsf@gnu.org> (raw)
In-Reply-To: <875z8l95cp.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 10 Sep 2020 14:35:50 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
> Date: Thu, 10 Sep 2020 14:35:50 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Right, but we wouldn't to re-implement the test in isearch.el, so the
> >> question is to find an existing function which gives us the answer.
> >
> > We'd need to write it, I think.
>
> So basically mash up this stuff into a convenient DEFUN?
>
> && !NILP (val = get_char_property_and_overlay
> (make_fixnum (PT), Qdisplay, selected_window,
> &overlay))
> && display_prop_intangible_p (val, overlay, PT, PT_BYTE)
Yes, something like that.
But what about 'display' properties on overlay strings? do we want to
support that as well?
> I also read the "Display Specs That Replace The Text" node in the
> manual, but I'm not quite sure what the relevance is here -- it talks
> about how (display) text properties are collated (i.e., merged over eq
> sequences of text), but does isearch have to deal with that?
The rest of the section makes a point of saying, for each display
property kind, whether it is replacing or not.
next prev parent reply other threads:[~2020-09-10 12:42 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
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 [this message]
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=83een9kdkl.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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).