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

Restore workspaces to output on re-enable #1852

Closed
edrex opened this issue Mar 22, 2023 · 3 comments
Closed

Restore workspaces to output on re-enable #1852

edrex opened this issue Mar 22, 2023 · 3 comments
Labels
0: low prio Low priority - minor impact on usability enhancement New feature or request

Comments

@edrex
Copy link

edrex commented Mar 22, 2023

I frequently plug/unplug my laptop from external displays. Each time I reconnect, I have to restore workspaces to the reconnected output manually.

t would be nice if hyprland remembered which workspaces were on an output on output disconnect, and restored them to that output on reconnect.

Implementation in sway: swaywm/sway#2115

@edrex edrex added the enhancement New feature or request label Mar 22, 2023
@vaxerski vaxerski added the 0: low prio Low priority - minor impact on usability label Mar 22, 2023
@CryoMyst
Copy link

CryoMyst commented May 3, 2023

This is a major issue for me as my main monitor is an OLED I frequently turn off. Workaround currently is to move everything to another workspace and back again. This is annoying to have to do many times a day.

@vaxerski
Copy link
Member

vaxerski commented May 3, 2023

fixed in fd3e6a3

@vaxerski vaxerski closed this as completed May 3, 2023
@flajann2
Copy link

I probably should submit this as a feature request. But it would be beyond cool if, after I, say, restart the hyprland session, that it can restore the total state of off my windows across all the virtual desktops and attached monitors.

Everytime I have to reboot after a kernel upgrade, there are 30 or so browser and other windows I have to send to the places I need them to be. That gets annoying. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0: low prio Low priority - minor impact on usability enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants