Closed mphojele closed 4 years ago
Oh! Yes, why am I telling you this? Since I use Spacemacs, I tried debugging this issue by setting up spacemacs with a minimal config called spacemacs-base and then testing each layer in turn to see in which does the issue persist. And it turned out to be the spacemacs-layouts layer. So I looked at the packages in there, I added them in turn to dotspacemacs-excluded-packages, then my foundings yielded a high chance of persp-mode causing the issue. However, I do not know the why and how but I think it would be great if you also found it interesting and gave it a quick look
The reproduction guide is in the issue mentioned above. Hope to hear from this project soon :)
Well I tried a lot of different things and I have no idea what is wrong.
// Looks like without spacemacs it works. So I assume it's somehow related to spacemacs layouts code, but I am not familiar with spacemacs codebase.)
Thank you for the reply. I forgot to test it without spacemacs. And yes, I think you are correct in that it might be how persp-mode is configured in spacemacs since I found no similar reported issue in doom-emacs.
This may be fixed
https://github.com/syl20bnr/spacemacs/issues/12873
Hi @Bad-ptr, I use spacemacs, and the spacemacs issue link above is about how the emacs daemon fails to shutdown probably on spacemacs, that is, via systemd or a simple
emacsclient -e "(kill-emacs)"
. I also triedsave-buffers-kill-emacs
andsave-buffers-kill-terminal
, they all yield the same results, emacs just gives a unusual prompt onrecentf buffer modified. Kill anyway?
. So this is a prompt you can't interact unless you launch a new emacsclient to get to it. Gets awkward when you shutting down, cause systemd is finding it hard to kill the emacs daemon.