Feature request: Move all komorebi files in $HOME to $HOME/.komorebi/ #53

New Issue

2026-01-05T14:47:56+01:00

adam commented

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

Originally created by @da-rth on GitHub (Oct 29, 2021).

Originally assigned to: @LGUG2Z on GitHub.

Currently, komorebi stores its user and auto-generated .sock, .json and .ahk files directly in the users home directory, however, this can get a bit cluttered - especially if these files aren't set to 'hidden' on the windows file system.

I would like to instead request that all komorebi files should be stored in and read from the directory $HOME/.komorebi e.g. C:/Users/denBot/.komorebi/komorebi.ahk

Some logic of the requested feature may include:

If the directory does not exist on start-up, komorebi could automatically create it and generate some default configuration files within the directory.
If anyone has updated from a previous version of komorebi and their config files are still in $HOME, komorebi can check for this and attempt to load the configuration files before attempting to create the .komorebi directory.
- If such files exist and are successfully loaded, no .komorebi directory needs to be created. If the user chooses, they can manually move their configuration files into a user-created .komorebi folder in $HOME.
- Alternatively, komorebi could prompt the user (via a popup alert) that their configuration files will be moved into $HOME/.komorebi

Originally created by @da-rth on GitHub (Oct 29, 2021). Originally assigned to: @LGUG2Z on GitHub. Currently, komorebi stores its user and auto-generated `.sock`, `.json` and `.ahk` files directly in the users home directory, however, this can get a bit cluttered - especially if these files aren't set to 'hidden' on the windows file system. I would like to instead request that all komorebi files should be stored in and read from the directory `$HOME/.komorebi` e.g. `C:/Users/denBot/.komorebi/komorebi.ahk` Some logic of the requested feature may include: - If the directory does not exist on start-up, komorebi could automatically create it and generate some default configuration files within the directory. - If anyone has updated from a previous version of komorebi and their config files are still in `$HOME`, komorebi can check for this and attempt to load the configuration files *before* attempting to create the `.komorebi` directory. - If such files exist and are successfully loaded, no `.komorebi` directory needs to be created. If the user chooses, they can manually move their configuration files into a user-created `.komorebi` folder in $HOME. - Alternatively, komorebi could prompt the user (via a popup alert) that their configuration files will be moved into `$HOME/.komorebi`

adam added the enhancement label 2026-01-05 14:47:56 +01:00

adam closed this issue

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

adam commented

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

@LGUG2Z commented on GitHub (Jan 28, 2022):

@denBot The directory for komorebi files can now be set explicitly by the user with $Env:KOMOREBI_CONFIG_HOME in the PowerShell rc file. 🎉

@LGUG2Z commented on GitHub (Jan 28, 2022): @denBot The directory for komorebi files can now be set explicitly by the user with `$Env:KOMOREBI_CONFIG_HOME` in the PowerShell rc file. 🎉

adam commented

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

@sitiom commented on GitHub (Jul 23, 2022):

@LGUG2Z I think that is not enough. By default, komorebi should not clutter the $HOME directory at all and use ~/.config/komorebi instead. KOMOREBI_CONFIG_HOME is provided as a second choice by the user.

@sitiom commented on GitHub (Jul 23, 2022): @LGUG2Z I think that is not enough. By default, komorebi should not clutter the $HOME directory at all and use `~/.config/komorebi` instead. `KOMOREBI_CONFIG_HOME` is provided as a second choice by the user.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#53