[BUG]: Variable names are case-sensitive in komorebic start #469

New Issue

2026-01-05T14:50:56+01:00

adam commented

2026-01-05 14:50:56 +01:00

Originally created by @CAESIUS-TIM on GitHub (Sep 12, 2024).

Describe the bug

Variable names are case-insensitive in both `pwsh` and `cmd`.

pwsh: 7.5.0-preview.4

❯ $eNv:koMOREbi_conFig_hOmE
C:\Users\26523\.config\komorebi

cmd: Version 10.0.22631.4169

C:\Users\26523>echo %kOmOrebI_cOnfiG_HomE%
C:\Users\26523\.config\komorebi

Variable names are case-sensitive in `komorebic start`

To run komorebic start with komorebi.json

komorebi.json must be:

// Ok
"app_specific_configuration_path": "$Env:KOMOREBI_CONFIG_HOME/applications.yaml",

And even $env is not ok:

// Fail with lowercase `e` in start
"app_specific_configuration_path": "$env:KOMOREBI_CONFIG_HOME/applications.yaml",

komorebic: 0.1.28

❯ komorebic start --ahk
Start-Process 'komorebi.exe' -WindowStyle hidden
Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again
Start-Process 'komorebi.exe' -WindowStyle hidden
Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again
Start-Process 'komorebi.exe' -WindowStyle hidden
Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again

Running komorebi.exe directly for detailed error output

Error:
   0: 文件名、目录名或卷标语法不正确。 (os error 123)

Location:
   komorebi\src\static_config.rs:782

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   1: BaseThreadInitThunk<unknown>
      at <unknown source file>:<unknown line>
   2: RtlUserThreadStart<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.

To Reproduce

Steps to reproduce the behavior:

Edit komorebic.json
Toggle one or more letter upper/lower case in app_specific_configuration_path's variable names.
Start komorebi

Operating System

OS Name:                   Microsoft Windows 11 家庭中文版
OS Version:                10.0.22631 N/A Build 22631

`komorebic check` Output

KOMOREBI_CONFIG_HOME detected: C:\Users\26523\.config\komorebi

Looking for configuration files in C:\Users\26523\.config\komorebi

Found komorebi.json; this file can be passed to the start command with the --config flag

Application specific configuration file path '$env:KOMOREBI_CONFIG_HOME/applications.yaml' does not exist. Try running 'komorebic fetch-asc'

No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard

Additional context

It seems that komorebic fetch-asc is case-insensitive.

❯ komorebic fetch-asc
Latest version of applications.yaml from https://github.com/LGUG2Z/komorebi-application-specific-configuration downloaded

You can add this to your komorebi.json static configuration file like this:

"app_specific_configuration_path": "C:\Users\26523\.config\komorebi\applications.yaml"

Originally created by @CAESIUS-TIM on GitHub (Sep 12, 2024). ## **Describe the bug** ### Variable names are case-insensitive in both `pwsh` and `cmd`. - pwsh: 7.5.0-preview.4 ```pwsh ❯ $eNv:koMOREbi_conFig_hOmE C:\Users\26523\.config\komorebi ``` - cmd: Version 10.0.22631.4169 ```cmd C:\Users\26523>echo %kOmOrebI_cOnfiG_HomE% C:\Users\26523\.config\komorebi ``` ### Variable names are case-sensitive in `komorebic start` To run `komorebic start` with `komorebi.json` `komorebi.json` must be: ```jsonc // Ok "app_specific_configuration_path": "$Env:KOMOREBI_CONFIG_HOME/applications.yaml", ``` And even `$env` is not ok: ```jsonc // Fail with lowercase `e` in start "app_specific_configuration_path": "$env:KOMOREBI_CONFIG_HOME/applications.yaml", ``` - komorebic: 0.1.28 ``` ❯ komorebic start --ahk Start-Process 'komorebi.exe' -WindowStyle hidden Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again Start-Process 'komorebi.exe' -WindowStyle hidden Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again Start-Process 'komorebi.exe' -WindowStyle hidden Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again Running komorebi.exe directly for detailed error output Error: 0: 文件名、目录名或卷标语法不正确。 (os error 123) Location: komorebi\src\static_config.rs:782 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1: BaseThreadInitThunk<unknown> at <unknown source file>:<unknown line> 2: RtlUserThreadStart<unknown> at <unknown source file>:<unknown line> Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering. Run with RUST_BACKTRACE=full to include source snippets. ``` ## **To Reproduce** Steps to reproduce the behavior: 1. Edit `komorebic.json` 2. Toggle one or more letter upper/lower case in `app_specific_configuration_path`'s variable names. 3. Start komorebi ## **Operating System** ``` OS Name: Microsoft Windows 11 家庭中文版 OS Version: 10.0.22631 N/A Build 22631 ``` ## **`komorebic check` Output** ``` KOMOREBI_CONFIG_HOME detected: C:\Users\26523\.config\komorebi Looking for configuration files in C:\Users\26523\.config\komorebi Found komorebi.json; this file can be passed to the start command with the --config flag Application specific configuration file path '$env:KOMOREBI_CONFIG_HOME/applications.yaml' does not exist. Try running 'komorebic fetch-asc' No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard ``` ## **Additional context** It seems that `komorebic fetch-asc` is case-insensitive. ``` ❯ komorebic fetch-asc Latest version of applications.yaml from https://github.com/LGUG2Z/komorebi-application-specific-configuration downloaded You can add this to your komorebi.json static configuration file like this: "app_specific_configuration_path": "C:\Users\26523\.config\komorebi\applications.yaml" ```

adam added the bug label 2026-01-05 14:50:56 +01:00

adam closed this issue

2026-01-05 14:50:56 +01:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#469

[BUG]: Variable names are case-sensitive in komorebic start #469

Describe the bug

Variable names are case-insensitive in both pwsh and cmd.

Variable names are case-sensitive in komorebic start