#Komorebi only launches when Run without await-configuration

1 messages · Page 1 of 1 (latest)

wraith badge
#

I have YASB installed, and have recently upgraded my boot drive to an ssd (my first thought was the config path wasn't correct but pwsh $PROFILE has the $Env:KOMOREBI_CONFIG_HOME = 'C:\Users\USERNAME-HERE.config\komorebi' in it. My second thought was it could be whkdrc in the wrong path. But that isn't the case either. Is there like a verbose way to launch komorebic So I could get more information?

as right now all I know is sometimes when launched No tiling happens, then I have to restart my pc to get it working again.

wraith badge
#

I realize I should probably share my config

if (!(Get-Process whkd -ErrorAction SilentlyContinue))
{
    Start-Process whkd -WindowStyle hidden
}

. $PSScriptRoot\komorebi.generated.ps1

# Send the ALT key whenever changing focus to force focus changes
komorebic alt-focus-hack enable
# Default to cloaking windows when switching workspaces
komorebic window-hiding-behaviour cloak
# Set cross-monitor move behaviour to insert instead of swap
komorebic cross-monitor-move-behaviour insert
# Enable hot reloading of changes to this file
komorebic watch-configuration enable

# Create named workspaces I-V on monitor 0
komorebic ensure-named-workspaces 0 I II III IV V
# You can do the same thing for secondary monitors too
# komorebic ensure-named-workspaces 1 A B C D E F

# Assign layouts to workspaces, possible values: bsp, columns, rows, vertical-stack, horizontal-stack, ultrawide-vertical-stack
komorebic named-workspace-layout I bsp

# Set the gaps around the edge of the screen for a workspace
komorebic named-workspace-padding I 20
# Set the gaps between the containers for a workspace
komorebic named-workspace-container-padding I 20

# You can assign specific apps to named workspaces
# komorebic named-workspace-rule exe "Firefox.exe" III

# Configure the invisible border dimensions
komorebic invisible-borders 7 0 14 7

# Uncomment the next lines if you want a visual border around the active window
komorebic active-window-border-colour 31 30 28 --window-kind single
komorebic active-window-border-colour 53 65 87 --window-kind stack
komorebic active-window-border-colour 85 57 61 --window-kind monocle
komorebic active-window-border enable

# komorebic identify-border-overflow-application exe wezterm-gui.exe

komorebic complete-configuration

mellow jay
#

Can you share the output of the logs when you just run komorebi and also the output of komorebic check

#

It's most likely that your komorebi.ps1 file isn't being loaded

#

This is usually down to either mislocation or an issue with calling PowerShell from the system $PATH

wraith badge
#

komorebic check output:

KOMOREBI_CONFIG_HOME detected:C:\Users\Jamie\.config\komorebi
Looking for configuration files in C:\Users\Jamie\.config\komorebi

Found komorebi.ps1; this file will be autoloaded by komorebi

Found ~/.config/whkdrc; key bindings will be loaded from here when whkd is started                               

And it launches now, Hmmmm. I guess I just had to end process tree on komorebi.exe.

Log is attached anyways.

mellow jay
#
2023-07-09T20:28:07.224329Z  INFO komorebi: loading configuration file: C:\Users\Jamie\.config\komorebi\komorebi.ps1

Yeah it seems ok now, and since you have complete-configuration at the end you should be able to start with that as well