From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46151@debbugs.gnu.org, Sean Whitton <spwhitton@spwhitton.name>
Subject: bug#46151: 28.0.50; Set revert-buffer-function in shell command output buffers
Date: Tue, 2 Feb 2021 14:38:28 +0200 [thread overview]
Message-ID: <c2dccd7a-6c4b-b55a-7417-f1b68f5ee4dd@yandex.ru> (raw)
In-Reply-To: <87v9ban9bp.fsf@gnus.org>
On 02.02.2021 10:49, Lars Ingebrigtsen wrote:
> The impetus for introducing this binding now is that we have two cases
> of a non-special mode with a (very) useful `revert-buffer' binding, so
> we can't use `g' there. So it's time to give it a global binding.
I offered an alternative suggestion for how 'g' could work (prohibit
free editing when the command finishes). Or perhaps some of the other
suggestions could be taken and standardized on for similar circumstances
('C-c C-g' might be appropriate since it's major mode specific).
I think it's a nice property that major modes that have this binding
implement some special behavior for reverting. And all that do, have
this binding.
But now, if a global binding is added, I worry that people might abandon
that convention.
> But I disagree that it's not a useful general command for non-power
> users: A common question is "how do I reload a file?", and we didn't
> have a key binding for that. `C-x C-f' does not reliably reload a file,
> since it has DWIM stuff going on.
Isn't the answer to most such questions, 'enable global-auto-revert-mode'?
I do revert buffers explicitly from time to time too (especially when
developing or debugging certain Elisp packages), but still not often
enough to worry about having to type 'M-x revert-buffer'.
next prev parent reply other threads:[~2021-02-02 12:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c2dccd7a-6c4b-b55a-7417-f1b68f5ee4dd@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 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.