From: Perry Smith <pedzsan@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Text/overlay property to hide buffer contents from lisp?
Date: Sun, 10 Apr 2011 12:51:53 -0500 [thread overview]
Message-ID: <D4C1E513-4171-430C-AE5C-687B586A896D@gmail.com> (raw)
In-Reply-To: <4DA1D488.1070900@easy-emacs.de>
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
On Apr 10, 2011, at 11:02 AM, Andreas Röhler wrote:
> Am 10.04.2011 10:49, schrieb Tom:
>> I know there are the `invisible' and `intangible' properties to
>> hide parts of the buffer from the user, but these hidden regions
>> are apparently not hidden from lisp commands like
>> query-replace-regexp.
>>
>
> If query-replacs goes into `intangible' sounds like a bug for me.
>
> Whilst with `invisible' it seems reasonable. Emacs don't need eyes... :)
`intangible' is a new concept to me. For anyone else trying to follow along, intangible is documented in the Elisp manual (but not in Emacs' Concept Index which is the first place I looked).
One thing it mentions:
> When the variable `inhibit-point-motion-hooks' is non-`nil', the
> `intangible' property is ignored.
I assume that is not set but it might be.
From grep'ing the source and looking at what is in the Elisp manual and the comments in the code, I too would expect searches to not enter intangible areas. The code also mentioned "sticky forward" and "sticky backward" -- not sure what that is (yet) but that might be affecting things too.
[-- Attachment #2: Type: text/html, Size: 1895 bytes --]
next prev parent reply other threads:[~2011-04-10 17:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-10 8:49 Text/overlay property to hide buffer contents from lisp? Tom
2011-04-10 16:02 ` Andreas Röhler
2011-04-10 17:51 ` Perry Smith [this message]
[not found] <mailman.3.1302425364.25365.help-gnu-emacs@gnu.org>
2011-04-10 14:16 ` Stefan Monnier
2011-04-10 15:05 ` Tom
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=D4C1E513-4171-430C-AE5C-687B586A896D@gmail.com \
--to=pedzsan@gmail.com \
--cc=help-gnu-emacs@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.