Closed lictw closed 8 months ago
Hello, thanks! Happy you like dotdrop and it's useful to you :+1:
Since we have all information in the config file, I think that's doable. It would be a new command (something like uninstall
) and remove everything that was installed by dotdrop.
Regarding the ability to remove non-managed files in a known dotfile, I would however suggest adding an option to install
so that you can force, as part of installing a dotfile, remove any other files present. What do you think?
Yep, I thinks it's nice!
Ok cool, I'll work on this and keep you posted
@lictw I have something for you:
uninstall
to uninstall any file installed by dotdrop--remove-existing
that will, when using install
, remove any files not managed by dotdrop (only for directories with link: nolink
)You can test a branch using the doc here.
I would be thankful if you could test the above two with your setup (since it seems you'd make good use of it). Thanks a lot for your help!
@lictw the two branches have been merged into master. Both features are now available:
uninstall
command to uninstall files installed by dotdropinstall
command line switch --remove-existing
to remove any files not managed by dotdrop
Hello!
First of all - thanks for the great tool! It's really the most feature-rich dotfiles manager for multi-ricing/overlaying: keeping bases/common things, patching them and extending in the rices etc., patching from other files, other repositories, any case can be implemented and I really like it!
But
dotdrop
misses some things for clean up dotfiles after another rice or experiment:profile
or just a ability to delete files of somedotfile
(without changing things in dotdrop, just clean up real things), may be with some filtering or advanced logic.dotfile
if it's directory, now we only see warnings about this files and must delete them manually.