From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 2553@debbugs.gnu.org, Chong Yidong <cyd@stupidchicken.com>,
David Reitter <david.reitter@gmail.com>,
emacs-devel@gnu.org
Subject: Re: bug#2553: *vc-diff* buffers are read-only, but M-k works
Date: Thu, 06 Oct 2011 23:59:02 +0200 [thread overview]
Message-ID: <m3zkhdhjdl.fsf@stories.gnus.org> (raw)
In-Reply-To: <jwvhb4hp72h.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 12 Sep 2011 21:26:03 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Perhaps a more general solution would be possible here. I think there
>> probably are other "mostly-read-only" modes where you have one or two
>> special commands that alter the buffer, anyway. Like with `M-k'.
>> Perhaps there could be a buffer-local variable like
>> `undo-read-only-buffer' that if set, would allow `undo' to work in these
>> cases.
>
> Or we could record in the buffer-undo-list the fact the the modification
> was done with inhibit-read-only bound to non-nil, and bind it similarly
> during the undo.
That would be even better, and is even more general.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-10-06 21:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 15:41 *vc-diff* buffers are read-only, but M-k works Chong Yidong
2009-03-04 15:54 ` Juanma Barranquero
2009-03-04 15:54 ` bug#2553: " Juanma Barranquero
2011-09-11 21:46 ` Lars Magne Ingebrigtsen
2011-09-13 1:26 ` Stefan Monnier
2011-10-06 21:59 ` Lars Magne Ingebrigtsen [this message]
2011-10-06 21:59 ` bug#2553: " Lars Magne Ingebrigtsen
2011-09-13 1:26 ` Stefan Monnier
2011-09-11 21:46 ` Lars Magne Ingebrigtsen
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 15:41 Chong Yidong
2009-03-03 4:18 David Reitter
2012-04-26 3:33 ` Chong Yidong
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=m3zkhdhjdl.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=2553@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.