From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 19070@debbugs.gnu.org
Subject: bug#19070: 25.0.50; Provide a user option that filters the buffer list for `switch-to-next-buffer'
Date: Thu, 12 May 2022 03:35:32 +0200 [thread overview]
Message-ID: <87r14z353v.fsf@gnus.org> (raw)
In-Reply-To: <6ccbf136-5fc1-4b95-ab58-67ad51619fe8@default> (Drew Adams's message of "Sun, 16 Nov 2014 08:38:32 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> Provide a user option with a regexp value that filters the buffers (by
> name) that are cycled through by `next-buffer' and `previous-buffer'.
> Buffer names matching the regexp would be excluded.
Emacs 27.1 added switch-to-prev-buffer-skip, but didn't include a simple
regexp form, and I agree that such a simple form is usually what people
want. (I know you can achieve some of this stuff by making windows
dedicated, too, but that's another complication.)
> Or the option could be a cons, with one part determining whether the
> regexp is used to exclude or include and the other part being the
> regexp.
I see the charm, but for complex setups like that, I think using
dedicated windows would be the thing.
So I've now added switch-to-prev-buffer-skip-regexp to Emacs 29.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-12 1:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-16 16:38 bug#19070: 25.0.50; Provide a user option that filters the buffer list for `switch-to-next-buffer' Drew Adams
2022-05-12 1:35 ` Lars Ingebrigtsen [this message]
2022-05-12 16:02 ` Drew Adams
2022-05-12 16:47 ` Eli Zaretskii
2022-05-12 16:53 ` Drew Adams
2022-05-12 17:06 ` Eli Zaretskii
2022-05-12 17:25 ` Drew Adams
2022-05-12 17:37 ` Eli Zaretskii
2022-05-12 17:50 ` Drew Adams
2022-05-12 18:14 ` Eli Zaretskii
2022-05-12 21:57 ` Kévin Le Gouguec
2022-05-13 8:14 ` Robert Pluim
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=87r14z353v.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=19070@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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.