From: Rahul Martim Juliato <rahuljuliato@gmail.com>
To: 73545@debbugs.gnu.org
Subject: bug#73545: 30.0.91; Strange behaviour on switch-to-next-buffer
Date: Sun, 29 Sep 2024 01:25:21 -0300 [thread overview]
Message-ID: <20240929042521.cgiwkts2ot6ms2tx@debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
Hello there!
I just wanted to report something I found a bit strange.
I would like some keybindings to jump to the next/previous *non-special*
buffer.
With these settings:
(setq switch-to-prev-buffer-skip-regexp "\*[^*]+\*")
(setq switch-to-next-buffer-skip-regexp "\*[^*]+\*")
I have the init.el file open, along with the Messages and scratch
buffers.
When I run (switch-to-next-buffer) or (switch-to-previous-buffer), I get
a special buffer. If I run it again, I return to the file, and running
it once more takes me to another special buffer.
If I open another file, like .bashrc, it works as I initially expected.
Now, (switch-to-next-buffer) switches to init.el, and running it again
returns me to init.el back and forth, without switching to any more
special buffers.
It seems that I need to have at least two non-special buffers open. With
only one, the switch function probably (I haven't checked) reaches the
end of the buffer list without finding a match and returns the last
buffer.
Should it work this way? If there are no matches, shouldn't it stay on
the current buffer and/or display a message like "no next/prev buffer"
in the echo area?
Thanks!
--
Rahul Martim Juliato
https://www.rahuljuliato.com
PGP Fingerprint: 6B68 4353 84E2 2C7E 5A26 B79A C666 FC94 BD7E A483
PGP Public Key : https://www.rahuljuliato.com/rahul_pub_key.asc
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2024-09-29 4:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 4:25 Rahul Martim Juliato [this message]
2024-09-29 5:39 ` bug#73545: 30.0.91; Strange behaviour on switch-to-next-buffer Eli Zaretskii
2024-09-29 12:29 ` Rahul Martim Juliato
2024-09-29 12:51 ` Eli Zaretskii
2024-09-29 14:17 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <d5a2e607-d1c7-4f8d-b7e0-cde2c3d5009b@gmx.at>
2024-10-03 21:19 ` Rahul Martim Juliato
2024-10-04 8:07 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-05 10:31 ` Eli Zaretskii
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=20240929042521.cgiwkts2ot6ms2tx@debian \
--to=rahuljuliato@gmail.com \
--cc=73545@debbugs.gnu.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.