From: David Kastrup <dak@gnu.org>
Cc: Lennart Borgman <lennart.borgman.073@student.lu.se>,
teirllm@dms.auburn.edu, emacs-devel@gnu.org
Subject: Re: Todays exercise of sanity (or does "see" really match "not"?)
Date: Mon, 21 Mar 2005 21:18:42 +0100 [thread overview]
Message-ID: <x5ll8glplp.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87hdj4vppf.fsf@jurta.org> (Juri Linkov's message of "Mon, 21 Mar 2005 21:27:21 +0200")
Juri Linkov <juri@jurta.org> writes:
> "Lennart Borgman" <lennart.borgman.073@student.lu.se> writes:
>> From: "Luc Teirlinck" <teirllm@dms.auburn.edu>
>>> I guess that you have Info-hide-note-references enabled. The reason
>>> why it stops on "see" is that the actual text in the buffer is:
>>> (*note Character Sets::). and note matches "not".
>>
>> Thanks. I am feeling better.
>
> The text "*note " has the `display' text property with the string
> "see " which is displayed instead of the original text. The
> function `isearch-range-invisible' (which is used by Info search)
> doesn't pay attention to the `display' property. It processes only
> the `invisible' property. It works the same in all Emacs buffers
> with the `display' property (in `image-mode', `w3m' mode, etc.)
> where it finds the text not visible on the screen.
>
> How to handle this situation is not clear. Should isearch find the
> displayed text as a contiguous part of the search space?
>
> The simplest solution is to treat the `display' property like
> `invisible' property and to skip the text displayed over the
> original text.
No, no, no. preview-latex is one such application, and it is
essential that the text remains searchable (it will get autoopened if
point is inside of it). It's overlays it uses instead of text
properties, but that does not change the underlying basics. If we
want some text to be impervious to search, you can
a) make it a single character, and so point will never be inside
b) declare a special property that makes this character not match for
searches.
But that will also break things like ^.*$, so it would probably be
better to use some otherwise unused character and adorn it with proper
character class and syntax.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-03-21 20:18 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 13:20 Todays exercise of sanity (or does "see" really match "not"?) Lennart Borgman
2005-03-21 13:49 ` Luc Teirlinck
2005-03-21 14:00 ` Lennart Borgman
2005-03-21 19:27 ` Juri Linkov
2005-03-21 20:18 ` David Kastrup [this message]
2005-03-22 13:57 ` Richard Stallman
2005-03-22 14:46 ` David Kastrup
2005-03-22 17:29 ` Juri Linkov
2005-03-22 22:22 ` David Kastrup
2005-03-23 6:21 ` Richard Stallman
2005-03-23 13:08 ` Juri Linkov
2005-03-23 14:19 ` Luc Teirlinck
2005-03-23 15:19 ` Juri Linkov
2005-03-23 17:03 ` Luc Teirlinck
2005-03-23 20:21 ` Juri Linkov
2005-03-23 20:33 ` Stefan Monnier
2005-03-23 21:16 ` Luc Teirlinck
2005-03-23 21:42 ` Luc Teirlinck
2005-03-23 22:54 ` Kim F. Storm
2005-03-24 1:18 ` Luc Teirlinck
2005-03-25 6:42 ` Richard Stallman
2005-03-23 21:44 ` Drew Adams
2005-03-24 0:21 ` Juri Linkov
2005-03-24 1:12 ` Luc Teirlinck
2005-03-25 6:41 ` Richard Stallman
2005-03-23 21:30 ` Luc Teirlinck
2005-03-24 5:18 ` Richard Stallman
2005-03-23 20:26 ` Richard Stallman
2005-03-24 0:19 ` Juri Linkov
2005-03-25 6:42 ` Richard Stallman
2005-03-23 0:59 ` Richard Stallman
2005-03-23 1:10 ` David Kastrup
2005-03-23 10:07 ` Kim F. Storm
2005-03-23 11:01 ` David Kastrup
2005-03-23 22:57 ` Kim F. Storm
2005-03-23 23:00 ` Kim F. Storm
2005-03-23 23:57 ` David Kastrup
2005-03-25 6:42 ` Richard Stallman
2005-03-23 12:59 ` Juri Linkov
2005-08-10 0:19 ` Drew Adams
2005-08-10 3:42 ` Eli Zaretskii
2005-08-10 4:19 ` Drew Adams
2005-08-10 4:03 ` Juri Linkov
2005-03-21 23:20 ` Drew Adams
2005-03-22 4:57 ` Miles Bader
2005-03-22 10:51 ` David Kastrup
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5ll8glplp.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=teirllm@dms.auburn.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.