this post was submitted on 13 Jun 2024
42 points (97.7% liked)
Rust Programming
8004 readers
2 users here now
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
False
I'll assume you meant
..
, since...
is an ordinary filename. (Aside from the "who remembers ...?" feature introduced in Windows 95'sCOMMAND.COM
wherecd ...
was shorthand for doingcd ..
twice and you could omit the space aftercd
if your target was all dots.)The reason it doesn't do that is that, when symlinks get involved,
/foo/bar/..
does not necessarily resolve to/foo
and making that assumption could introduce a lurking security vulnerability in programs which use it.Hm it seems I misread the documentation there. I know why it doesn't resolve the ".." and that's fine, it just seemed very unnecessary in combination with my flawed understanding of the relative path handling.
Edit: and just to be snarky: I didn't type "..." I typed "..". ;)
*chuckle* I think Lemmy typed those for you, because I typed three periods and got a Unicode ellipsis, and both of those are also unicode ellipses.
Huh that might actually be an issue with your client, mine renders those as two dots
I'm using the web UI, so I'm assuming whatever broad-spectrum Markdown rendering library it uses has smart quote rendering turned on.