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: Thu, 4 Feb 2021 00:46:44 +0200 [thread overview]
Message-ID: <a74cd553-a0f0-5c0c-dfa4-c613cab42985@yandex.ru> (raw)
In-Reply-To: <87y2g5gfr3.fsf@gnus.org>
On 03.02.2021 20:36, Lars Ingebrigtsen wrote:
>> 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.
>
> I don't think modes will stop creating reversion functions, and I think
> special modes will continue to bind `g' -- it's more convenient than
> `C-x g', after all. So I don't think this is much to worry about.
I hope so.
OTOH, I think it might seem perfectly reasonable for some future
maintainer to stop that practice because, after all, a handy global
binding already exists.
For example, this bug can be considered only halfway fixed for anyone
who uses 'C-x g' for other purposes. It's not a big deal in one
instance, only as part of a possible future trend.
>>> 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'?
>
> No, I think `global-auto-revert-mode' is something most people don't
> want. For instance, if you're looking at /var/log/exim4/mainlog in
> Emacs (which I do sometimes), you do not want that to be reloaded all
> the time, because that would make it difficult to get any work done in
> that buffer. But you do want to reload it occasionally.
Avoiding a feature that saves people time on account of certain rare
buffers being more difficult seems counter-productive. It's like giving
up on automatic transmission on account of the existence of hills.
Even if somebody doesn't want to use auto-revert is all buffers,
toggling auto-revert-mode on only in certain ones is bound to save them
time. Or people can explicitly disable the mode in certain buffers, like
ones showing log files. Does 'exim4/mainlog' have a dedicated major
mode? It can go in global-auto-revert-ignore-modes.
I can understand calling revert-buffer manually if you're editing a few
files, but if you're working on a larger project and switch to a
different Git branch with multiple buffers open, that's unmanageable.
Almost all editors I used have this feature on by default (except Vim, I
guess?), so there is a consensus there.
>> 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'.
>
> I do it quite often (both in the log file case and because I apply
> patches a lot).
FWIW, I apply patches with diff-mode.
next prev parent reply other threads:[~2021-02-03 22:46 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 [this message]
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=a74cd553-a0f0-5c0c-dfa4-c613cab42985@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.