From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22819@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: 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 [thread overview]
Message-ID: <CAFyQvY0yJMGL=isZxXhHVRBDH-_jMDHvoa+UMgEVaf-H4ETrLQ@mail.gmail.com> (raw)
In-Reply-To: <83y3qtswvv.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]
On Tue, Aug 8, 2017 at 3:06 PM Eli Zaretskii <eliz@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
[-- Attachment #2: Type: text/html, Size: 1562 bytes --]
next prev parent reply other threads:[~2017-08-08 19:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:54 bug#22819: 25.0.91; Don't try to indent region if the buffer is read-only Kaushal Modi
2017-08-05 1:56 ` npostavs
2017-08-05 6:52 ` Eli Zaretskii
2017-08-05 11:50 ` Kaushal Modi
2017-08-05 12:10 ` Eli Zaretskii
2017-08-05 12:29 ` Kaushal Modi
2017-08-05 12:37 ` Eli Zaretskii
2017-08-05 12:47 ` npostavs
2017-08-05 13:13 ` Eli Zaretskii
2017-08-07 17:45 ` Kaushal Modi
2017-08-07 17:53 ` Noam Postavsky
2017-08-07 18:02 ` Kaushal Modi
2017-08-07 18:11 ` Noam Postavsky
2017-08-08 13:06 ` Kaushal Modi
2017-08-08 13:15 ` npostavs
2017-08-08 19:05 ` Eli Zaretskii
2017-08-08 19:19 ` Kaushal Modi [this message]
2017-08-08 21:31 ` John Wiegley
2017-08-09 11:03 ` Kaushal Modi
2017-08-09 21:14 ` John Wiegley
2019-06-25 14:33 ` Lars Ingebrigtsen
2019-06-25 14:35 ` Kaushal Modi
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='CAFyQvY0yJMGL=isZxXhHVRBDH-_jMDHvoa+UMgEVaf-H4ETrLQ@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=22819@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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.