GNU bug report logs - #22819
25.0.91; Don't try to indent region if the buffer is read-only

Previous Next

Full log

Message #28 received at 22819 <at> debbugs.gnu.org (full text, mbox):

From: npostavs <at> users.sourceforge.net
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22819 <at> debbugs.gnu.org, Kaushal Modi <kaushal.modi <at> gmail.com>
Subject: Re: bug#22819: 25.0.91;
 Don't try to indent region if the buffer is read-only
Date: Sat, 05 Aug 2017 08:47:37 -0400

Eli Zaretskii <eliz <at> gnu.org> writes:

>> >against veteran Emacs behavior regarding read-only text, behavior
>> >that is present in several other commands, and that AFAIR resulted
>> >from some past discussions.
>> 
>> This is the only one that provided me this surprise in about a decade of Emacs use. Which other commands
>> do the text manipulation, and then check the buffer read-only status? 
>
> C-w, to name just one.

That seems like a bit of a special case, as there is `kill-read-only-ok'
which specifically controls this behaviour.

> IOW, a command could have useful side effects that are produced even
> if the buffer is read-only and its text cannot be changed, thus
> preventing the main effect of the command from happening.

indent-region doesn't have any side-effects though, right?  There are
lots of other commands which check read-only status at the beginning:

    M-x rgrep barf-if-buffer-read-only\|(interactive "\*

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.