[BUG]: Autostart with AHK "Script file not found"

[melMass]

Describe the bug When using the --ahk flag of autostart I'm now getting this error

Tbh I'm not sure of what komorebi expects, I did copy the lib there to be sure too yet it still errors out

Expected behavior A clearer error.

Screenshots and Videos

Operating System Provide the output of systeminfo | grep "^OS Name\|^OS Version"

For example:

OS Name:                   Microsoft Windows 11 Pro
OS Version:                10.0.22000 N/A Build 22000

komorebic check Output

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\User

Looking for configuration files in C:\Users\User

No komorebi configuration found in C:\Users\User

If running 'komorebic start --await-configuration', you will manually have to call the following command to begin tiling: komorebic complete-configuration

Additional Context

The content of my AHK script:

#Requires AutoHotkey v2.0

#SingleInstance
#Include lib/komorebic.lib.ahk

;- KOMOREBIC
; Ctrl - ^
; Alt - !
; Shift - +
; Win - #

; AltFocusHack("enable")

; Focus windows
!h::Focus("left")
!j::Focus("down")
!k::Focus("up")
!l::Focus("right")
!+[::CycleFocus("previous")
!+]::CycleFocus("next")

!Enter::{
    RunWait("C:/Users/User/.cargo/bin/alacritty.exe --working-directory C:/Users/User")
}

; Move windows
!Left::Move("left")
!Down::Move("down")
!Up::Move("up")
!Right::Move("right")
!+Enter::Promote()

; Stack windows
!+Left::Stack("left")
!+Right::Stack("right")
!+Up::Stack("up")
!+Down::Stack("down")
!u::Unstack()
![::CycleStack("previous")
!]::CycleStack("next")

; Resize
!NumpadAdd::ResizeAxis("vertical", "increase")
!NumpadSub::ResizeAxis("vertical", "decrease")
!NumpadMult::ResizeAxis("horizontal", "increase")
!NumpadDiv::ResizeAxis("horizontal", "decrease")

; Manipulate wineows
!t::ToggleFloat()
!+f::ToggleMonocle()

; Window manager options
!+r::Retile()
!p::TogglePause()

; Layouts
!x::FlipLayout("horizontal")
!y::FlipLayout("vertical")
!+l::CycleLayout("next")

; Workspaces
!&::{
    FocusWorkspace(0)
}
!SC003::FocusWorkspace(1)
!SC004::FocusWorkspace(2)
!SC005::FocusWorkspace(3)
!SC006::FocusWorkspace(4)
!SC007::FocusWorkspace(5)
!SC008::FocusWorkspace(6)
!SC009::FocusWorkspace(7)
!SC00A::FocusWorkspace(8)

; Move windows across workspaces
!+1::MoveToWorkspace(0)
!+2::MoveToWorkspace(1)
!+3::MoveToWorkspace(2)
!+4::MoveToWorkspace(3)
!+5::MoveToWorkspace(4)
!+6::MoveToWorkspace(5)
!+7::MoveToWorkspace(6)
!+8::MoveToWorkspace(7)
!+9::MoveToWorkspace(8)

; Caps lock as Esc
Capslock::Esc

[jpmiller25]

I have this same issue, reported here. https://github.com/LGUG2Z/komorebi/issues/645 As a workaround, I added a link to the autohotkey script to the startup folder to start it independently. Someone suggested making sure the executable name is autohotkey.exe, and that it's in your path environment variable. IDK, didn't fix it for me, I have ahk installed through scoop which puts everything in the path.

[LGUG2Z]

I'm not seeing anything obvious in the code that would cause this.

start tries to locate the ahk file using HOME_DIR: https://github.com/LGUG2Z/komorebi/blob/5e714cafab61a5fd8a9bb11adf14504ffe609135/komorebic/src/main.rs#L1855

HOME_DIR respects the KOMOREBI_CONFIG_HOME environment variable: https://github.com/LGUG2Z/komorebi/blob/5e714cafab61a5fd8a9bb11adf14504ffe609135/komorebic/src/main.rs#L62

enable-autostart constructs a shortcut file which calls the start command with the --ahk flag: https://github.com/LGUG2Z/komorebi/blob/5e714cafab61a5fd8a9bb11adf14504ffe609135/komorebic/src/main.rs#L1302

... which respects the custom config home env var, etc.

Maybe someone else can take a look and see if I'm missing something here?

[Zerogaku]

I have the same problem, I manually compiled komorebi.

[Zerogaku]

I also tried placing a shortcut to the autohotkey script, and adding a line in the autohotkey script that autostarts komorebi:

RunWait("komorebic.exe start", ,"Hide")

What I found was that komorebi did startup, but it did not use the komorebi.json or applications.yaml, so application windows weren't being placed correctly and configurations like window borders didn't display. and if I ran:

RunWait("komorebic.exe start --ahk", ,"Hide")

It would just give me an error saying komorebi.ahk not found

[gzachariadis]

Same thing here, I second this issue, setting a custom config home, doesn't stop the client from looking at the wrong place, Either we have to find a way to specify where to look for the ahk script, or find a way to set an enviroment variable for Command Prompt.