mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: "Hide" hiding behavior does not unhide windows when re-opening workspace #608
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @YelovSK on GitHub (May 2, 2025).
Summary
When using the "hide" window hiding behavior, switching to another workspace correctly makes the windows disappear, but when coming back to the workspace, the windows do not reappear and stay hidden.
https://github.com/user-attachments/assets/1ee8bde0-3075-47bf-a071-b9e2b22a95f9
^^ The VS Code window does not reappear when I switch back to the 3rd workspace (it happens for all Windows, not just VS Code)
Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.26100 N/A Build 26100
komorebic 0.1.36
Komorebi Configuration
Hotkey Configuration
Output of komorebic check
@LGUG2Z commented on GitHub (May 2, 2025):
I think this is more of a documentation nit to mark "Hide" as EOL - there are too many issues with this approach and it isn't being developed further - "Cloak" is now the default (this is also what Virtual Desktops uses) and what all users are encouraged to use
@YelovSK commented on GitHub (May 2, 2025):
Oh okay. In that case is there a way to show only programs from the current workspace in the taskbar? My issue with cloak is that the windows are hidden visually, but my taskbar is cluttered because it' always showing windows from all workspaces.
@LGUG2Z commented on GitHub (May 3, 2025):
Curiosity is getting the better of me so I'm trying to bisect to find exactly which commit broke this, because the Hide behaviour has not really been touched for years now
The last version where Hide works as expected is 0.1.33
@LGUG2Z commented on GitHub (May 3, 2025):
Looks like I shot the sheriff:
80b611890a@LGUG2Z commented on GitHub (May 3, 2025):
The fix for the regression will be in the next nightly and the next numbered release