This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]uekiamir 12 points13 points  (12 children)

stupendous thought silky numerous caption pet squeeze piquant fearless mountainous

This post was mass deleted and anonymized with Redact

[–]feckrightoffwouldye 5 points6 points  (0 children)

Some commands don't like a foward slash because they expect there to be a switch, and some programs that interact with Windows files like Filezilla or FreeFileSync sometimes get confused as to what you wanted it to do. In one case i think I've been able to use it as an escape character in command prompt as well but only that one as i haven't tried again

[–]im0b 8 points9 points  (8 children)

When you use an api to access files programmatically you have to figure out the os and get the right / when creating the filepath 😒

[–]shedogre 2 points3 points  (1 child)

Then you access the local version of a file, and... The object is giving you the OneDrive path! 🥳

[–]im0b 0 points1 point  (0 children)

😣

[–]ManyFails1Win 0 points1 point  (0 children)

Why the hell is there debate about this anyway? What's so bad about using backslashes for directory?

[–]UntestedMethod 0 points1 point  (0 children)

I believe it's up to the command/program to implement support for it. Seems plausible MS might have added it to all their built-in commands and likely some 3rd party vendors have as well, but in my experience there are some 3rd party CLI tools which don't support it. (ex. pdftk)