unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>,
	Rahul Martim Juliato <rahuljuliato@gmail.com>
Cc: 73545@debbugs.gnu.org
Subject: bug#73545: 30.0.91; Strange behaviour on switch-to-next-buffer
Date: Sun, 29 Sep 2024 16:17:08 +0200	[thread overview]
Message-ID: <8cfbc823-ad1a-4ad6-90a6-fdf18baac037@gmx.at> (raw)
In-Reply-To: <86jzeu4o8p.fsf@gnu.org>

 > If you mean that Emacs switches to a buffer whose name matches
 > switch-to-prev-buffer-skip-regexp when there are no other buffers to
 > show, then this is the intended behavior, I think.  Martin, am I
 > right?

I don't know about 'switch-to-prev-buffer-skip-regexp'.  Here I have
set 'switch-to-prev-buffer-skip' to the function

(defun skip-undisplayed-buffers (_window buffer _bury-or-kill)
   "Function for `switch-to-prev-buffer-skip'.
Skip BUFFER if it has never been displayed before."
   (zerop (buffer-local-value 'buffer-display-count buffer)))

(setq switch-to-prev-buffer-skip 'skip-undisplayed-buffers)

Now with emacs -Q evaluate that in *scratch* and do C-x <left>.  Gets me
"No previous buffer" and *scratch* stays.  I think the same should
happen if 'switch-to-prev-buffer-skip-regexp' matches *Messages*.  What
is the value of that variable?

martin





  reply	other threads:[~2024-09-29 14:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-29  4:25 bug#73545: 30.0.91; Strange behaviour on switch-to-next-buffer Rahul Martim Juliato
2024-09-29  5:39 ` 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 [this message]
     [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

  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=8cfbc823-ad1a-4ad6-90a6-fdf18baac037@gmx.at \
    --to=bug-gnu-emacs@gnu.org \
    --cc=73545@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rahuljuliato@gmail.com \
    --cc=rudalics@gmx.at \
    /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).