GNU bug report logs - #73545
30.0.91; Strange behaviour on switch-to-next-buffer

Previous Next

Full log

Message #17 received at 73545 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Eli Zaretskii <eliz <at> gnu.org>, Rahul Martim Juliato <rahuljuliato <at> gmail.com>
Cc: 73545 <at> debbugs.gnu.org
Subject: Re: bug#73545: 30.0.91; Strange behaviour on switch-to-next-buffer
Date: Sun, 29 Sep 2024 16:17:08 +0200

> 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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.