Wsl

Introduction

In the last post we saw how to create a drop-in replacement for notify-send. This allowed us to take a script that used notify-send and run it without modification. In this post, we’ll take a look at how we can update that script to take better advantage of Windows notifications.

At the end of the last post, the notification was fairly generic as shown below:

[Read More]

See how to create a replacement notify-send utility for WSL, and how to integrate that with the GitHub cli to get Windows notifications when your GitHub workflows finish

Make magic happen! Learn how to automatically forward content copied to the clipboard in a VS Code dev container to your Windows clipboard

Wish that Windows Terminal started in your user HOME directory for WSL profiles?

Find out how to store your SSH keys in Windows and access them from your WSL distros

Getting errors because your WSL 2 clock is out of sync? FOllow these steps to automatically sync it

UPDATE (2020-04-08): With the 1.44 release of Visual Studio Code (and the corresponding Remote Containers release), the Insiders release is no longer needed as the . I have updated the post to reflect this (update made in vscode dev container on stable release 😁).

Introduction

In my previous post I gave some thoughts on using Visual Studio Code dev containers. Until very recently your source code needed to be cloned in Windows in order to be able to build and run dev containers with Visual Studio Code. While this has still been a great experience overall, I have hit a few edge cases where being able to have my source code in Linux (under WSL) and then create a dev container from there would have been a big help.

[Read More]