-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing backup for existing files #76
Comments
* Now is different Sloth symlinks and user symlinks * dot symlinks update use new dotbot.sh library to apply symlinks * Fixed missing paths for gnutools in init-sloth.sh * Fixed dot package add loop when try to install docpars or cargo packages * Fixed no backup when installing Sloth (see CodelyTV#76) * Added libraries (dotbot.sh and symlinks.sh) to parse dotbot yaml files in symlinks context * Added python-yq recipe and dependency on dot core install * Added some options for dot symlinks apply see --help * Added function readarray in array.sh for those who are not running bash greather than version 4 * Changed mapfile for readarray in all scripts and libraries * Added files::backup_move_if_path_exists in files.sh * Added files::fzf that helps including Dotly/.Sloth core libraries and any other libraries in fzf --preview option
Hi @gtrabanco , Is this issue fixed? I've just lost the whole config from my I think we should add a warning/alert in the For whom with the same issue, here is a little help to restore the |
It is solved in .Sloth but the PR was open for months and after no feedback, approval or reject I decided to use only my fork to make some improvements where it is this one between some other. I also apply the new patchs and features to dotly there. It is quite complex because it is a good idea parse the dotbot files to know which files you have to do a backup. |
There is not a disclaimer when you install dotly on a configured computer, the installation overwrites my existing .zshrc and replace them with the default template, I lost my configuration.
The text was updated successfully, but these errors were encountered: