Originally created by @johnnaaron on GitHub (Jun 26, 2022).
Komorebi might benefit from its own .config folder (.komorebi) to avoid polluting the home folder, since it ends up having 4 or 5 files sitting there on a standard scoop install. This would be similar to Yabai's behavior, which allows configuration files in:
$HOME/yabai/ $HOME/.yabai/ $HOME/.config/yabai/
or just as $HOME/.yabairc
Originally created by @johnnaaron on GitHub (Jun 26, 2022).
Komorebi might benefit from its own .config folder (.komorebi) to avoid polluting the home folder, since it ends up having 4 or 5 files sitting there on a standard scoop install. This would be similar to Yabai's behavior, which allows configuration files in:
`$HOME/yabai/`
`$HOME/.yabai/`
`$HOME/.config/yabai/`
or just as
`$HOME/.yabairc`
Please check out this part of the readme which talks about setting a custom folder for configuration and related files using an environment variable.
I and many others use this to ensure that the $HOME dir stays free of both config and runtime files.
@LGUG2Z commented on GitHub (Jun 26, 2022):
Please check out [this part of the readme](https://github.com/LGUG2Z/komorebi#setting-a-custom-komorebi_config_home-directory) which talks about setting a custom folder for configuration and related files using an environment variable.
I and many others use this to ensure that the `$HOME` dir stays free of both config and runtime files.
The default behaviour will eventually be changed with the next "breaking change" release, but for now there are already hundreds of people using komorebi with the default $HOME dir and unfortunately this isn't the kind of change that can be pushed on them with a minor release.
Coincidentally my least favourite memories of using chunkwm and yabai were when I'd do a brew update and breaking changes meant spending hours getting everything working again. 😅
@LGUG2Z commented on GitHub (Jun 26, 2022):
The default behaviour will eventually be changed with the next "breaking change" release, but for now there are already hundreds of people using `komorebi` with the default `$HOME` dir and unfortunately this isn't the kind of change that can be pushed on them with a minor release.
Coincidentally my least favourite memories of using `chunkwm` and `yabai` were when I'd do a `brew update` and breaking changes meant spending hours getting everything working again. 😅
I think you could just add the folllowing directories in this order:
~.config/komorebi
~/.komorebi
~
This way, users can have their config in ~/.config/komorebi (or move it there), and komorebi would parse it
@es183923 commented on GitHub (Jul 15, 2022):
I think you could just add the folllowing directories in this order:
```
~.config/komorebi
~/.komorebi
~
```
This way, users can have their config in ~/.config/komorebi (or move it there), and komorebi would parse it
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 @johnnaaron on GitHub (Jun 26, 2022).
Komorebi might benefit from its own .config folder (.komorebi) to avoid polluting the home folder, since it ends up having 4 or 5 files sitting there on a standard scoop install. This would be similar to Yabai's behavior, which allows configuration files in:
$HOME/yabai/$HOME/.yabai/$HOME/.config/yabai/or just as
$HOME/.yabairc@LGUG2Z commented on GitHub (Jun 26, 2022):
Please check out this part of the readme which talks about setting a custom folder for configuration and related files using an environment variable.
I and many others use this to ensure that the
$HOMEdir stays free of both config and runtime files.@LGUG2Z commented on GitHub (Jun 26, 2022):
The default behaviour will eventually be changed with the next "breaking change" release, but for now there are already hundreds of people using
komorebiwith the default$HOMEdir and unfortunately this isn't the kind of change that can be pushed on them with a minor release.Coincidentally my least favourite memories of using
chunkwmandyabaiwere when I'd do abrew updateand breaking changes meant spending hours getting everything working again. 😅@johnnaaron commented on GitHub (Jul 15, 2022):
Ah, gotcha! Thank you, that makes sense.
@es183923 commented on GitHub (Jul 15, 2022):
I think you could just add the folllowing directories in this order:
This way, users can have their config in ~/.config/komorebi (or move it there), and komorebi would parse it