mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-01-11 14:40:25 +01:00
[BUG]: Autohotkey.exe cannot be found #371
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 @Haisaru on GitHub (May 10, 2024).
Running korombic.exe start --ahk does not find autohotkey v2. Results in
Error: could not find autohotkey, please make sure it is installed before using the --ahk flagSteps to reproduce the behavior:
C:\Users\User\AppData\Local\Programs\AutoHotkey\v2to pathFor example:
It looks like, on line 1769 in
komorebi/komorebic/src/main.rslet mut ahk: String = String::from("autohotkey.exe");only checks for autohotkey.exe.By default C:\Users\User\AppData\Local\Programs\AutoHotkey\v2 contains 3 files, AutoHotkey.chm, AutoHotkey32.exe, and AutoHotkey64.exe
Renaming AutoHotkey64.exe -> AutoHotkey.exe seems to fix things for me.
@LGUG2Z commented on GitHub (May 10, 2024):
Please use the
KOMOREBI_AHK_EXEenvironment variable to set the executable name for whichever binary gets created with your AHK installation method.As far as this project is concerned, what you and other users are experiencing here is an AHK packaging bug; the AHK project needs to decide on a single binary naming convention for installations of AHK via all methods (scoop, winget, msi, whatever it is).
We're not going to add lines and lines of codes to
komorebicto handle N numbers of different possible AHK executable names.@LGUG2Z commented on GitHub (May 10, 2024):
https://lgug2z.github.io/komorebi/troubleshooting.html#autohotkey-executable-not-found added to the docs here