-
Notifications
You must be signed in to change notification settings - Fork 147
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
I lost my castle #106
Comments
Yes, and this might sound a bit harsh... read the manual.
homeshick is a tool coded in the spirit of how most other unix tools work. |
Looking forward to that |
What about a hard link option? Would that interfere with homesick's ability to recognise files that are not linked? In general, I think I'd prefer hard links because: a) some and backup tools tools don't follow symlinks, they back them up. |
Maybe I'm missing some obvious issue here but let me just tell my story:
I created a new castle:
homeshick generate vim
I tracked my vim folder
homeshick track vim .vim/
I made a mess, wanted to start over like before homeshick, my first instint was:
rm -rfv ~/.homesick/repos/vim
Great... now all I got are null symlinks in ~/.vim folder.
Totally my bad I know, but maybe using hardlinks instead of symlinks, or a new "untrack" command could highlight the fact that the process of "untracking" unpushed castles is dangerous and should be done with extreme care.
Any thoughts on this?
The text was updated successfully, but these errors were encountered: