[FEATURE] Consider symlinking every file individually when specifying a directory. about toml-bombadil HOT 2 CLOSED

Hello @flyxi121

It might seems a good idea to get the directory tree and link only inner files but that would actually make your dotfiles harder to manage in my opinion.

Toml-bombadil config has a declarative approach and we try to avoid hidden behaviors. In other word if your config states
the nvim directory links to ~/.config/nvim, running bombadil link will do exactly this. Linking your dotfiles should not left your config in an inconsistent state.

It is easy to forget what config files are present in your ~/.config directories and spend hours figuring out what was left behind.

That said there are multiple ways you can solve this, here are how you could do it with vim-plug.

1. use a post install hook:

[settings]
# Runs vim-plug `PlugInstall` in headless mode and quit when finished
posthooks = [ "nvim --headless +PlugInstall +qa" ]

2. Place your plugin directory somewhere not managed by toml-bombadil

" init.vim
call plug#begin('~/.vim/plugged')

You might what to adapt this if you are using another plugin manager.

I would recommend using both methods to always get to the desired state running bombadil link.

from toml-bombadil.

Alright, I have to admit that never having hidden behavior is probably the best choice. Thanks for the tips to avoid the problem in the first place!

from toml-bombadil.