nil 'buffer-list causes *scratch* buffer (re-)created when loading

[jeff-phil]

I am newly switching over from another workspace manager and getting set up.

System is emacs 29.1 on macos (emacs-mac).

I am using this config: https://github.com/florommel/bufferlo?tab=readme-ov-file#complete-configuration-sample

When I start up emacs with (bufferlo-mode) on in above configuration, i always get an unwanted scratch buffer. Historically, i have killed this on start (kill-buffer "*scratch*"), but no longer working.

I've tried all kinds of things to get it not to show or go away (e.g. setting tab-bar-new-tab-choice to various things), including put this in my bufferlo :config startup:

    (add-hook 'bufferlo-mode-hook
            (lambda ()
              (run-with-timer
               2
               nil
               (lambda ()
                 (ignore-errors
                   (kill-buffer "*scratch*"))))))
  (add-hook 'emacs-startup-hook
            (lambda ()
              (run-with-timer
               2
               nil
               (lambda ()
                 (ignore-errors
                   (kill-buffer "*scratch*"))))))

But the proverbial cat 😼 keeps coming back.

[shipmints]

Welcome to the bufferlo family.

What is the value of tab-bar-new-tab-choice in your configuration?

Did you add either of these?

(add-hook 'after-make-frame-functions #'bufferlo-switch-to-scratch-buffer)
(add-hook 'after-make-frame-functions #'bufferlo-switch-to-local-scratch-buffer)

[jeff-phil]

Thanks!

tab-bar-new-tab-choice is t, i've tried "*Messages*" and 'current (which I believe is same as t, but just to be sure tried 'current)

My after-make-frame-functions has these: (bufferlo--include-exclude-buffers bufferlo--set-buffer-predicate aw--after-make-frame)

What is weird, if I don't do (bufferlo-mode) then I don't get the scratch. And if I then eval (bufferlo-mode) after startup I also don't get scratch.

So I tried starting (bufferlo-mode) with after-mode-hook with and without a 20s timer, but scratch still came in.

I know having scratch popup is a little nit and I rarely restart emacs, so please don't spend time on this. Just thought someone else had maybe run across.

[shipmints]

tab-bar-new-tab-choice being t also means that if you're on your normal "scratch" buffer when you create a new tab, the new tab will default to that buffer.

Do you have your complete configuration checked in somewhere we can take a look?

[jeff-phil]

If i comment out these two lines at 1064-1065:

          (dolist (frame (frame-list))
            (bufferlo--set-buffer-predicate frame))

Then i do not get the scratch buffer.

In frame-list while above is running, there is only 1 frame. If I subsequently run after startup, etc. then i don't get scratch. Nor If i create a frame with the hook from line 1066 scratch also does not show up.

Not sure what it is about being in the mode definition during startup that produces a scratch, but doesn't otherwise.

Config probably not in a state to share. I will see about scrubbing it and producing a minimal one that can reproduce.

[shipmints]

What is your bufferlo-prefer-local-buffers set to?

[shipmints]

Also, what do you have on switch-to-prev-buffer-skip-regexp and switch-to-prev-buffer-skip?

[jeff-phil]

What is your bufferlo-prefer-local-buffers set to?

Set to 'tabs in the :init section.

what do you have on switch-to-prev-buffer-skip-regexp

"\\` *\\(\\*\\(Messages\\|Buffer List\\|Ibuffer\\|Local Buffer List\\|scratch\\|Occur\\|Completions\\|Help\\|Warnings\\|Apropos\\|Bookmark List\\|Async-native-compile-log\\|Flymake log\\|ruff-format errors\\|vc-diff\\)\\*\\)\\|\\*[^z-a]+ Ibuffer\\*\\|\\*helpful [^z-a]+\\*\\|\\*tramp[^z-a]+\\*\\|magit[^z-a]*: [^z-a]+\\'"

and switch-to-prev-buffer-skip

bufferlo--switch-to-prev-buffer-skip-p

[shipmints]

When you say the "scratch" buffer reappears automatically, do you mean on the bufferlo local buffer list or on the global buffer list? Why do you wrap kill-buffer with ignore-errors and what errors does it produce when you let it run naturally?

[jeff-phil]

When you say the "scratch" buffer reappears automatically

At the top of my init, i kill the scratch that is automatically created during startup, so this with added messages:

(ignore-errors
  (message "scratch: %s" (get-buffer "*scratch*"))
  (kill-buffer "*scratch*")
  (message "scratch: %s" (get-buffer "*scratch*"))

outputs:

scratch: *scratch*
scratch: nil

showing that the initial scratch buffer is indeed gone (nil). Then after (bufferlo-mode) a new scratch buffer shows up again.

do you mean on the bufferlo local buffer list or on the global buffer list

I've not yet gotten past setting up anything other than the initial config, and not saved any bookmarks, frames, tabs, sets, etc. yet. But looking at consult-buffers, it shows under: Buffer Local Buffers and Buffers. Does that mean both local and global?

Why do you wrap kill-buffer with ignore-errors

What it does is if there is no *scratch* buffer, kill-buffer doesn't error because the buffer is not there. It is not necessary on startup since scratch always created. I believe it's there so originally I could re-run my entire ".emacs.el" and if scratch wasn't there would not backtrace on me, but it's been in my config for 30+ years, so faint memories... same thing happens regardless of if wrapped.

what errors does it produce when you let it run naturally

Runs the same.

[shipmints]

Would you be able to reproduce this issue in a script dedicated to just killing scratch and loading bufferlo? Also would be good to know what version of bufferlo you have installed (I guess this is a silly question if you just installed from ELPA but if you got it somewhere else we need to know).

[jeff-phil]

Yes, will try to create a reproducible init.

Version is 1.2 freshly from ELPA, but in order to debug this: #63 (comment) I pulled from your repo.

[jeff-phil]

Here's a reproducible init file:

init-bufferlo.el.txt

System specifics:

GNU Emacs 29.4 (build 1, aarch64-apple-darwin24.6.0, Carbon Version 170 AppKit 2575.7)

Thanks again! Happy new year!

[shipmints]

That's not a minimal -Q style reproducer. I will pare it down to the essentials and see if the problem presents itself. I will post the edited file back here. Unless you want to create a minimal reproducer; i.e., no color changing, don't load server or no-littering or blink cursor, no settings like drag-and-drop which have nothing to do with bufferlo...

[jeff-phil]

Sorry, I can skinny it down more.

[shipmints]

I did already. Don't worry.