From: Juri Linkov <juri@jurta.org>
Cc: lennart.borgman.073@student.lu.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Todays exercise of sanity (or does "see" really match "not"?)
Date: Wed, 23 Mar 2005 14:59:27 +0200 [thread overview]
Message-ID: <87br9a7c28.fsf@jurta.org> (raw)
In-Reply-To: <m3ll8ed6b8.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Wed, 23 Mar 2005 11:07:07 +0100")
storm@cua.dk (Kim F. Storm) writes:
> Instead we can explicitly put an inivisible property together with the
> display property on a priece of "hidden" text which should be ignored
> by searches. That need a little work to check all uses of display
> properties, but it doesn't break any old code relying on the current
> behaviour.
Yes, there are existing packages where finding the underlying text
might be useful. For example, in w3m images are placed over the text
extracted from the ALT="" image HTML attribute. Finding it with isearch
seems useful.
> I don't know whether it actually works to put both invisible and
> display on some text (with the effect of showing the image and
> ignoring the under-laying text). Would someone make some examples
> to check it?
The `display' property takes precedence over the `invisible' property:
(progn
(goto-char (point-min))
(insert "abcdefghi\n")
(add-text-properties (- (point) 9) (- (point) 2)
`(display ,(create-image (expand-file-name "gnu.xpm" data-directory) 'xpm)
invisible t))
(goto-char (point-min))
(search-forward "def"))
And the image is visible. Incremental search skips the underlying text,
but low-level search functions find it.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2005-03-23 12:59 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
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 [this message]
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=87br9a7c28.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=rms@gnu.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 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.