Open ville-h opened 3 years ago
Hi @ville-h, thanks for the report. Not sure if it's still relevant to you, but as far as I can tell, the problem isn't actually in purpose-load-window-layout-file
. What I assume is happening, is that something else could change the frame's contents during startup. I'd suggest delaying the call to purpose-load-window-layout-file
to the end of the startup process, via after-init-hook
:
(add-hook 'after-init-hook
(lambda () (purpose-load-window-layout-file (concat (car purpose-layout-dirs) "/" "default.window-layout"))))```
I am trying to load a window layout on startup. The layout is a simple 2 windows side-by-side 50-50 split. One of my attempts is as follows:
The window layout file looks like:
The result is that the frame does not contain 2 windows. The frame only has 1 window. There are no apparent error messages in
*Messages*
buffer at least. Callingpurpose-reset-window-layout
does "reset" to the expected 2-window layout.