@simontatham That btw will blow up in interesting ways if one of them already exists and is a symlink 8)
Top-level
@simontatham That btw will blow up in interesting ways if one of them already exists and is a symlink 8) 2 comments
@rotopenguin @etchedpixels yes, I've always hated the bash feature of 'helpfully' trying to interpret .. more like the naïve expectation, but only managing to do it for bash builtins, so that 'cd ../foo' and 'ls ../foo' are talking about different directories. I do 'set -P' in my .bashrc, so that I get a consistent experience of .. going to the physical parent dir linked from my cwd's inode. I'd rather that than have to keep remembering which is which. |
@etchedpixels @simontatham I can never tell when .. means to pop the last directory in the path I used to get here, or it means to follow the literal ".." directory entry of wherever-the-hell-I-am-now.