From: martin rudalics <rudalics@gmx.at>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Jefferson Carpenter <jefferson@aoeu2code.com>,
37514 <37514@debbugs.gnu.org>
Subject: bug#37514: PATCH: Add setting to allow switching to an already-visible buffer by default
Date: Mon, 7 Oct 2019 11:26:15 +0200 [thread overview]
Message-ID: <34f8685e-ceef-33ca-e36c-58964415da06@gmx.at> (raw)
In-Reply-To: <87eezp9o6j.fsf@gnus.org>
>> 'switch-to-prev-buffer' and 'switch-to-next-buffer' are the canonical
>> commands for navigating a specific window's buffer list (here these
>> are bound to <M-left> and <M-right> because I don't care for word-like
>> movement).
>
> Hey, those are really useful commands that I didn't know about.
>
> Would it make sense to give them a default key binding?
Maybe Juri has an idea ...
martin
next prev parent reply other threads:[~2019-10-07 9:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 21:24 bug#37514: PATCH: Add setting to allow switching to an already-visible buffer by default Jefferson Carpenter
2019-09-26 7:12 ` Eli Zaretskii
2019-09-26 19:13 ` Jefferson Carpenter
2019-09-26 19:14 ` Jefferson Carpenter
2019-09-27 8:16 ` martin rudalics
2019-09-28 21:00 ` Jefferson Carpenter
2019-10-02 3:36 ` Jefferson Carpenter
2019-10-02 8:54 ` martin rudalics
2019-10-04 0:45 ` Jefferson Carpenter
2019-10-05 8:42 ` martin rudalics
2019-10-05 9:30 ` Eli Zaretskii
2020-01-20 19:35 ` Stefan Kangas
2020-03-18 5:36 ` Stefan Kangas
2019-10-07 4:25 ` Lars Ingebrigtsen
2019-10-07 9:26 ` martin rudalics [this message]
2019-10-07 18:09 ` Juri Linkov
2019-10-08 8:45 ` martin rudalics
2019-10-09 18:48 ` Juri Linkov
2019-10-12 20:47 ` Juri Linkov
2019-10-13 8:17 ` martin rudalics
2019-10-08 16:32 ` Lars Ingebrigtsen
2019-10-09 20:50 ` Juri Linkov
2019-10-09 20:59 ` Lars Ingebrigtsen
2019-10-11 8:16 ` martin rudalics
2019-10-07 12:04 ` Robert Pluim
2019-10-08 8:42 ` martin rudalics
2019-10-08 11:42 ` Robert Pluim
2019-09-26 7:20 ` martin rudalics
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=34f8685e-ceef-33ca-e36c-58964415da06@gmx.at \
--to=rudalics@gmx.at \
--cc=37514@debbugs.gnu.org \
--cc=jefferson@aoeu2code.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 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).