starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: autostart broken with --ahk flag #645

New Issue
Closed
opened 2026-01-05 14:52:09 +01:00 by adam · 3 comments
adam commented 2026-01-05 14:52:09 +01:00
Owner
Copy Link

Originally created by @laur89 on GitHub (Jun 26, 2025).

Summary

I have both komorebi and AHK installed via chocolatey.

As the latter is in a nonstandard location, I set the KOMOREBI_AHK_EXE env var in my POSH profile as per troubleshooting.

Then I enabled autostart via

$ komorebic.exe enable-autostart --bar --ahk

that created the .lnk file in the autostart directory. But autostart still doesn't work. The created link targets "C:\Program Files\komorebi\bin\komorebic-no-console.exe" start --bar --ahk. Running this command in terminal (not in POSH!) also fails, but silently -- no error, no nothing.

I suspect this is due to autostart logic bypassing POSH altogether, meaning the KOMOREBI_AHK_EXE env var set in our profile is not accessed.

Potential solutions:

  1. make sure the created autostart link executes via posh, ensuring config set in its profile is always picked up.
  2. add documentation instructing users to set system-wide env var like in this issue for KOMOREBI_CONFIG_HOME env var. I believe my issue is duplicate of that, only for KOMOREBI_AHK_EXE env var.

Version Information

Windows 11
komorebi 0.1.37

Komorebi Configuration

N/A

Hotkey Configuration

N/A

Output of komorebic check

N/A

Originally created by @laur89 on GitHub (Jun 26, 2025). ### Summary I have both komorebi and AHK installed via chocolatey. As the latter is in a nonstandard location, I set the `KOMOREBI_AHK_EXE` env var in my POSH profile as per [troubleshooting](https://lgug2z.github.io/komorebi/troubleshooting.html). Then I enabled [autostart](https://lgug2z.github.io/komorebi/common-workflows/autostart.html) via ```sh $ komorebic.exe enable-autostart --bar --ahk ``` that created the .lnk file in the autostart directory. But autostart still doesn't work. The created link targets `"C:\Program Files\komorebi\bin\komorebic-no-console.exe" start --bar --ahk`. Running this command in terminal (_not_ in POSH!) also fails, but silently -- no error, no nothing. I suspect this is due to autostart logic bypassing POSH altogether, meaning the `KOMOREBI_AHK_EXE` env var set in our profile is not accessed. --- Potential solutions: 1. make sure the created autostart link executes via posh, ensuring config set in its profile is always picked up. 2. add documentation instructing users to set system-wide env var like in [this issue](https://github.com/LGUG2Z/komorebi/issues/881#issuecomment-2338089110) for KOMOREBI_CONFIG_HOME env var. I believe my issue is duplicate of that, only for KOMOREBI_AHK_EXE env var. ### Version Information Windows 11 komorebi [0.1.37](https://community.chocolatey.org/packages/komorebi/0.1.37) ### Komorebi Configuration ```json N/A ``` ### Hotkey Configuration N/A ### Output of komorebic check N/A
adam added the bug label 2026-01-05 14:52:09 +01:00
adam closed this issue 2026-01-05 14:52:09 +01:00
adam commented 2026-01-05 14:52:10 +01:00
Author
Owner
Copy Link

@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

@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
adam commented 2026-01-05 14:52:10 +01:00
Author
Owner
Copy Link

@laur89 commented on GitHub (Oct 17, 2025):

Sorry which feature is eol? Komorebic or using komorebic to launch ahk script?

Will the next ver bump provide any guidance for migration?

@laur89 commented on GitHub (Oct 17, 2025): Sorry which feature is eol? Komorebic or using komorebic to launch ahk script? Will the next ver bump provide any guidance for migration?
adam commented 2026-01-05 14:52:10 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Oct 17, 2025):

Full commit is here: 62303eebdf

Any --ahk flags are being marked as EOL and won't be worked on any further

Code probably won't be removed for a few years, but there will of course be a migration guide for everything that is EOL whenever there is a major version bump

@LGUG2Z commented on GitHub (Oct 17, 2025): Full commit is here: https://github.com/LGUG2Z/komorebi/commit/62303eebdfc2231e8506997ebc8c1b273a84bd59 Any `--ahk` flags are being marked as EOL and won't be worked on any further Code probably won't be removed for a few years, but there will of course be a migration guide for everything that is EOL whenever there is a major version bump
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#645
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?