-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No komorebi configuration found #625
Comments
whkd has its own config home environment variable. WHKD_CONFIG_HOME |
do you start komorebi and whkd like this? komorebic start -c "<komorebi.json file path goes here>" --whkd |
hi! no.
so, i need to set that up and point it to same as |
so,
$ komorebic start -c $KOMOREBI_CONFIG_HOME/komorebi.json --whkd
Start-Process 'komorebi.exe' -ArgumentList '--config="D:\UserFiles\komorebi_config_home\komorebi.json"' -WindowStyle hidden
Waiting for komorebi.exe to start...komorebi.exe did not start... Trying again
Start-Process 'komorebi.exe' -ArgumentList '--config="D:\UserFiles\komorebi_config_home\komorebi.json"' -WindowStyle hidden
$ komorebic start --whkd
Start-Process 'komorebi.exe' -WindowStyle hidden
Waiting for komorebi.exe to start...Started!
if (!(Get-Process whkd -ErrorAction SilentlyContinue))
{
Start-Process whkd -WindowStyle hidden
}
|
do you mind sharing your json file? |
hi! yeah, i have attached it below. Lines 200 to 201 in f9c69e5
but rerading the above example , i actually think u were right before regaring this:
in the sense that, edit2: even after setting up the
{
"$schema": "https://raw.githubusercontent.com/LGUG2Z/komorebi/master/schema.json",
// "app_specific_configuration_path": "$Env:USERPROFILE/applications.yaml",
"app_specific_configuration_path": "$Env:KOMOREBI_CONFIG_HOME/applications.yaml",
"window_hiding_behaviour": "Cloak",
"cross_monitor_move_behaviour": "Insert",
"alt_focus_hack": true,
"default_workspace_padding": 20,
"default_container_padding": 20,
"active_window_border": false,
"active_window_border_colours": {
"single": { "r": 66, "g": 165, "b": 245 },
"stack": { "r": 256, "g": 165, "b": 66 },
"monocle": { "r": 255, "g": 51, "b": 153 }
},
"monitors": [
{
"workspaces": [
{ "name": "I", "layout": "BSP" },
{ "name": "II", "layout": "VerticalStack" },
{ "name": "III", "layout": "HorizontalStack" },
{ "name": "IV", "layout": "UltrawideVerticalStack" },
{ "name": "V", "layout": "Rows" }
]
}
]
} it basically came as follows:
|
can you remove the commented out line in json file and try it again? If i am right json can't include lines commented out. not sure 100%. |
hi! i have got exams. so, wont be able to attach ay things for a month. however sharing my foundings from 2 days ago: it seems that evon on starting with I was doing that as i was used to expecting it to cycle back as it does in dwm-win32 port. i found that this was erronoeus when i started it as other than that, i tried changing the configs in and ofc i tried removing that commented out line, and it still showed no config found on |
'komorebic check' command shows me 'no config found' as well but it has picked it up correctly. could be a wrong message. |
hey @ LGUG2Z ! i am also a new user to komorebi coming here after failed try with dwm-win32 port.
i have been looking for almost 100 minutes, and still couldn't find how to enable hotkeys.
on looking further with
komorebic check
(thannks a lot for check subcommand 😃), i found that it says "no config found" which is confusing as i have done the equivalent of all the steps given in the readme.i have done:
komorebi
&whkd
PATH
, and added theKOMOREBI_CONFIG_HOME
env variableapplications.yaml komorebi.json whkdrc
files to that directory configured abovei am using msys2, not wsl or anything like that. so, the issue is not related to it.
i.e. equivalent of as mentioned at:
(click me)komorebi/README.md
Lines 237 to 240 in f9c69e5
komorebi/README.md
Lines 277 to 280 in f9c69e5
komorebi/README.md
Line 163 in f9c69e5
komorebi/README.md
Lines 191 to 201 in f9c69e5
komorebi/README.md
Lines 357 to 360 in f9c69e5
Versions and environment:
The text was updated successfully, but these errors were encountered: