From: John Wiegley <jwiegley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Marcin Borkowski <mbork@mbork.pl>,
mt_void@warpmail.net, rms@gnu.org, 6922@debbugs.gnu.org
Subject: bug#6922: 23.1; Setting read-only property in an overlay has no effect
Date: Thu, 18 Feb 2016 10:53:00 -0800 [thread overview]
Message-ID: <m2bn7dn94j.fsf@newartisans.com> (raw)
In-Reply-To: <83y4ait0ys.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Feb 2016 18:52:43 +0200")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
> If you are arguing for having a feature that marks some portion of buffer
> text read-only, then we already have that: the 'read-only' text property.
> The issue in this discussion is whether we should _also_ have a similar
> overlay property.
That said, I think the right way to implement clock-masking in Org would be to
use an overlay whose existence is tied to the clock. A text-property might be
incompatible with the way Org uses font-locking.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2016-02-18 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 14:46 bug#6922: 23.1; Setting read-only property in an overlay has no effect MT
2011-12-10 12:09 ` Johan Bockgård
2016-01-18 21:29 ` Marcin Borkowski
2016-01-20 18:00 ` Eli Zaretskii
2016-01-21 3:02 ` Richard Stallman
2016-01-21 17:33 ` Eli Zaretskii
2016-01-22 3:24 ` Richard Stallman
2016-01-22 7:37 ` Eli Zaretskii
2016-01-22 10:59 ` Lars Magne Ingebrigtsen
2016-01-22 12:58 ` Marcin Borkowski
2016-02-07 22:24 ` John Wiegley
2016-02-07 22:30 ` Marcin Borkowski
2016-02-18 5:12 ` Marcin Borkowski
2016-02-18 16:52 ` Eli Zaretskii
2016-02-18 18:53 ` John Wiegley [this message]
2016-02-08 16:04 ` John Wiegley
2016-02-08 17:55 ` Eli Zaretskii
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=m2bn7dn94j.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=6922@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=johnw@gnu.org \
--cc=mbork@mbork.pl \
--cc=mt_void@warpmail.net \
--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 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).