[BUG]: komorebic start no longer works with no arguments in 0.1.18 #229

New Issue

2026-01-05T14:49:08+01:00

adam commented

2026-01-05 14:49:08 +01:00

Originally created by @notkvwu on GitHub (Jul 15, 2023).

Originally assigned to: @LGUG2Z on GitHub.

Describe the bug
komorebic start no longer works with no arguments

To Reproduce
Run komorebic start with no arguments

Expected behavior
Komorebi starts as it always has

Operating System

OS Name:                   Microsoft Windows 11 Enterprise
OS Version:                10.0.22621 N/A Build 22621

komorebic check Output
Komorebi does not start

Additional context
It looks like komorebi tries to execute

Start-Process komorebi.exe -ArgumentList  -WindowStyle hidden

But this is not valid powershell since ArgumentList must have a value. I assume it was introduced in this commit https://github.com/LGUG2Z/komorebi/commit/4510cccc3e7efb548e48ceb69ae5a20768ade4aa.

I know the guides have switched to komorebic start --await-configuration, which works perfectly fine. But I thought maybe this was unintended, so I thought I'd create a bug report.

Originally created by @notkvwu on GitHub (Jul 15, 2023). Originally assigned to: @LGUG2Z on GitHub. **Describe the bug** `komorebic start` no longer works with no arguments **To Reproduce** Run `komorebic start` with no arguments **Expected behavior** Komorebi starts as it always has **Operating System** ``` OS Name: Microsoft Windows 11 Enterprise OS Version: 10.0.22621 N/A Build 22621 ``` **`komorebic check` Output** Komorebi does not start **Additional context** It looks like komorebi tries to execute ``` Start-Process komorebi.exe -ArgumentList -WindowStyle hidden ``` But this is not valid powershell since `ArgumentList` must have a value. I assume it was introduced in this commit https://github.com/LGUG2Z/komorebi/commit/4510cccc3e7efb548e48ceb69ae5a20768ade4aa. I know the guides have switched to `komorebic start --await-configuration`, which works perfectly fine. But I thought maybe this was unintended, so I thought I'd create a bug report.

adam added the bug label 2026-01-05 14:49:08 +01:00

adam closed this issue

2026-01-05 14:49:09 +01:00

adam commented

2026-01-05 14:49:09 +01:00

@LGUG2Z commented on GitHub (Jul 15, 2023):

This is definitely a regression ^

Will make sure this is fixed going into the next release. In the meantime, people who specifically still want to start the program like this can run Start-Process komorebi.exe -WindowStyle hidden instead of komorebic start.

@LGUG2Z commented on GitHub (Jul 15, 2023): This is definitely a regression ^ Will make sure this is fixed going into the next release. In the meantime, people who specifically still want to start the program like this can run `Start-Process komorebi.exe -WindowStyle hidden` instead of `komorebic start`.

adam commented

2026-01-05 14:49:09 +01:00

@davorklju commented on GitHub (Sep 11, 2023):

Hey new user.
Does running the above command respect the komorebi_config_dir env variable? On my end it's staring up with the default config.
Just want to make sure if it's an issue on my end.

@davorklju commented on GitHub (Sep 11, 2023): Hey new user. Does running the above command respect the komorebi_config_dir env variable? On my end it's staring up with the default config. Just want to make sure if it's an issue on my end.

adam commented

2026-01-05 14:49:09 +01:00

@LGUG2Z commented on GitHub (Sep 11, 2023):

Running the above command does respect the config environment variable, as this is looked up once komorebi has started, not during the PS command execution. I'm actually working on a fix for this regression as we speak. 😅

@LGUG2Z commented on GitHub (Sep 11, 2023): Running the above command does respect the config environment variable, as this is looked up once `komorebi` has started, not during the PS command execution. I'm actually working on a fix for this regression as we speak. 😅

adam commented

2026-01-05 14:49:09 +01:00