From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46369@debbugs.gnu.org, Sean Whitton <spwhitton@spwhitton.name>
Subject: bug#46369: 28.0.50; Bind clone-buffer into the new C-x x keymap
Date: Mon, 8 Feb 2021 16:44:34 +0200 [thread overview]
Message-ID: <af1fca97-8e5a-82f2-380b-56e60c9f3f92@yandex.ru> (raw)
In-Reply-To: <877dnjnkh9.fsf@gnus.org>
On 08.02.2021 08:26, Lars Ingebrigtsen wrote:
> Dmitry Gutov <dgutov@yandex.ru> writes:
>
>> But if 'revert-buffer' were to move to 'C-x x u', I wouldn't find it
>> odd. Because 'revert-buffer' pretty much has two different jobs:
>>
>> - There are file-visiting buffers, revert-buffer-function is never
>> set, and revert-buffer reverts to contents saved to disk as well as
>> re-initializes the modes. Up until now this function never had a
>> binding.
>>
>> - There are non-file-visiting buffers, revert-buffer-function must be
>> set, and the command does whatever revert-buffer-function says. This
>> is usually bound to 'g', though apparently not always.
>>
>> If these were two different commands, I don't think much would have
>> changed for the vast majority of our users.
>
> Yes, that's true -- they're really quite different things... but I'm
> not sure I feel much enthusiasm for detangling that bit at this point.
FWIW, I'm not saying we should split them (the benefits are small), but
that keeping revert-buffer on 'g' in special modes and yet on 'C-x x u'
otherwise can make sense.
next prev parent reply other threads:[~2021-02-08 14:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 18:26 bug#46369: 28.0.50; Bind clone-buffer into the new C-x x keymap Sean Whitton
2021-02-07 18:42 ` Dmitry Gutov
2021-02-07 21:19 ` Lars Ingebrigtsen
2021-02-07 22:09 ` Dmitry Gutov
2021-02-08 6:26 ` Lars Ingebrigtsen
2021-02-08 14:44 ` Dmitry Gutov [this message]
2021-02-07 20:14 ` bug#46369: [External] : " Drew Adams
2021-02-08 6:52 ` Lars Ingebrigtsen
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=af1fca97-8e5a-82f2-380b-56e60c9f3f92@yandex.ru \
--to=dgutov@yandex.ru \
--cc=46369@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).