You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would request an update to the tutorial to show "As of Insider build 17093, you can use use bashslashes on your Windows paths in WSL and forward slashes in your Linux paths from Windows. " With that, an updated code to reflect this change for each section that says 17093+ as a header with the updated code underneath.
The text was updated successfully, but these errors were encountered:
I don't exactly have time myself to make said changes but thought I could at least bring it up so someone in the community could be aware of it. I'm just thinking of the perspective of wanting to be able to copy and paste the code without having to modify it as much. You no longer need to account for which slash to use for Windows/WSL path translations, which was one of the biggest hurdles in interoperability.
I would request an update to the tutorial to show "As of Insider build 17093, you can use use bashslashes on your Windows paths in WSL and forward slashes in your Linux paths from Windows. " With that, an updated code to reflect this change for each section that says 17093+ as a header with the updated code underneath.
The text was updated successfully, but these errors were encountered: