From: Lars Ingebrigtsen <larsi@gnus.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: search-invisible and friends
Date: Fri, 11 Sep 2020 13:46:10 +0200 [thread overview]
Message-ID: <87v9gkzgcd.fsf@gnus.org> (raw)
In-Reply-To: <CAP_d_8XjHbeSBSZNMdi92+pTqdWMgC9OKT2C3kn2RAkV8C4zvQ@mail.gmail.com> (Yuri Khan's message of "Fri, 11 Sep 2020 12:35:53 +0700")
Yuri Khan <yuri.v.khan@gmail.com> writes:
> The ‘display’ property can replace buffer text with a different string
> or an image for purposes of display. Maybe it makes sense to have a
> property that can similarly specify a different string for purposes of
> search? A property that can replace buffer text with a different
> string or a waveform for purposes of text-to-speech?
Oh, that's smart and even more general. Yes, I like it.
> A mode that replaces one word with another could decide which aspects
> (display, search and/or text-to-speech) it wants to affect and how.
Yup.
If the new text property is, say, `search', we could also have
special values like `ignore' to say that there is no alternative
(search) text, and `display', which means that if it's a textual
replacing display property, then isearch should use that text as the
search.
Like
(propertize "foo" 'display "bar" 'search 'display)
Or perhaps that's too complicated.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-11 11:46 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 [this message]
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=87v9gkzgcd.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yuri.v.khan@gmail.com \
/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).