3 ms·
Most (everything?) on Windows actually works with forward slashes. However, much of the tooling will overwrite your version with a backslash wherever it can.
by 0cf8612b2e1e 5mo ago
Most (everything?) on Windows actually works with forward slashes. However, much of the tooling will overwrite your version with a backslash wherever it can.
- badc0ffee 5mo agoAt which layer? dir /w, for example, is never going to list the contents of \w.
- deleted 5mo ago[deleted]
- recursive 5mo agoUse powershell. Get-ChildItem /w
- jimjimjim 5mo agoToo many keystrokes, people won't use it.
- yyyk 5mo agogci /w than?
- recursive 5mo agols /w also works
- ranger_danger 5mo agohttps://learn.microsoft.com/en-us/powershell/module/microsoft.graph.identity.signins/remove-mgidentityauthenticationeventflowasongraphapretributecollectionexternaluserselfservicesignupattributeidentityuserflowattributebyref?view=graph-powershell-1.0 https://learn.microsoft.com/en-us/powershell/module/microsof...
- pjmlp 5mo agoAliases
- vips7L 5mo agoThe kernel and ntfs does not care about slash direction. Specific programs like dir might though and honestly if you're on windows just use powershell and avoid legacy cmd stuff.
- pjmlp 5mo agoAdditionally on programming languages use the apis for path management, instead of explicit looking for the \ or / characters.
- pjmlp 5mo agoAll the layers, except applications where devs still look for the wrong slash manually. OSes and modern programming languages have APIs for file navigation for a reason. On Windows this implies old applications from another era, good old command window, or people that don't know better.