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 #69 received at 22819 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 22819 <at> debbugs.gnu.org, npostavs <at> users.sourceforge.net,
 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: Tue, 25 Jun 2019 16:33:06 +0200

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

>> From: Kaushal Modi <kaushal.modi <at> gmail.com>
>> Date: Tue, 08 Aug 2017 13:06:52 +0000
>> Cc: 22819 <at> debbugs.gnu.org
>> 
>> @Eli: Based on the discussion[1] on emacs-devel, there isn't any
>> opposition to doing what's proposed in this
>> bug thread. So if it's alright by you, and if there is no strong
>> reason to use the more concise alternative i.e. if
>> both barf-if-buffer-read-only and interactive "*.." are equally
>> correct, can the former approach be committed?
>
> I'm not sure what is it that you are asking me.  You already know my
> opinion on this proposal, and it hasn't changed.

I think the rough consensus was that adding this special-casing to this
command wasn't idea, so I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

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