mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Unstack, cycle-stack and workspace hotkeys not working #654
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 @kangroozeeh on GitHub (Jul 27, 2025).
Summary
All my hotkeys are working, except the unstack, cycle-stack and workspace commands, no matter what I change them to. If I leave them at oem_1 (or oem_4, oem_6) it also doesn't work (neither with German nor US layout).
Version Information
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
.shell powershell
Reload whkd configuration
alt + o : taskkill /f /im whkd.exe && start /b whkd # if shell is cmd
alt + o : taskkill /f /im whkd.exe; Start-Process whkd -WindowStyle hidden # if shell is pwsh / powershell
alt + shift + o : komorebic reload-configuration
alt + i : komorebic toggle-shortcuts
App shortcuts - these require shell to be pwsh / powershell
The apps will be focused if open, or launched if not open
alt + f : if ($wshell.AppActivate('Firefox') -eq $False) { start firefox }
alt + b : if ($wshell.AppActivate('Chrome') -eq $False) { start chrome }
alt + x : komorebic close
alt + q : komorebic minimize
Focus windows
alt + a : komorebic focus left
alt + s : komorebic focus down
alt + w : komorebic focus up
alt + d : komorebic focus right
alt + shift + oem_4 : komorebic cycle-focus previous # oem_4 is [
alt + shift + oem_6 : komorebic cycle-focus next # oem_6 is ]
Move windows
alt + shift + a : komorebic move left
alt + shift + s : komorebic move down
alt + shift + w : komorebic move up
alt + shift + d : komorebic move right
alt + e : komorebic promote
Stack windows
alt + left : komorebic stack left
alt + down : komorebic stack down
alt + up : komorebic stack up
alt + right : komorebic stack right
alt + ö : komorebic unstack # oem_1 is ;
alt + shift + y : komorebic cycle-stack previous # oem_4 is [
alt + shift + c : komorebic cycle-stack next # oem_6 is ]
Resize
alt + oem_plus : komorebic resize-axis horizontal increase
alt + oem_minus : komorebic resize-axis horizontal decrease
alt + shift + oem_plus : komorebic resize-axis vertical increase
alt + shift + oem_minus : komorebic resize-axis vertical decrease
Manipulate windows
alt + t : komorebic toggle-float
alt + shift + e : komorebic toggle-monocle
Window manager options
alt + shift + r : komorebic retile
alt + p : komorebic toggle-pause
alt + m : komorebic manage
Layouts
alt + x : komorebic flip-layout horizontal
alt + y : komorebic flip-layout vertical
Workspaces
alt + 1 : komorebic focus-workspace 0
alt + 2 : komorebic focus-workspace 1
alt + 3 : komorebic focus-workspace 2
alt + 4 : komorebic focus-workspace 3
alt + 5 : komorebic focus-workspace 4
alt + 6 : komorebic focus-workspace 5
alt + 7 : komorebic focus-workspace 6
alt + 8 : komorebic focus-workspace 7
Move windows across workspaces
alt + shift + 1 : komorebic move-to-workspace 0
alt + shift + 2 : komorebic move-to-workspace 1
alt + shift + 3 : komorebic move-to-workspace 2
alt + shift + 4 : komorebic move-to-workspace 3
alt + shift + 5 : komorebic move-to-workspace 4
alt + shift + 6 : komorebic move-to-workspace 5
alt + shift + 7 : komorebic move-to-workspace 6
alt + shift + 8 : komorebic move-to-workspace 7
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\zbign
Looking for configuration files in C:\Users\zbign
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\zbign.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@omark96 commented on GitHub (Aug 3, 2025):
Just to make sure, are you certain that you have actually stacked the windows and you have the stack focused when you try these commands?
@chuahziyang commented on GitHub (Sep 16, 2025):
im getting the same bug