From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
Dmitry Gutov <dmitry@gutov.dev>
Cc: 70587@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#70587: More buffers that ought to be read-only
Date: Sat, 04 May 2024 14:22:41 +0300 [thread overview]
Message-ID: <8634qxhldq.fsf@gnu.org> (raw)
In-Reply-To: <jwvr0epik7l.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 28 Apr 2024 11:30:26 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: jidanni@jidanni.org, 70587@debbugs.gnu.org
> Date: Sun, 28 Apr 2024 11:30:26 -0400
>
> > Does it mean you will not be terribly mad if I remove the read-only
> > setting from "M-x diff", and let it behave as every other client of
> > diff-mode?
>
> I don't have a strong opinion on this, no (diff-mode buffers are
> among those where I use `C-x C-q` most frequently).
>
> `C-x v =` is an important "client of diff-mode" (arguably more
> important than `M-x diff`), and it does make `*vc-diff*` read-only,
> so if you want to change `M-x diff`, I suggest you change `C-x v =` at
> the same time.
So the two most important clients of diff-mode unconditionally make
the buffer read-only, but we have a diff-mode option that by default
leaves the buffer writable? This makes absolutely no sense to me!
Does anyone have any explanation for how we ended up in this
situation?
next prev parent reply other threads:[~2024-05-04 11:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 1:16 bug#70587: More buffers that ought to be read-only Dan Jacobson
2024-04-26 9:58 ` Sean Whitton
2024-04-26 10:48 ` Eli Zaretskii
2024-04-26 11:02 ` Dan Jacobson
2024-04-26 11:13 ` Eli Zaretskii
2024-04-27 7:24 ` Dan Jacobson
2024-04-27 7:57 ` Eli Zaretskii
2024-04-27 8:15 ` bug#70602: Add hooks to control *Shell Command Output* Dan Jacobson
2024-04-28 3:02 ` bug#70587: More buffers that ought to be read-only Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-28 4:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-28 5:13 ` Eli Zaretskii
2024-04-28 9:04 ` Dan Jacobson
2024-04-28 14:57 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-28 15:18 ` Eli Zaretskii
2024-04-28 15:30 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-04 11:22 ` Eli Zaretskii [this message]
2024-05-04 14:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-04 21:40 ` Dan Jacobson
2024-05-05 5:36 ` Eli Zaretskii
2024-04-28 20:35 ` Dmitry Gutov
2024-04-29 6:57 ` Eli Zaretskii
2024-04-30 9:56 ` Dan Jacobson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8634qxhldq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70587@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=jidanni@jidanni.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).