all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Marcin Borkowski <mbork@mbork.pl>, John Wiegley <johnw@gnu.org>,
	Richard Stallman <rms@gnu.org>
Cc: mt_void@warpmail.net, 6922@debbugs.gnu.org
Subject: bug#6922: 23.1; Setting read-only property in an overlay has no effect
Date: Wed, 20 Jan 2016 20:00:01 +0200	[thread overview]
Message-ID: <837fj49lni.fsf@gnu.org> (raw)
In-Reply-To: <87wpr67ezy.fsf@mbork.pl> (message from Marcin Borkowski on Mon,  18 Jan 2016 22:29:53 +0100)

> From: Marcin Borkowski <mbork@mbork.pl>
> Date: Mon, 18 Jan 2016 22:29:53 +0100
> Cc: MT <mt_void@warpmail.net>
> 
> For the record, the problem persists in GNU Emacs 25.1.50.1.  Neither
> seems there to be any change in the manual (as RMS suggested in the
> discussion at
> http://lists.gnu.org/archive/html/emacs-devel/2008-01/msg01598.html).

What is the current consensus? should we adjust the documentation or
fix the code?  John?  Richard?

Which other overlay properties don't cause exactly the same effect as
the corresponding text properties?





  reply	other threads:[~2016-01-20 18:00 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=837fj49lni.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 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.