2

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.

Improve this question
10
  • Is there something that forces you to use the snap? The latest version of Ubuntu apparently comes with Emacs 30.1 in the repositories, so why not just sudo apt install emacs? Commented May 31 at 19:48
  • Not that it helps me solve this problem but a Snap channel is available that is updated more frequently and, under Snap, it takes almost no work to run separate versions since instances are both isolated from each other and self-contained. Commented Jun 1 at 14:45
  • 1
    Well, if you install it using apt and try running that version, it may at least help you in determining whether it is something to do with the snap (or something in the snap container) that is causing the issue... And just in general, the stranger the setup, the harder it is to find other people who are familiar with and can assist with that particular setup (not saying the snap is causing it, but we don't know). I don't think there are as many people running Emacs as a snap. Commented Jun 1 at 17:45
  • I get the impression you were unable to reproduce the problem. I'm new to Linux and I'm more-and-more getting the impression that people believe Snap is the cause or source of problems. I don't understand how or why it is looked upon as an avenue for introduction of what look like code problems unless perhaps the problems are 'native compile' related and the compilers used for Snap are different than other environments -- and are not stable. Commented Jun 2 at 12:18
  • 1
    Well, in your recent questions you have a bunch of mysterious things happening that nobody seems to be able to reproduce (I haven't tried this one though). Is it any wonder that our suspicions fall on your installation? And since part of that installation is the Snap package, it is suspect along with the rest. Commented Jun 2 at 12:29

1 Answer 1

Reset to default
2

Thanks to @NickD who managed to trace the messages as originating from widget-move calls in recentf-dialog-goto-first, I reported a bug. I also suggested adding an optional parameter to recentf-dialog-goto-first that allowed callers to suppress the message when the operation was part of initialization rather than due to user interaction.

Upon review of my report, rather than take my band-aid suggestion, they [Steve B] not only suppressed the spurious message but added a customization allowing users to turn the messages off when their own interactions would normally result in these informational messages. See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78666.

Improve this answer
1
  • You can accept your own answer. Commented Jul 23 at 13:50

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.