[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#70587: More buffers that ought to be read-only
|
From: |
Dan Jacobson |
|
Subject: |
bug#70587: More buffers that ought to be read-only |
|
Date: |
Sun, 5 May 2024 05:40:03 +0800 |
On Sat, May 04, 2024 at 10:36:07AM -0400, Stefan Monnier wrote:
> [ So, by and large, I agree with Dan that things like `*Shell Command
> Output*` and errors buffers might benefit from being made read0only by
> default. ]
Currently there is no way for users to even make *Shell Command
Output* read only even if they wanted. No hook. No variable. Nothing.
Execpt of course manually hitting C-x C-q. Good thing at least one can also set
view-read-only.
Also what's so good about having *Shell Command Output* read-write,
when anything you change will get lost? Unless OK, you are planning to
feed it back in to a second shell-command-on-region.