What happens when you have two or more packages that use . config/ ? Will it still try to symlink that directory? It would be much better to make sure the directory is created and only symlink files.
Great question! I can only answer from experience. There may be a more sophisticated answer.
Before setting up my .dotfiles in the way I described in this post, I had a .config directory with a few subdirectories for packages I use routinely. I don't need to version control these packages, so they aren't stowed in my .dotfiles directory.
stow realizes this, and instead of symlinking the entire .config directory, it goes one level deeper and symlinks the stowed directory. This preserves the rest of the folders in .config from being symlinked.
So what this looks like using a stowed nvim directory:
What happens when you have two or more packages that use . config/ ? Will it still try to symlink that directory? It would be much better to make sure the directory is created and only symlink files.
Great question! I can only answer from experience. There may be a more sophisticated answer.
Before setting up my
.dotfiles
in the way I described in this post, I had a.config
directory with a few subdirectories for packages I use routinely. I don't need to version control these packages, so they aren't stowed in my.dotfiles
directory.stow
realizes this, and instead of symlinking the entire.config
directory, it goes one level deeper and symlinks the stowed directory. This preserves the rest of the folders in.config
from being symlinked.So what this looks like using a stowed
nvim
directory:Hope this answers your question!