From: Tassilo Horn <tassilo@member.fsf.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 10222@debbugs.gnu.org
Subject: bug#10222: 24.0.92; Sentence movement commands make emacs hang
Date: Mon, 05 Dec 2011 16:41:30 +0100 [thread overview]
Message-ID: <87d3c32fh1.fsf@tsdh.uni-koblenz.de> (raw)
In-Reply-To: <jwvborn3ygy.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 05 Dec 2011 09:08:22 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> (overlay-put ol 'invisible t)
>> (overlay-put ol 'intangible t))))
>
> While we probably can and maybe should make your test case work
> better, the use of `intangible' is strongly discouraged,
Then it would be good if the docs stated that.
> specifically because it's pretty much impossible to make all other
> commands work "right" in the presence of intangible properties.
Yes, probably. I've experimented a bit more, and it gets even worse
with line-editing commands like kill-line, especially if the intangible
overlay starts or ends in the middle of a line...
But it seems that there's no sense in making an invisible overlay
intangible, anyway, at least I can't find any difference in behavior
between invisible and invisible + intangible (except that the problem
doesn't appear).
The mode that creates those overlays (iedit-mode) seems to do that in
order to protect the invisible regions, but you can still accidentally
kill an intangible & invisible region as a whole. `read-only' would be
the right property to use here, but it seems it's not supported for
overlays...
Bye,
Tassilo
next prev parent reply other threads:[~2011-12-05 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 12:28 bug#10222: 24.0.92; Sentence movement commands make emacs hang Tassilo Horn
2011-12-05 14:08 ` Stefan Monnier
2011-12-05 15:41 ` Tassilo Horn [this message]
2011-12-05 16:55 ` Stefan Monnier
2011-12-05 19:31 ` Tassilo Horn
2011-12-10 12:11 ` Johan Bockgård
2022-01-27 17:50 ` bug#10222: intangible property and sentence movement Lars Ingebrigtsen
2022-01-27 20:12 ` Tassilo Horn
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=87d3c32fh1.fsf@tsdh.uni-koblenz.de \
--to=tassilo@member.fsf.org \
--cc=10222@debbugs.gnu.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 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.