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

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

[Message part 1 (text/plain, inline)]

On Tue, Aug 8, 2017 at 3:06 PM Eli Zaretskii <eliz <at> gnu.org> wrote:

>
> 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 don't know what the outcome should be in this case:
- No one raised any issue moving forward with this in that emacs-devel.
- The concern you raised about indent-region having side-effects doesn't
seem practical. Indenting is a buffer-editing act for which the buffer
should not be read-only. If there are some side-effects other than that,
then that's a different problem. Also no one has presented a real scenario
where this proposal would cause an issue.
- Talking about pilot-error, this proposal simply alerts the user of the
pilot-error (doing indentation in read-only buffer) sooner rather than
later, thus saving the user's time.

So I don't know how differences are resolved in cases like this. The
proposal in this thread is to solve a real-life time-consuming annoyance,
where-as the against-point is about side-effects getting masked, and which
do not have any real-life examples.
-- 

Kaushal Modi

[Message part 2 (text/html, inline)]

Previous Next

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