Closed allora closed 1 month ago
When the ghost tile is there, run "komorebic visible-windows" to get the information you need about it to add a rule ignoring it: https://lgug2z.github.io/komorebi/common-workflows/ignore-windows.html
Also for anyone having the same issues: temporary workaround I've been using for stuff I don't want to bother making special rules for is to switch to the window with alt + hjlk (or whatever) and then minimizing it with alt + m (or whatever).
It would be nice if the heuristics detected invisible windows though.
Summary
Using Unreal Engine 5 (seems any version will do this, unsure of unreal engine 4), starting the editor will create a phantom window. I can alt F4 on this window and close it, but it consumes a tile in Komorebi until then. Ultimately this is probably something unreal is doing, but i wonder if Komorebi can just.. ignore it heh
Version Information
OS Name: Microsoft Windows 10 Pro OS Version: 10.0.19045 N/A Build 19045
komorebic 0.1.29 tag:v0.1.29 commit_hash:818ac340 build_time:2024-09-28 01:48:31 +00:00 build_env:rustc 1.81.0 (eeb90cda1 2024-09-04),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
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 }
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 + 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 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 alt + 9 : komorebic focus-workspace 8 alt + 0 : komorebic focus-workspace 9
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 alt + shift + 9 : komorebic move-to-workspace 8 alt + shift + 0 : komorebic move-to-workspace 9
Output of komorebic check
No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\
Looking for configuration files in C:\Users\
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag