-
Notifications
You must be signed in to change notification settings - Fork 125
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
homesick symlinks use absoulte paths #50
Comments
Hey Michael! There really isn't a reason to use absolute paths, and moving to relative paths is a great idea. If it's something that you'd like to do you can submit a pull request, or I'll fix it within the next week or two. Cheers! |
👍 |
I'm new to the project, but this sounds like a fairly straightforward addition--is anyone working on this currently? |
I don't believe anyone started work on this. If you'd like to fix it, submit a pull request and I'll look at it. Otherwise, if people still want this fixed, I might be able to do so in the next few days myself. |
Sure, I'd like to do it. On Fri, May 30, 2014 at 2:02 AM, Nicolas McCurdy notifications@github.com
|
Hi there,
I like homesick!
However, I noticed that it uses absolute paths in the symlinks it creates. Is there a reason for this? I noticed this when I mounted the home directory in a rescue system under another path and all symlinks where broken. I think relative symlinks would work fine in this situation and see no other disadvantages. So my question is: why does homesick use absolute paths and could/should it be changed to relative paths?
Best Regards
MIchael
The text was updated successfully, but these errors were encountered: