Clean Setup
One thing I noticed is that every package contains its own .config directory:
nvim/.config/nvim
ghostty/.config/ghostty
tmux/.config/tmux
...
Personally, repeating .config in every single package feels a bit tedious and adds a lot of boilerplate to the repo structure.
GNU Stow has a --dotfiles flag that lets you avoid this entirely by using a single dot-config directory. Stow automatically translates dot- back to . when creating symlinks.
For example:
dot-config/
├── nvim
├── ghostty
├── tmux
├── waybar
└── ...
gets linked to:
~/.config/nvim
~/.config/ghostty
~/.config/tmux
~/.config/waybar
I've been using this approach in my own dotfiles repo, and it keeps things much cleaner once the config collection starts growing:
https://github.com/kushvinth/dotfiles
Might be worth checking out if you ever feel like reducing some of the .config repetition throughout the repository.
Clean Setup
One thing I noticed is that every package contains its own
.configdirectory:Personally, repeating
.configin every single package feels a bit tedious and adds a lot of boilerplate to the repo structure.GNU Stow has a
--dotfilesflag that lets you avoid this entirely by using a singledot-configdirectory. Stow automatically translatesdot-back to.when creating symlinks.For example:
gets linked to:
I've been using this approach in my own dotfiles repo, and it keeps things much cleaner once the config collection starts growing:
https://github.com/kushvinth/dotfiles
Might be worth checking out if you ever feel like reducing some of the
.configrepetition throughout the repository.