all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Nordin <tomasn@posteo.net>
To: "Lars Ingebrigtsen" <larsi@gnus.org>,
	"Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 46151@debbugs.gnu.org
Subject: bug#46151: 28.0.50; Set revert-buffer-function in shell command output buffers
Date: Sun, 31 Jan 2021 11:48:05 +0100	[thread overview]
Message-ID: <87sg6h4c2i.fsf@posteo.net> (raw)
In-Reply-To: <87sg6htord.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
>
>> (info "(elisp) Key Binding Conventions") says C-c [^[:alpha:]] is
>> reserved for major modes (paraphrasing).  IIUC this binding for
>> revert-buffer would be global, so the C-x map would make more sense?  I
>> think?
>>
>> C-x g would make the most sense under that assumption; unfortunately
>> magit-status has been using that for years now…
>
> Oh, yeah, I was thinking of `C-x C-r' and not `C-c C-r', but that's
> unfortunately taken.
>
> Hm...  the `C-x' map is pretty heavily populated.  Let's see what's
> free...
>
> C-x C-a
> C-x C-y
>
> Wow, those are the only `C-x C-<something>' not bound of the
> alphabetical keys.  Neither seem extremely mnemonic for "revert"...
>
> Perhaps `C-x C-a' for "aaargh, reload that file already!"

Am I confused or did this discussion drift away from something specific
to shell command output buffers to something global always?

What was wrong with C-c C-r ? Maybe that existing binding in shell mode
('comint-show-output')? But if this new binding could be restricted to
those output buffers it might be ok? I mean, in those buffers it seems
to me that 'comint-show-output' (C-c C-r) do the same as
'beginning-of-buffer' (M-<).

--
Tomas





  reply	other threads:[~2021-01-31 10:48 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 [this message]
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=87sg6h4c2i.fsf@posteo.net \
    --to=tomasn@posteo.net \
    --cc=46151@debbugs.gnu.org \
    --cc=kevin.legouguec@gmail.com \
    --cc=larsi@gnus.org \
    /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.