mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Autostart with AHK "Script file not found" #320
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 @melMass on GitHub (Mar 30, 2024).
Describe the bug
When using the
--ahkflag of autostart I'm now getting this errorTbh 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:
komorebic checkOutputAdditional Context
The content of my AHK script:
@jpmiller25 commented on GitHub (Apr 5, 2024):
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 commented on GitHub (Apr 6, 2024):
I'm not seeing anything obvious in the code that would cause this.
starttries to locate the ahk file usingHOME_DIR:5e714cafab/komorebic/src/main.rs (L1855)HOME_DIRrespects theKOMOREBI_CONFIG_HOMEenvironment variable:5e714cafab/komorebic/src/main.rs (L62)enable-autostartconstructs a shortcut file which calls thestartcommand with the--ahkflag:5e714cafab/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 commented on GitHub (Apr 8, 2024):
I have the same problem, I manually compiled komorebi.
@Zerogaku commented on GitHub (Apr 8, 2024):
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
@stereotypicaldev commented on GitHub (Jun 17, 2024):
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.
@jklasdjklasdc commented on GitHub (Dec 7, 2024):
instead of
RunWait("komorebic.exe start", ,"Hide")
do
RunWait("komorebic.exe start", A_ScriptDir, "Hide")
to start the command in the current directory
@alan12345678 commented on GitHub (Jan 12, 2025):
I'm having this issue even now. I copied the example config from the website, haven't modified it yet. I think I've done everything correctly...
I have komorebi.ahk in C:\Users\User, I installed the latest version of AHK (2.0.18)
I ran
komorebic.exe enable-autostart --masir --ahkand it didn't complain, but when I logged out and back in again, komorebi isn't running. I could use whkd but prefer AHK.@LGUG2Z commented on GitHub (Jan 23, 2025):
Covered in the troubleshooting part of the doc site: https://lgug2z.github.io/komorebi/troubleshooting.html#autohotkey-executable-not-found
Ahk packaging is unfortunately very confusing and fragmented; from my side since the ability to specify a custom executable name is available, this is issue will be closed.