4 ms·
At which layer? dir /w, for example, is never going to list the contents of \w.
by badc0ffee 4mo ago
At which layer? dir /w, for example, is never going to list the contents of \w.
- deleted 4mo ago[deleted]
- recursive 4mo agoUse powershell. Get-ChildItem /w
- jimjimjim 4mo agoToo many keystrokes, people won't use it.
- yyyk 4mo agogci /w than?
- recursive 4mo agols /w also works
- ranger_danger 4mo 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 4mo agoAliases
- vips7L 4mo 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 4mo agoAdditionally on programming languages use the apis for path management, instead of explicit looking for the \ or / characters.
- pjmlp 4mo 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.