Buffer -> Window assignments lost after closing frame when using Emacs daemon #13811
Labels
- Bug tracker -
Help wanted
Running as daemon
Spacemacs Layouts
stale
marked as a stale issue/pr (usually by a bot)
Description
I'm using emacs in daemon mode, also storing my layout and automatically
loading it on emacs startup.
Now, lets say I create a new layout and open
.emacs.d/README.md
in it.Then, I quit the frame with
<SPC> q f
. The emacs server stays running.Now, I start a new frame with
emacsclient -c
. My newly created layoutis still there, as expected. But if I now switch to that new layout,
I don't have the
.emacs.d/README.md
buffer open, but instead I seethe
scratch
buffer opened in the layout's only window. Pressing<SPC> b b
actually shows me that the buffer is still open, but it'snot loaded into the window.
Conversely, if I kill the server too, by pressing
<SPC> q q
insteadof just killing the frame with
<SPC> q f
, the buffer withREADME.md
is still open in the layout's window, as expected.
TLDR: It seems to me that while the layout, open buffer lists and so
on are stored, the info which buffer is open in which window isn't.
Reproduction guide 🪲
emacsclient -c
<SPC> l 2
<SPC> f f
<SPC> q f
emacsclient -c
<SPC> l 2
in the window anymore
<SPC> b b
to observe the buffer is still openedObserved behaviour: 👀 💔
The information about which buffer is loaded in which window is not
stored between frames.
Expected behaviour: ❤️ 😄
When I close the last frame/emacsclient and open a new one,
the previously loaded buffers are still shown in the windows they
were in when I closed the previous buffer.
System Info 💻
Possibly relevant info
I have
dotspacemacs-auto-resume-layouts 't
set in my.spacemacs
config.The text was updated successfully, but these errors were encountered: