Looking for configuration files in C:\Users\abc.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\abc.config\whkd\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Originally created by @johnnydepup on GitHub (Aug 11, 2025).
### Summary
I have AHK installed, and I have set the environment variable `$Env:KOMOREBI_AHK_EXE` to the Autothokey64.exe file.
When I start with `--ahk`, it works only when I give the full path in the env variable and not a relative path with `~`.
```
C:/Users/abc/AppData/Local/Programs/AutoHotkey/v2/AutoHotkey64.exe ->Works
~/AppData/Local/Programs/AutoHotkey/v2/AutoHotkey64.exe -> Does not work
```
This is odd because in my `$PROFILE` file, Komorebi's config home is set with `~` and that is working.
Am I missing something here? It is supposed to work, right?
### Version Information
komorebic 0.1.37
tag:v0.1.37
commit_hash:00384ce3
build_time:2025-05-17 19:16:53 +00:00
build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc
### Komorebi Configuration
```json
-
```
### Hotkey Configuration
-
### Output of komorebic check
KOMOREBI_CONFIG_HOME detected: C:\Users\abc\.config\komorebi
Looking for configuration files in C:\Users\abc\.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\abc\.config\whkd\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
adam
added the bug label 2026-01-05 14:52:14 +01:00
can you test it with using $Env:USERPROFILE in the powershell?
something like this: $Env:KOMOREBI_AHK_EXE = "$Env:USERPROFILE\scoop\apps\autohotkey\current\UX\AutoHotkeyUX.exe"
@azinsharaf commented on GitHub (Oct 15, 2025):
can you test it with using `$Env:USERPROFILE` in the powershell?
something like this:
`$Env:KOMOREBI_AHK_EXE = "$Env:USERPROFILE\scoop\apps\autohotkey\current\UX\AutoHotkeyUX.exe"`
Closing issues related to launching AHK from komorebic because this feature is now EOL, meaning no more work will be done on it and it will eventually be dropped during a major version bump
@LGUG2Z commented on GitHub (Oct 17, 2025):
Closing issues related to launching AHK from `komorebic` because this feature is now EOL, meaning no more work will be done on it and it will eventually be dropped during a major version bump
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @johnnydepup on GitHub (Aug 11, 2025).
Summary
I have AHK installed, and I have set the environment variable
$Env:KOMOREBI_AHK_EXEto the Autothokey64.exe file.When I start with
--ahk, it works only when I give the full path in the env variable and not a relative path with~.This is odd because in my
$PROFILEfile, Komorebi's config home is set with~and that is working.Am I missing something here? It is supposed to work, right?
Version Information
komorebic 0.1.37
tag:v0.1.37
commit_hash:00384ce3
build_time:2025-05-17 19:16:53 +00:00
build_env:rustc 1.87.0 (17067e9ac 2025-05-09),stable-x86_64-pc-windows-msvc
Komorebi Configuration
Hotkey Configuration
Output of komorebic check
KOMOREBI_CONFIG_HOME detected: C:\Users\abc.config\komorebi
Looking for configuration files in C:\Users\abc.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\abc.config\whkd\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@azinsharaf commented on GitHub (Oct 15, 2025):
can you test it with using
$Env:USERPROFILEin the powershell?something like this:
$Env:KOMOREBI_AHK_EXE = "$Env:USERPROFILE\scoop\apps\autohotkey\current\UX\AutoHotkeyUX.exe"@LGUG2Z commented on GitHub (Oct 17, 2025):
Closing issues related to launching AHK from
komorebicbecause this feature is now EOL, meaning no more work will be done on it and it will eventually be dropped during a major version bump