You're reading from Windows Subsystem for Linux 2 (WSL 2) Tips, Tricks, and Techniques Maximise productivity of your Windows 10 development machine with custom workflows and configurations

Product type Paperback

Published in Oct 2020

Publisher Packt

ISBN-13 9781800562448

Length 246 pages

Edition 1st Edition

Tools

Linux

Concepts

Shell Scripting

Author (1):

Stuart Leeks

View More author details

Table of Contents (16) Chapters

Preface

1. Section 1: Introduction, Installation, and Configuration

2. Chapter 1: Introduction to the Windows Subsystem for Linux FREE CHAPTER

3. Chapter 2: Installing and Configuring the Windows Subsystem for Linux

4. Chapter 3: Getting Started with Windows Terminal

5. Section 2:Windows and Linux – A Winning Combination

6. Chapter 4: Windows to Linux Interoperability

7. Chapter 5: Linux to Windows Interoperability

8. Chapter 6: Getting More from Windows Terminal

9. Chapter 7: Working with Containers in WSL

10. Chapter 8: Working with WSL Distros

11. Section 3: Developing with the Windows Subsystem for Linux

12. Chapter 9: Visual Studio Code and WSL

13. Chapter 10: Visual Studio Code and Containers

14. Chapter 11: Productivity Tips with Command-Line Tools

15. Other Books You May Enjoy

Leave a review - let other readers know what you think

Running Linux applications from Windows

In Chapter 2, Installing and Configuring the Windows Subsystem for Linux, you were briefly introduced to the wsl command and you saw how it could be used both for controlling running distros and for executing applications inside distros. In this section, we're going to dig deeper into running applications in distros with the wsl command.

As we saw in the last section, being able to access files across Windows and Linux is useful and being able to invoke applications builds on this further. WSL doesn't stop with just being able to run applications in a distro from Windows, it also lets you pipe output between applications. When building up scripts in either Windows or Linux, piping output between applications is a very common way to build up script functionality. Being able to pipe output between Windows and Linux commands allows you to build scripts that run across both Windows and Linux, which really helps build that sense of uniting...