Tuckr icon indicating copy to clipboard operation
Tuckr copied to clipboard

Data loss possible at nearly every step

Open Walter-o opened this issue 1 year ago • 4 comments

For linux tuckr so far i found 0 video explanations and barely any mentions online. So i figured i read the official github page for this project and then wing it a bit with --help and man page if needed.

However, this went wrong in insane ways.

I had times when it gave a cryptic rust error because it tried to resolve a broken symlink it made itself.

And now it zeroed out my nvim config from just running 2 benign commands.

image image

From what i can gather tuckr does not expand nicely and instead overwrites files with emptiness, and i did the command this way to save time travelling through directories too.

I have to now pick up the scraps of the nvim explosion and am going to try out GNU stow for the first time, hopefully this isn't as brittle as tuckr is at the moment.

Also if i made any insane mistake in using tuckr i would really like to know. I am using the "-a" flag when deploying to evacuate conflicting files, this should never end in zeroed out files.

Walter-o avatar Nov 26 '24 13:11 Walter-o