You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I created a lovely floating + tiled window and I saved it using i3-resurrect. The mark on the outer frame is present in the json file (attached), but it is not restored when I restore the window.
To Reproduce
Steps to reproduce the behavior:
Create a floating window containing multiple tiles.
Mark its outermost parent, so that you can send it to the scratchpad.
i3-resurrect save -w __i3_scratch -p bunchawindows
Close float.
i3-resurrect restore -p bunchawindows
Expected behavior
The restored window should have the mark, but it doesn't.
System information (please complete the following information):
Linux distribution: Ubuntu 18.04
i3-resurrect version (output of i3-resurrect --version): 1.4.3
i3 version (output of i3 -v): 4.19
Python version (output of python -V): 3.6.9
The text was updated successfully, but these errors were encountered:
How are you even able to do i3-resurrect save -w __i3_scratch -p bunchawindows? According to #97 I would've expected this not to even save successfully.
Oh sorry I must be blind, didn't reread properly before asking that.. Hmm I'm not sure there's anything that I can do if the mark is saved in the layout file but not being restored by i3 itself. That would probably need changing in i3 itself.
Describe the bug
I created a lovely floating + tiled window and I saved it using i3-resurrect. The mark on the outer frame is present in the json file (attached), but it is not restored when I restore the window.
To Reproduce
Steps to reproduce the behavior:
i3-resurrect save -w __i3_scratch -p bunchawindows
i3-resurrect restore -p bunchawindows
Expected behavior
The restored window should have the mark, but it doesn't.
System information (please complete the following information):
i3-resurrect --version
): 1.4.3i3 -v
): 4.19python -V
): 3.6.9The text was updated successfully, but these errors were encountered: