Originally created by @nicolasshu on GitHub (Nov 27, 2024).
Summary
I've been observing a weird behavior when I use the quickstart scripts for Komorebi. I'm not sure what is going wrong. Have you seen this behavior before?
.shell powershell
# Reload whkd configuration
# alt + o : taskkill /f /im whkd.exe && start /b whkd # if shell is cmd
alt + o : taskkill /f /im whkd.exe; Start-Process whkd -WindowStyle hidden # if shell is pwsh / powershell
alt + shift + o : komorebic reload-configuration
# App shortcuts - these require shell to be pwsh / powershell
# The apps will be focused if open, or launched if not open
# alt + f : if ($wshell.AppActivate('Firefox') -eq $False) { start firefox }
# alt + b : if ($wshell.AppActivate('Chrome') -eq $False) { start chrome }
alt + q : komorebic close
alt + m : komorebic minimize
# Focus windows
alt + h : komorebic focus left
alt + j : komorebic focus down
alt + k : komorebic focus up
alt + l : komorebic focus right
alt + shift + oem_4 : komorebic cycle-focus previous # oem_4 is [
alt + shift + oem_6 : komorebic cycle-focus next # oem_6 is ]
# Move windows
alt + shift + h : komorebic move left
alt + shift + j : komorebic move down
alt + shift + k : komorebic move up
alt + shift + l : komorebic move right
alt + shift + return : komorebic promote
# Stack windows
alt + left : komorebic stack left
alt + down : komorebic stack down
alt + up : komorebic stack up
alt + right : komorebic stack right
alt + oem_1 : komorebic unstack # oem_1 is ;
alt + oem_4 : komorebic cycle-stack previous # oem_4 is [
alt + oem_6 : komorebic cycle-stack next # oem_6 is ]
# Resize
alt + oem_plus : komorebic resize-axis horizontal increase
alt + oem_minus : komorebic resize-axis horizontal decrease
alt + shift + oem_plus : komorebic resize-axis vertical increase
alt + shift + oem_minus : komorebic resize-axis vertical decrease
# Manipulate windows
alt + t : komorebic toggle-float
alt + shift + f : komorebic toggle-monocle
# Window manager options
alt + shift + r : komorebic retile
alt + p : komorebic toggle-pause
# Layouts
alt + x : komorebic flip-layout horizontal
alt + y : komorebic flip-layout vertical
# Workspaces
alt + 1 : komorebic focus-workspace 0
alt + 2 : komorebic focus-workspace 1
alt + 3 : komorebic focus-workspace 2
alt + 4 : komorebic focus-workspace 3
alt + 5 : komorebic focus-workspace 4
alt + 6 : komorebic focus-workspace 5
alt + 7 : komorebic focus-workspace 6
alt + 8 : komorebic focus-workspace 7
# Move windows across workspaces
alt + shift + 1 : komorebic move-to-workspace 0
alt + shift + 2 : komorebic move-to-workspace 1
alt + shift + 3 : komorebic move-to-workspace 2
alt + shift + 4 : komorebic move-to-workspace 3
alt + shift + 5 : komorebic move-to-workspace 4
alt + shift + 6 : komorebic move-to-workspace 5
alt + shift + 7 : komorebic move-to-workspace 6
alt + shift + 8 : komorebic move-to-workspace 7
Output of komorebic check
Looking for configuration files in C:\Users\username.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\username.config\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 @nicolasshu on GitHub (Nov 27, 2024).
### Summary
I've been observing a weird behavior when I use the quickstart scripts for Komorebi. I'm not sure what is going wrong. Have you seen this behavior before?
```
komorebic quickstart
komorebic start --whkd --bar
```

### Version Information
0.1.30
### Komorebi Configuration
```json
komorebi.bar.json
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.30/schema.bar.json",
"monitor": {
"index": 0,
"work_area_offset": {
"left": 0,
"top": 40,
"right": 0,
"bottom": 40
}
},
"font_family": "JetBrains Mono",
"theme": {
"palette": "Base16",
"name": "Ashes",
"accent": "Base0D"
},
"left_widgets": [
{
"Komorebi": {
"workspaces": {
"enable": true,
"hide_empty_workspaces": false
},
"layout": {
"enable": true
},
"focused_window": {
"enable": true,
"show_icon": true
}
}
}
],
"right_widgets": [
{
"Media": {
"enable": true
}
},
{
"Storage": {
"enable": true
}
},
{
"Memory": {
"enable": true
}
},
{
"Network": {
"enable": true,
"show_total_data_transmitted": true,
"show_network_activity": true
}
},
{
"Date": {
"enable": true,
"format": "DayDateMonthYear"
}
},
{
"Time": {
"enable": true,
"format": "TwentyFourHour"
}
},
{
"Battery": {
"enable": true
}
}
]
}
```
komorebi.json
```json
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/v0.1.30/schema.json",
"app_specific_configuration_path": "$Env:KOMOREBI_CONFIG_HOME/applications.json",
"window_hiding_behaviour": "Cloak",
"cross_monitor_move_behaviour": "Insert",
"default_workspace_padding": 20,
"default_container_padding": 20,
"border": true,
"border_width": 8,
"border_offset": -1,
"theme": {
"palette": "Base16",
"name": "Ashes",
"unfocused_border": "Base03",
"bar_accent": "Base0D"
},
"stackbar": {
"height": 40,
"mode": "OnStack",
"tabs": {
"width": 300
}
},
"monitors": [
{
"workspaces": [
{
"name": "I",
"layout": "BSP"
},
{
"name": "II",
"layout": "VerticalStack"
},
{
"name": "III",
"layout": "HorizontalStack"
},
{
"name": "IV",
"layout": "UltrawideVerticalStack"
},
{
"name": "V",
"layout": "Rows"
},
{
"name": "VI",
"layout": "Grid"
},
{
"name": "VII",
"layout": "RightMainVerticalStack"
}
]
}
]
}
```
### Hotkey Configuration
```
.shell powershell
# Reload whkd configuration
# alt + o : taskkill /f /im whkd.exe && start /b whkd # if shell is cmd
alt + o : taskkill /f /im whkd.exe; Start-Process whkd -WindowStyle hidden # if shell is pwsh / powershell
alt + shift + o : komorebic reload-configuration
# App shortcuts - these require shell to be pwsh / powershell
# The apps will be focused if open, or launched if not open
# alt + f : if ($wshell.AppActivate('Firefox') -eq $False) { start firefox }
# alt + b : if ($wshell.AppActivate('Chrome') -eq $False) { start chrome }
alt + q : komorebic close
alt + m : komorebic minimize
# Focus windows
alt + h : komorebic focus left
alt + j : komorebic focus down
alt + k : komorebic focus up
alt + l : komorebic focus right
alt + shift + oem_4 : komorebic cycle-focus previous # oem_4 is [
alt + shift + oem_6 : komorebic cycle-focus next # oem_6 is ]
# Move windows
alt + shift + h : komorebic move left
alt + shift + j : komorebic move down
alt + shift + k : komorebic move up
alt + shift + l : komorebic move right
alt + shift + return : komorebic promote
# Stack windows
alt + left : komorebic stack left
alt + down : komorebic stack down
alt + up : komorebic stack up
alt + right : komorebic stack right
alt + oem_1 : komorebic unstack # oem_1 is ;
alt + oem_4 : komorebic cycle-stack previous # oem_4 is [
alt + oem_6 : komorebic cycle-stack next # oem_6 is ]
# Resize
alt + oem_plus : komorebic resize-axis horizontal increase
alt + oem_minus : komorebic resize-axis horizontal decrease
alt + shift + oem_plus : komorebic resize-axis vertical increase
alt + shift + oem_minus : komorebic resize-axis vertical decrease
# Manipulate windows
alt + t : komorebic toggle-float
alt + shift + f : komorebic toggle-monocle
# Window manager options
alt + shift + r : komorebic retile
alt + p : komorebic toggle-pause
# Layouts
alt + x : komorebic flip-layout horizontal
alt + y : komorebic flip-layout vertical
# Workspaces
alt + 1 : komorebic focus-workspace 0
alt + 2 : komorebic focus-workspace 1
alt + 3 : komorebic focus-workspace 2
alt + 4 : komorebic focus-workspace 3
alt + 5 : komorebic focus-workspace 4
alt + 6 : komorebic focus-workspace 5
alt + 7 : komorebic focus-workspace 6
alt + 8 : komorebic focus-workspace 7
# Move windows across workspaces
alt + shift + 1 : komorebic move-to-workspace 0
alt + shift + 2 : komorebic move-to-workspace 1
alt + shift + 3 : komorebic move-to-workspace 2
alt + shift + 4 : komorebic move-to-workspace 3
alt + shift + 5 : komorebic move-to-workspace 4
alt + shift + 6 : komorebic move-to-workspace 5
alt + shift + 7 : komorebic move-to-workspace 6
alt + shift + 8 : komorebic move-to-workspace 7
```
### Output of komorebic check
Looking for configuration files in C:\Users\username\.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\username\.config\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:51:22 +01:00
This title is a little misleading as you have clearly changed the configuration from the quickstart.
The correct output of komorebic check when you have set $Env:KOMOREBI_CONFIG_HOME properly:
❯ komorebic check
KOMOREBI_CONFIG_HOME detected: C:\Users\LGUG2Z\.config\komorebi
Looking for configuration files in C:\Users\LGUG2Z\.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\LGUG2Z\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
Because you have not set KOMOREBI_CONFIG_HOME properly as an env var on your system, you won't be able to look up the reference you have given to applications.json (which contains the ignore rule for komorebi-bar)
Closing as this is a user system configuration issue and not an issue with komorebi or the quickstart. Either use a full path to the applications.json file (this is given whenever you run komorebic fetch-asc to fetch the latest file), or set the environment variable at the system level.
@LGUG2Z commented on GitHub (Nov 27, 2024):
This title is a little misleading as you have clearly changed the configuration from the quickstart.
The correct output of `komorebic check` when you have set `$Env:KOMOREBI_CONFIG_HOME` properly:
```
❯ komorebic check
KOMOREBI_CONFIG_HOME detected: C:\Users\LGUG2Z\.config\komorebi
Looking for configuration files in C:\Users\LGUG2Z\.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\LGUG2Z\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
```
Because you have not set `KOMOREBI_CONFIG_HOME` properly as an env var on your system, you won't be able to look up the reference you have given to `applications.json` (which contains the ignore rule for `komorebi-bar`)
```json
"app_specific_configuration_path": "$Env:KOMOREBI_CONFIG_HOME/applications.json",
```
Closing as this is a user system configuration issue and not an issue with komorebi or the quickstart. Either use a full path to the `applications.json` file (this is given whenever you run `komorebic fetch-asc` to fetch the latest file), or set the environment variable at the system level.
My apologies. I do not know where I changed the quickstart configuration. I had gone to the location of $Env:KOMOREBI_CONFIG_HOME, and ran komorebi quickstart. It generated those files and I ran with them without editing them. Could you point me to where I changed them?
@nicolasshu commented on GitHub (Nov 27, 2024):
My apologies. I do not know where I changed the quickstart configuration. I had gone to the location of `$Env:KOMOREBI_CONFIG_HOME`, and ran `komorebi quickstart`. It generated those files and I ran with them without editing them. Could you point me to where I changed them?
Also, is this not what it was supposed to be?
```
PS C:\Users\username> echo $Env:KOMOREBI_CONFIG_HOME
C:\Users\username\.config\komorebi
```
I just deleted everything, created brand new files using komorebic quickstart and ran it again, and this is what I've found.
Is there a log that shows where this issue may be coming from?
@nicolasshu commented on GitHub (Nov 27, 2024):
I just deleted everything, created brand new files using `komorebic quickstart` and ran it again, and this is what I've found.

Is there a log that shows where this issue may be coming from?
I just did a sanity check to see if I did indeed change the files from the komorebic quickstart and I'm finding 0 differences. Where did you see the differences?
komorebic.bar.json
komorebic.json
@nicolasshu commented on GitHub (Nov 27, 2024):
I just did a sanity check to see if I did indeed change the files from the `komorebic quickstart` and I'm finding 0 differences. Where did you see the differences?
# komorebic.bar.json

# komorebic.json

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 @nicolasshu on GitHub (Nov 27, 2024).
Summary
I've been observing a weird behavior when I use the quickstart scripts for Komorebi. I'm not sure what is going wrong. Have you seen this behavior before?
Version Information
0.1.30
Komorebi Configuration
komorebi.json
Hotkey Configuration
Output of komorebic check
Looking for configuration files in C:\Users\username.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
Found C:\Users\username.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag
@LGUG2Z commented on GitHub (Nov 27, 2024):
This title is a little misleading as you have clearly changed the configuration from the quickstart.
The correct output of
komorebic checkwhen you have set$Env:KOMOREBI_CONFIG_HOMEproperly:Because you have not set
KOMOREBI_CONFIG_HOMEproperly as an env var on your system, you won't be able to look up the reference you have given toapplications.json(which contains the ignore rule forkomorebi-bar)Closing as this is a user system configuration issue and not an issue with komorebi or the quickstart. Either use a full path to the
applications.jsonfile (this is given whenever you runkomorebic fetch-ascto fetch the latest file), or set the environment variable at the system level.@nicolasshu commented on GitHub (Nov 27, 2024):
My apologies. I do not know where I changed the quickstart configuration. I had gone to the location of
$Env:KOMOREBI_CONFIG_HOME, and rankomorebi quickstart. It generated those files and I ran with them without editing them. Could you point me to where I changed them?Also, is this not what it was supposed to be?
@nicolasshu commented on GitHub (Nov 27, 2024):
I just deleted everything, created brand new files using
komorebic quickstartand ran it again, and this is what I've found.Is there a log that shows where this issue may be coming from?
@nicolasshu commented on GitHub (Nov 27, 2024):
I just did a sanity check to see if I did indeed change the files from the
komorebic quickstartand I'm finding 0 differences. Where did you see the differences?komorebic.bar.json
komorebic.json