I'm moving from Emacs 24 on Windows to Emacs 30.1 in server mode on Ubuntu via Snap so I'm having to deal with a huge number of things changing all at once. The problem I'm bothering you with occurs in both standalone and server mode although the messaging is slightly different in each mode I'm showing the messages from a server mode startup.
When I open a new or initial frame I almost always want to open something I've opened before so I put this in my .emacs.
(setq initial-buffer-choice 'recentf-open-files) What I'm bothered by is the messages that follow "Starting Emacs daemon." They are clearly related to the above statement but I'm not sure what I could be doing to cause it to open (apparently 3 times) the last file I opened before shutting down.
Whatever is going on, the buffer doesn't actually exist by the time I have access to look at available buffers. And getting rid of the "Collapse node" messages would be a bonus.
Starting new Ispell process /usr/bin/aspell with default dictionary...done Starting Emacs daemon. Collapse node Open ~/snap/emacs/site-lisp/anchored-transpose.el Collapse node Open ~/snap/emacs/site-lisp/anchored-transpose.el [2 times] When done with this frame, type C-x 5 0 Mark set Collapse node Since it likely makes a difference, these are the other recentf things I've configured.
'(recentf-auto-cleanup 'never) '(recentf-max-menu-items 40) '(recentf-max-saved-items 200) '(recentf-menu-filter 'recentf-arrange-by-mode) '(recentf-menu-open-all-flag t) '(recentf-mode t) '(recentf-show-file-shortcuts-flag nil) Update: I say 'clearly related" because removal of the setq line eliminates the messages but I need help because, while 'debug-on-entry' followed by 'c' does result in the messages being generated, if I try to 'd' thru the code, the messages don't appear. So I'm really at a loss concerning how to proceed. I see no dependencies to recentf.el beyond wid-edit.el and neither contain the word 'Collapse' making me suspect something, perhaps idle-timer related is stepping in but at that point I'm out of my depth concerning how to diagnose further.
Update2: I failed to mention above, that the debug attempt described was executed from -Q start. That is, I issued the recentf-mode and debug commands via M-x ... after a -Q startup.