Also, with a little imagination, if you interpret it as a fraction, you’d have the topdir as a common denominator like this:
topdir\subdir1, topdir\subdir2
You would also have to read it from right to left for it to make sense though:
subdir1/topdir, subdir2/topdir
But considering this approach, when writing the parts of the fraction below each other, the topdir is below the subdir (like a real tree growing from the ground lol). The “subdir is under topdir” analogy gets lost, which is my main problem with the backslash approach:
Backslash for subdirectories is unintuitive.
Change my mind!
The little subdirectory is leaning against the big directory :)
If you delete the little subdirectory, the big directory is unaffected (because it’s a heartless removed)
But if you delete the big directory, the little directory falls over and dies :(
I don’t really think either is unintuitive, I just made it up.
It’s clearly only meant as an escape character. Every other usecase should be forbidden. Oh, that little shrug emote thing is fine tho.
¯\_(ツ)_/¯
Better than RISC OS paths that use colons, and far better than VMS paths that look like this
DENVER::DKA100:[RD.PROJECTS.SAMBA]SETUP.COM;15The backslash is a descending line showing that the subdirectory is under the parent directory, as it would be in a tree view.
If that’s the case we should all be using ┖
That’s a good one 🕊️
So they come together like this:
Also, with a little imagination, if you interpret it as a fraction, you’d have the topdir as a common denominator like this:
You would also have to read it from right to left for it to make sense though:
But considering this approach, when writing the parts of the fraction below each other, the topdir is below the subdir (like a real tree growing from the ground lol). The “subdir is under topdir” analogy gets lost, which is my main problem with the backslash approach:
=>
subdir --- topdirit’s the main reason i prefer ANSI keyboards.