I've been using linux & macs for ~18yrs and I still have to look up whether the source or the destination comes first when running `ln -s`
-
Show this thread
-
Replying to @brianloveswords
Same. I think one of the issues is that one(both?) of the arguments doesn't accept relative paths (the target?) So if you `ln -s ./foo ~/bar/foo` from the target folder you get an infinite loop and it's just so confusing
3 replies 0 retweets 4 likes -
Replying to @ManishEarth @brianloveswords
Just pretend it’s a cp. Then you always get the argument order right.
1 reply 0 retweets 1 like -
Replying to @pcwalton @brianloveswords
That doesn't fix the relative path thing
3 replies 0 retweets 0 likes -
ln -s $(cd ../..; pwd)/src-file If symlinks didn't interpret relative paths literally, how would you create links to relative paths?
1 reply 0 retweets 0 likes -
I feel like that that is a less common use case, and is inconsistent with how basically every other coreutil woks. It could always have a flag that meant "link to hardcoded relative path". Normally you expect ./foo to mean "the locally available file foo"
1 reply 0 retweets 2 likes
Yeah, I’d prefer if ln did the right thing automatically and required a “--literal” flag or something for special cases.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.