I use forward slashes in all of my software’s paths, so I don’t have to fiddle around with it when I’m porting to Linux (in the future, I’ll likely go from “dev on Windows, port to Linux” to "dev on Linux, port to Windows).
This only works because MS gave in and added some path normalization. The actual path-component separator is still backslash. Sometimes it doesn’t work right, like in cmd if you try and do cd and use forward slashes then autocomplete won’t work even though the command itself works fine with forward slashes.
No idea when this happened but you can also use forward slashes in Windows. So typing
c:/usersinto the Explorer address bar works.You can even mix and match!
C:\tmp/file.txtis valid. Very helpful for cross-os compatibility.Does only windows do this or do Linux and mac work with both slashes too ?
I thought linux was pretty strict with this
only windows, afaik. On linux \ is the escape symbol
Windows is the odd one out, everywhere else uses forward slash.
On classic MacOS the path separater was a “:”.
I use forward slashes in all of my software’s paths, so I don’t have to fiddle around with it when I’m porting to Linux (in the future, I’ll likely go from “dev on Windows, port to Linux” to "dev on Linux, port to Windows).
Beat me to it. It works in CMD/PowerShell too. It’s easier to just train your muscle memory to always use / regardless of platform
This only works because MS gave in and added some path normalization. The actual path-component separator is still backslash. Sometimes it doesn’t work right, like in cmd if you try and do cd and use forward slashes then autocomplete won’t work even though the command itself works fine with forward slashes.
I didn’t even knew I had to use the backslash