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
I found that after Windows sleep, monitors[1] and monitors[2] get swapped. I would say this happens pretty much every time, or nearly as frequent. My solution is to swap the values in the .json file manually every time. So essentially I keep rotating b and c to fix the issue.
At this point I've probably done it a few dozen times.
Version Information
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22631 N/A Build 22631
.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
# 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 + m : komorebic minimize
# Focus windows
alt + h : komorebic focus left
alt + j : komorebic focus down
alt + k : komorebic focus up
alt + l : 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 + h : komorebic move left
alt + shift + j : komorebic move down
alt + shift + k : komorebic move up
alt + shift + l : komorebic move right
alt + shift + return : 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 + oem_1 : komorebic unstack # oem_1 is ;
alt + oem_4 : komorebic cycle-stack previous # oem_4 is [
alt + oem_6 : 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 + f : komorebic toggle-monocle
# Window manager options
alt + shift + r : komorebic retile
alt + shift + p : komorebic toggle-pause
# 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
# 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
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\alex
Looking for configuration files in C:\Users\alex
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\alex\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
The text was updated successfully, but these errors were encountered:
Thank you for you help, unfortunately I already have display_index_preferences in my config referenced above and so I believe the problem is elsewhere.
Summary
I'm experiencing repeated monitor ID issue. I have 3 monitors arranged in this configuration:
The
monitor-information
always returns this for me:My config has the following:
I found that after Windows sleep,
monitors[1]
andmonitors[2]
get swapped. I would say this happens pretty much every time, or nearly as frequent. My solution is to swap the values in the.json
file manually every time. So essentially I keep rotatingb
andc
to fix the issue.At this point I've probably done it a few dozen times.
Version Information
Komorebi Configuration
Hotkey Configuration
Output of komorebic check
The text was updated successfully, but these errors were encountered: