unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: mbork@mbork.pl, johnw@gnu.org, mt_void@warpmail.net,
	6922@debbugs.gnu.org
Subject: bug#6922: 23.1; Setting read-only property in an overlay has no effect
Date: Thu, 21 Jan 2016 19:33:46 +0200	[thread overview]
Message-ID: <83oace96rp.fsf@gnu.org> (raw)
In-Reply-To: <E1aM5Vr-0006bp-D2@fencepost.gnu.org> (message from Richard Stallman on Wed, 20 Jan 2016 22:02:19 -0500)

> From: Richard Stallman <rms@gnu.org>
> CC: mbork@mbork.pl, johnw@gnu.org, 6922@debbugs.gnu.org,
> 	mt_void@warpmail.net
> Date: Wed, 20 Jan 2016 22:02:19 -0500
> 
> I have not been looking at this issue.  Do I need to?

There was an old discussion of this

  http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg01598.html

In that discussion, you said:

  It is no accident that read-only works only as a text property.
  It is tested for in textprop.c only as a text property.

  I am not sure that a read-only property on an overlay makes much sense.
  It is a strange thing to do.  So I will fix the documentation.

I'm asking if you still think the same.  If so, perhaps you could try
explaining why you do (in that old discussion, you said it was hard
for you to put this into words).

Thanks.





  reply	other threads:[~2016-01-21 17:33 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 [this message]
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
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=83oace96rp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=6922@debbugs.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).