mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Taskbar and workspace visibility issues with restricted apps and multiple monitors #638
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 @hsayed21 on GitHub (Jun 8, 2025).
Summary
I'm encountering two usability issues while using komorebi with multiple monitors and workspace-restricted apps:
When using workspaces with app restrictions (e.g., only allowing Chrome in workspace 3.WEB), the taskbar still displays all open apps from all workspaces, not just the apps assigned to the active workspace.
Expected behavior:
Current behavior (screenshot below):
I have two monitors. When switching focus to a workspace on one monitor (e.g., 3.WEB), the active workspace is shown on both monitors (e.g., 1.Home and 3.WEB both appear active).
Expected behavior:
Would love to hear your thoughts or guidance on potential fixes or workarounds!
Thanks for the awesome tool 🙌
Version Information
└─# komorebic --version
komorebic 0.1.37
tag:v0.1.37
commit_hash:00384ce3
build_time:2025-05-17 19:16:53 +00:00
build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc
Komorebi Configuration
Hotkey Configuration
_
Output of komorebic check
└─# komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\hsayed
Looking for configuration files in C:\Users\hsayed
Found komorebi.json; this file can be passed to the start command with the --config flag
"focus_follows_mouse" is now end-of-life
End-of-life features will not receive any further bug fixes or updates; they should not be used
Found C:\Users\hsayed.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@LGUG2Z commented on GitHub (Jun 8, 2025):
Both of these are the intended behaviours, but if you want to work on adding alternative opt-in behaviours, you can open a draft PR for implementation feedback.
@hsayed21 commented on GitHub (Jun 9, 2025):
@LGUG2Z
Sorry, I didn’t understand what was meant… I don’t have experience with Rust language to open PR