• ssokolow ( ssokolow@lemmy.ml ) 
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 years ago

    It still returns relative paths if the input was relative

    False

    and it doesn’t resolve “…”

    I’ll assume you meant .., since ... is an ordinary filename. (Aside from the “who remembers …?” feature introduced in Windows 95’s COMMAND.COM where cd ... was shorthand for doing cd .. twice and you could omit the space after cd 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 “…”. ;)