Linuxmemed@lemmy.worldM to linuxmemes@lemmy.world · 1 year agoBattle of the slasheslemmy.worldimagemessage-square15fedilinkarrow-up1137
arrow-up1137imageBattle of the slasheslemmy.worldLinuxmemed@lemmy.worldM to linuxmemes@lemmy.world · 1 year agomessage-square15fedilink
minus-squarewoelkchen@lemmy.worldlinkfedilinkarrow-up9·1 year agoNo idea when this happened but you can also use forward slashes in Windows. So typing c:/users into the Explorer address bar works.
minus-squareCupDock@lemmy.worldlinkfedilinkarrow-up5·1 year agoYou can even mix and match! C:\tmp/file.txt is valid. Very helpful for cross-os compatibility.
minus-squarePunkid @lemmy.worldlinkfedilinkarrow-up2·1 year agoDoes only windows do this or do Linux and mac work with both slashes too ? I thought linux was pretty strict with this
minus-squareMalix@lemmy.worldlinkfedilinkarrow-up3·1 year agoonly windows, afaik. On linux \ is the escape symbol
minus-squareinverimus@lemm.eelinkfedilinkarrow-up1·1 year agoWindows is the odd one out, everywhere else uses forward slash.
minus-squarewoelkchen@lemmy.worldlinkfedilinkarrow-up4·1 year agoOn classic MacOS the path separater was a “:”.
minus-squaremanbart@kbin.sociallinkfedilinkarrow-up2·1 year agoBeat me to it. It works in CMD/PowerShell too. It’s easier to just train your muscle memory to always use / regardless of platform
minus-squareZILtoid1991@kbin.sociallinkfedilinkarrow-up1·1 year agoI 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).
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 “:”.
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
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).