From: Marcin Borkowski <mbork@mbork.pl>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: johnw@gnu.org, 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: Fri, 22 Jan 2016 13:58:08 +0100 [thread overview]
Message-ID: <87bn8d93fj.fsf@mbork.pl> (raw)
In-Reply-To: <m3a8nxdglv.fsf@gnus.org>
On 2016-01-22, at 11:59, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> What do others think?
>
> I think read-only overlays sound kinda nonsensical, too.
Not necessarily. This is not the same, of course, but compare Dired to
Wdired: the same text is sometimes read-only and sometimes not, and it
does make a lot of sense.
Another possible use-case: a feature like narrowing, but not making some
text invisible, but read-only instead. (This might actually be useful,
e.g. in Org-mode.)
Of course, you could do this with text properties and not overlays, but
what I'm saying is that the assumption "it [is] strange to make certain
text read-only temporarily. If it isn't supposed to change, it should
never change, right?" is false in general, even in current stock Emacs.
Best,
--
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University
next prev parent reply other threads:[~2016-01-22 12:58 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 [this message]
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
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=87bn8d93fj.fsf@mbork.pl \
--to=mbork@mbork.pl \
--cc=6922@debbugs.gnu.org \
--cc=johnw@gnu.org \
--cc=larsi@gnus.org \
--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).