[FEAT]: Support ~/.config/komorebi as a config home alternative #328

New Issue

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

adam commented

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

Originally created by @michaelruigrok on GitHub (Apr 10, 2024).

A personal quibble: I track my home config in git for both Windows and Linux, and thus would prefer to prefix configuration files with a period so the files are hidden when using a Linux environment. Keeping these files under ~/.config/komorebi would be ideal.

Describe the solution you'd like
If $HOME/.config/komorebi exists, use this as the default komorebi home directory instead of $HOME directly.

While I don't think breaking compatibility would be a concern -- no one would have this directory unless they intended to use it -- a fallback solution would be alternatively available using .komorebi.json for example, instead of . If komorebi.json does not exist but .komorebi.json does, use the second file for configuration. This ideally would also apply to .ahk, .ps1 and any other configuration files.

Originally created by @michaelruigrok on GitHub (Apr 10, 2024). A personal quibble: I track my home config in git for both Windows and Linux, and thus would prefer to prefix configuration files with a period so the files are hidden when using a Linux environment. Keeping these files under `~/.config/komorebi` would be ideal. **Describe the solution you'd like** If `$HOME/.config/komorebi` exists, use this as the default komorebi home directory instead of $HOME directly. While I don't think breaking compatibility would be a concern -- no one would have this directory unless they intended to use it -- a fallback solution would be alternatively available using `.komorebi.json` for example, instead of . If `komorebi.json` does not exist but `.komorebi.json` does, use the second file for configuration. This ideally would also apply to `.ahk`, `.ps1` and any other configuration files.

adam added the enhancement label 2026-01-05 14:49:46 +01:00

adam closed this issue

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

adam commented

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

@azinsharaf commented on GitHub (Apr 10, 2024):

what if you use .config as a parent folder? that is how i do it.

@azinsharaf commented on GitHub (Apr 10, 2024): what if you use `.config` as a parent folder? that is how i do it.

adam commented

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

@michaelruigrok commented on GitHub (Apr 10, 2024):

what if you use .config as a parent folder? that is how i do it.

Yeah, that makes sense given the KOMOREBI_CONFIG envar. It would be nice to have ~/.config/komorebi as a default searched location. I'll update my ticket to reflect this, thanks :)

@michaelruigrok commented on GitHub (Apr 10, 2024): > what if you use `.config` as a parent folder? that is how i do it. Yeah, that makes sense given the KOMOREBI_CONFIG envar. It would be nice to have `~/.config/komorebi` as a default searched location. I'll update my ticket to reflect this, thanks :)

adam commented

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

@azinsharaf commented on GitHub (Apr 10, 2024):

maybe it can support XDG_CONFIG_HOME. not sure.

@azinsharaf commented on GitHub (Apr 10, 2024): maybe it can support `XDG_CONFIG_HOME`. not sure.

adam commented

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

@LGUG2Z commented on GitHub (Apr 10, 2024):

Going to close this as unplanned because there are already way too many lines of code in the project to look up predefined/default paths and there is a robust mechanism in place using the config home env vars to place config files anywhere the end user wants.

@LGUG2Z commented on GitHub (Apr 10, 2024): Going to close this as unplanned because there are already way too many lines of code in the project to look up predefined/default paths and there is a robust mechanism in place using the config home env vars to place config files anywhere the end user wants.

adam commented

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