From: Dan Jacobson <jidanni@jidanni.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70587@debbugs.gnu.org
Subject: bug#70587: More buffers that ought to be read-only
Date: Fri, 26 Apr 2024 19:02:04 +0800 [thread overview]
Message-ID: <ZiuJrLiF5wMDQqTm@jidanni.org> (raw)
In-Reply-To: <86jzkkz9f2.fsf@gnu.org>
All I know is I use
= runs the command dired-diff
Also in the "rare case that one needs to use the washroom while driving the car,"
instead of driving around with the doors open all day long, and seat belts off..."
it should be they who are forced to use C-x C-q to make those buffers read-write.
next prev parent reply other threads:[~2024-04-26 11:02 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZiuJrLiF5wMDQqTm@jidanni.org \
--to=jidanni@jidanni.org \
--cc=70587@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.