starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2026-01-05 14:49:46 +01:00 by adam · 5 comments
adam commented 2026-01-05 14:49:46 +01:00
Owner
Copy Link

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
Author
Owner
Copy Link

@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
Author
Owner
Copy Link

@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
Author
Owner
Copy Link

@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
Author
Owner
Copy Link

@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
Author
Owner
Copy Link

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

Sounds appropriate, thank you for your hard work!

@michaelruigrok commented on GitHub (Apr 11, 2024): Sounds appropriate, thank you for your hard work!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#328
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?