From: Dmitry Gutov <dgutov@yandex.ru>
To: Sean Whitton <spwhitton@spwhitton.name>,
Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46151@debbugs.gnu.org
Subject: bug#46151: 28.0.50; Set revert-buffer-function in shell command output buffers
Date: Mon, 1 Feb 2021 04:08:33 +0200 [thread overview]
Message-ID: <f6ea02ab-54a5-6e90-6711-e447cf9a3f13@yandex.ru> (raw)
In-Reply-To: <875z3ctzsw.fsf@melete.silentflame.com>
On 01.02.2021 02:08, Sean Whitton wrote:
> I think that this would have the same problem as 'g': since the buffers
> are freely-editable text, just trying to type something might result in
> a surprise re-execution of the command.
Fair enough.
But following that logic, having a easy global binding for revert-buffer
(such as 'C-x g' or even 'C-c C-r') is likely to be dangerous.
It could still be possible for command output buffers, if we switch them
to a special-mode derivative. Just how important is the ability to
freely edit those buffers? Compared to being able to easily re-run the
command.
next prev parent reply other threads:[~2021-02-01 2:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 6:22 bug#46151: 28.0.50; Set revert-buffer-function in shell command output buffers Sean Whitton
2021-01-29 5:52 ` Lars Ingebrigtsen
2021-01-29 7:05 ` Sean Whitton
2021-01-29 7:21 ` Lars Ingebrigtsen
2021-01-29 18:32 ` Sean Whitton
2021-01-30 6:18 ` Lars Ingebrigtsen
2021-01-31 18:50 ` Sean Whitton
2021-02-01 8:49 ` Lars Ingebrigtsen
2021-02-01 16:14 ` bug#46151: [External] : " Drew Adams
2021-02-01 18:00 ` Sean Whitton
2021-02-01 19:43 ` bug#46151: [External] : " Drew Adams
2021-02-02 8:44 ` Lars Ingebrigtsen
2021-02-01 20:13 ` Dmitry Gutov
2021-02-02 8:49 ` Lars Ingebrigtsen
2021-02-02 12:38 ` Dmitry Gutov
2021-02-03 18:36 ` Lars Ingebrigtsen
2021-02-03 22:46 ` Dmitry Gutov
2021-02-04 7:51 ` Lars Ingebrigtsen
2021-01-30 18:36 ` Juri Linkov
2021-01-30 21:01 ` bug#46151: [External] : " Drew Adams
2021-01-31 4:02 ` Michael Welsh Duggan
2021-01-31 7:37 ` Lars Ingebrigtsen
2021-01-31 9:20 ` Juri Linkov
2021-01-31 18:03 ` bug#46151: [External] : " Drew Adams
2021-01-31 9:46 ` Kévin Le Gouguec
2021-01-31 9:54 ` Lars Ingebrigtsen
2021-01-31 10:48 ` Tomas Nordin
2021-01-31 13:06 ` Kévin Le Gouguec
2021-01-31 21:35 ` Juri Linkov
2021-01-31 18:20 ` bug#46151: [External] : " Drew Adams
2021-01-31 16:07 ` Michael Welsh Duggan
2021-01-31 17:57 ` bug#46151: [External] : " Drew Adams
2021-01-31 18:47 ` Sean Whitton
2021-01-31 23:31 ` Dmitry Gutov
2021-02-01 0:08 ` Sean Whitton
2021-02-01 2:08 ` Dmitry Gutov [this message]
2021-02-01 5:44 ` Sean Whitton
2021-02-01 20:04 ` Dmitry Gutov
2021-02-01 20:49 ` Sean Whitton
2021-02-01 21:30 ` Dmitry Gutov
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=f6ea02ab-54a5-6e90-6711-e447cf9a3f13@yandex.ru \
--to=dgutov@yandex.ru \
--cc=46151@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=spwhitton@spwhitton.name \
/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).