Ha, ha. Windows admins don’t use the command line, do they?
Why wouldn’t they? PowerShell’s been a thing for 19 years.
This is so sad, alexa
rm -rf /*:(Dont remove the French :(
echo "Ceci n'est pas une pipe" | cowsayFYI Magritte was Belgian, not French.
| lolcat
Backslash for subdirectories is unintuitive.
Change my mind!
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:
topdir | subdirAlso, 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\subdir2You would also have to read it from right to left for it to make sense though:
subdir1/topdir, subdir2/topdirBut 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:
topdir\subdir=>
subdir --- topdir
it’s the main reason i prefer ANSI keyboards.
Windows admins when they have to use windows :-/\
*he is shouting.
Nobody quite hates Windows as much as the admins that have to deal with its quirks all the frigging time.
I mostly have had to use windows servers over my career. I get so fucking happy when I can use a Linux server.
Interesting read, thanks.
This will always piss me off to no end.
I think in powershell you can just use / for everything anyways.
Sometimes my brain just trips on itself and I superposition both as being correct for whichever terminal I’m working with (throw MacOS in there too), I stare at it blankly for a few seconds before remembering the ultimate CLI tool, ↑
:3
~ $ :3 No command :3 found, did you mean: Command i3 in package i3 from the x11-repo repository Command i3 in package i3-gaps from the x11-repo repository Command h3 in package libuber-h3 Command z3 in package z3 ~ $3:
:3c
:/
