all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 70587@debbugs.gnu.org
Subject: bug#70587: More buffers that ought to be read-only
Date: Fri, 26 Apr 2024 13:48:49 +0300	[thread overview]
Message-ID: <86jzkkz9f2.fsf@gnu.org> (raw)
In-Reply-To: <87le506i07.n.fsf@jidanni.org> (message from Dan Jacobson on Fri,  26 Apr 2024 09:16:08 +0800)

> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Fri, 26 Apr 2024 09:16:08 +0800
> 
> diff-default-read-only is a variable defined in ‘diff-mode.el’.
> Its value is nil
> If non-nil, ‘diff-mode’ buffers default to being read-only.
> 
> That's funny, it seems they are already read-only, without setting this
> variable. Maybe this variable can be retired.

I cannot reproduce this.  E.g., visiting a file that turned on
diff-mode doesn't make the buffer read-only.  So please show a recipe,
preferably starting from "emacs -Q", where a diff-mode buffer is
read-only without changing this variable from its default value of
nil.

> But how about *Shell Command Output*, and errors buffers, they should be
> read-only by default too.
> 
> Why? Because tons of times we realize for the last half hour we have
> been editing our program's output buffer instead of the source code.
> 
> (Often due to using sh -x or make (without -s) which echo command
> lines.)

A simple "C-x C-q" should set you up, in those cases.

Emacs cannot possibly cater to each and every use case out there.
Sometimes you need to do stuff manually, if your case is specialized
to require that.





  parent reply	other threads:[~2024-04-26 10:48 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 [this message]
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
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=86jzkkz9f2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70587@debbugs.gnu.org \
    --cc=jidanni@jidanni.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.