Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

desktop-save-mode blocks startup of spacemacs #1265

Closed
seschwar opened this issue Apr 19, 2015 · 4 comments
Closed

desktop-save-mode blocks startup of spacemacs #1265

seschwar opened this issue Apr 19, 2015 · 4 comments

Comments

@seschwar
Copy link

When desktop-save-mode is enabled spacemacs stops after initialization with the prompt Buffer "*emacs*" has a running process; kill it? (y or n). The "running process" is spacemacs checking its repository for updates.

While I can easily answer n and continue when launching Emacs with a frame attached, it's a problem when using emacs --daemon. Due to the question the daemon blocks and doesn't fork. This breaks scripted Emacs startup, both with shell scripts and systemd. The daemon doesn't fork and therefore the script can't continue past emacs --daemon.

This can be easily reproduced by appending the following lines onto the default ~/.spacemacs.

(custom-set-variables
 '(desktop-save-mode t))
@syl20bnr
Copy link
Owner

Thank you for the report, can you try to delay the first check and see if it allows the process to fork ?
https://github.com/syl20bnr/spacemacs/tree/develop/core/core-spacemacs.el#L366

(run-at-time 20 nil
                  (lambda () (spacemacs/check-for-new-version
                              spacemacs-version-check-interval)))

@person808
Copy link
Contributor

@seschwar Do you still encounter this issue? I want to know if I can recommend this in #1565

@StreakyCobra
Copy link
Contributor

@seschwar Do you still have this issue with last spacemacs release?

@StreakyCobra
Copy link
Contributor

This old issue has been waiting for a response for more than one month. As no answer has been provided, we can not help further or know if the issue is still relevant. We are then closing it. Feel free to open a new issue if there is any news on this side, be sure to read this guide first and link this issue in the new one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants