The result of these shortcomings is that Linux commands feel like second-class citizens to Windows and are harder to use than they should be.
Windows paths passed as arguments don’t often resolve due to not being translated to the appropriate mount point within WSL.Windows paths passed as arguments don’t often resolve due to backslashes being interpreted as escape characters rather than directory separators.Prefixing commands with wsl is tedious and unnatural.While a significant improvement, the experience is lacking in several ways: The Windows Subsystem for Linux (WSL) was a huge step forward here, enabling developers to call through to Linux commands from Windows by proxying them through wsl.exe (e.g. Whether longing for a powerful pager like less or wanting to use familiar commands like grep or sed, Windows developers desire easy access to these commands as part of their core workflow. A common question Windows developers have is “why doesn’t Windows have yet?”.
0 kommentar(er)
