From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 22819@debbugs.gnu.org
Subject: bug#22819: 25.0.91; Don't try to indent region if the buffer is read-only
Date: Mon, 7 Aug 2017 14:11:38 -0400 [thread overview]
Message-ID: <CAM-tV-_HJS06f9EbGvD5eHWY7kgJVhfSocOG1jvXdcZShLGcwg@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY1yHiB7qO8KdZst9xVj9g0nMM64f0X2HNEUasMsnh7pWA@mail.gmail.com>
On Mon, Aug 7, 2017 at 2:02 PM, Kaushal Modi <kaushal.modi@gmail.com> wrote:
> On Mon, Aug 7, 2017 at 1:53 PM Noam Postavsky
> <npostavs@users.sourceforge.net> wrote:
>>
>> hmm, I can't reproduce here, but is it possible you have bound C-M-\
>> to some other command which calls indent-region non-interactively?
>
> This deviates from this bug report.. but I am open to suggestions on how I
> could retain the * property of the interactive form while setting the region
> boundaries as I do in the below advice.
Ah, well since you're replacing the interactive form, I suppose the
replacement should then make sure to check the read-only status as
well.
(interactive (progn (barf-if-buffer-read-only) ...))
next prev parent reply other threads:[~2017-08-07 18:11 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 [this message]
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
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=CAM-tV-_HJS06f9EbGvD5eHWY7kgJVhfSocOG1jvXdcZShLGcwg@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=22819@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
/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.