{"id":778,"date":"2020-02-17T16:42:55","date_gmt":"2020-02-18T00:42:55","guid":{"rendered":"http:\/\/blog.nillsf.com\/?p=778"},"modified":"2020-07-14T17:25:09","modified_gmt":"2020-07-15T00:25:09","slug":"setting-up-wsl2-windows-terminal-and-oh-my-zsh","status":"publish","type":"post","link":"https:\/\/nillsf.com\/index.php\/2020\/02\/17\/setting-up-wsl2-windows-terminal-and-oh-my-zsh\/","title":{"rendered":"Setting up WSL2, Windows Terminal and oh-my-zsh"},"content":{"rendered":"\n

I recently re-imaged my laptop to a clean Windows 10. I haven’t yet taken the time to re-setup my Linux setup on top of Windows 10. In this post, I’ll walk you through how to setup WSL2, in combination with the (new) Windows Terminal and oh-my-zsh.<\/p>\n\n\n\n

WSL stands for the Windows Subsystem for Linux. WSL has brought a Linux kernel to Windows 10. WSL2 is the new version of WSL, available to only Windows insiders for now . It drastically improves performance, as it no longer translates kernel calls, but rather runs in a micro-VM on top of Hyper-V.<\/p>\n\n\n\n

The new Windows terminal is an improved terminal announced by Microsoft at Build 2019. Is allow multi-tabbed terminals, can connect to multiple run-times (PowerDhell, WSL, cloud shell) and is heavily customizable.<\/p>\n\n\n\n

Oh-my-zsh is a terminal tool that allows you to pretty up your Linux terminal. It can do pretty color printing, show git status and much more.<\/p>\n\n\n\n

Let’s get started and set this up.<\/p>\n\n\n\n

WSL2<\/h2>\n\n\n\n

In order to run WSL2 you need to be a Windows Insider and be on at least on version 18917 or higher. To check your Windows version, hit Windows Key + x <\/code> and click on system<\/code>. There you’ll see your Windows version:<\/p>\n\n\n\n

\"\"
My OS build is high enough to run WSL2<\/figcaption><\/figure>\n\n\n\n

To run WSL2, you’ll need to enable to additional Windows features: Hyper-V and WSL. To get both up and running, look for “Turn Windows features on or off” in the start menu:<\/p>\n\n\n\n

\"\"
You’ll need to turn on Hyper-V and WSL.<\/figcaption><\/figure>\n\n\n\n

In that window, make sure to select both HyperV and Windows Subsystem for Linux.<\/p>\n\n\n\n

\"\"
Enable Hyper-V and WSL<\/figcaption><\/figure>\n\n\n\n

If you have those selected, click OK and go through with the reboot of your system.<\/p>\n\n\n\n

After the reboot, we’ll go ahead and install our favorite Linux distro. Open the Microsoft store, and look for your distro (Ubuntu in my case).<\/p>\n\n\n\n

\"\"
I’ll be installing Ubuntu 18.04<\/figcaption><\/figure>\n\n\n\n

Hit the install button, and give it a couple of minutes to download and install. Once installed, hit the ‘Launch’ button, to start your Ubuntu. This will trigger an installation, which will take another couple of minutes. <\/p>\n\n\n\n

\"\"
Once the app is installed, hit the Launch button to trigger the actual Linux installation.<\/figcaption><\/figure>\n\n\n\n

Once the installation is complete, you’ll get prompted for a username and password. Fill that in, and your Linux installation will be complete.<\/p>\n\n\n\n

Now, we’ll go ahead and switch this installation from WSL1 to WSL2. To do this, open a (regular) command line, and execute the following commands:<\/p>\n\n\n\n

wsl -l -v\nwsl --set-version Ubuntu-18.04 2<\/code><\/pre>\n\n\n\n
This will convert our WSL1 to a WSL2. We can verify the conversion was successful, with the following command:<\/p>\n\n\n\n
wsl -l -v<\/code><\/pre>\n\n\n\n
With that done, we have our WSL2 setup. Next up, setting up the Windows Terminal.<\/p>\n\n\n\n
Windows Terminal<\/h2>\n\n\n\n
Installing the Windows Terminal isn’t too difficult. Simply head over to the Microsoft store, look for Windows Terminal, and hit the install button.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Give this a couple minutes to install, and then you can launch the terminal. The default shell in the terminal is PowerShell.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
I want to change this to WSL2. To edit this, go to the Terminal settings file. <\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
This opens up the settings file. Copy the GUID from the Ubuntu config and paste that in the defaultProfile:<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Save this file, and then reload the terminal. This should now open a WSL terminal.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Oh my zsh setup<\/h2>\n\n\n\n
Finally, we’ll go ahead and setup oh my zsh. Let’s start with setting up the prerequisites:<\/p>\n\n\n\n
sudo apt update\nsudo apt install git zsh -y<\/code><\/pre>\n\n\n\n
With the prerequisites installed, we can go ahead and install Oh my zsh:<\/p>\n\n\n\n
sh -c \"$(curl -fsSL https:\/\/raw.githubusercontent.com\/ohmyzsh\/ohmyzsh\/master\/tools\/install.sh)\"<\/code><\/pre>\n\n\n\n
This will ask you if you want the switch your shell to zsh. Hit yes.<\/p>\n\n\n\n
Next up, we’ll want to pick a fancier theme (if you feel like it). The agnoster <\/code>theme is a popular one. To change the theme, edit the ~\/.zshrc<\/code> file and input the agnoster theme there.<\/p>\n\n\n\n
\"\"<\/figure>\n\n\n\n
Reload your Terminal now. You will see that the visual isn’t perfect just yet. First thing we’ll do is edit the color setup of your Terminal. To edit this, open up the settings file for the Terminal again. We’ll make two changes:<\/p>\n\n\n\n
  1. Add a custom scheme.<\/li>
  2. Link that scheme to our WSL terminal.<\/li><\/ol>\n\n\n\n
    To add the scheme, paste the following code into schemes:<\/p>\n\n\n\n
        \"schemes\": [\n        {\n            \"background\" : \"#002B36\",\n            \"black\" : \"#002B36\",\n            \"blue\" : \"#268BD2\",\n            \"brightBlack\" : \"#657B83\",\n            \"brightBlue\" : \"#839496\",\n            \"brightCyan\" : \"#D33682\",\n            \"brightGreen\" : \"#B58900\",\n            \"brightPurple\" : \"#EEE8D5\",\n            \"brightRed\" : \"#CB4B16\",\n            \"brightWhite\" : \"#FDF6E3\",\n            \"brightYellow\" : \"#586E75\",\n            \"cyan\" : \"#2AA198\",\n            \"foreground\" : \"#93A1A1\",\n            \"green\" : \"#859900\",\n            \"name\" : \"wsl\",\n            \"purple\" : \"#6C71C4\",\n            \"red\" : \"#DC322F\",\n            \"white\" : \"#93A1A1\",\n            \"yellow\" : \"#B58900\"\n        }\n    ],<\/code><\/pre>\n\n\n\n
    Then, look for the configuration of you WSL, and add a line that says: \"colorScheme\" : \"wsl\" <\/code>:<\/p>\n\n\n\n
            {\n            \"guid\": \"{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}\",\n            \"hidden\": false,\n            \"name\": \"Ubuntu-18.04\",\n            \"source\": \"Windows.Terminal.Wsl\",\n            \"colorScheme\" : \"wsl\"\n        }<\/code><\/pre>\n\n\n\n
    Save this file and look back at your Terminal. The color scheme should have changed now. Final step remaining is installing a Powerline font that allows special characters. To do this, open up a PowerShell window as adminstrator. Navigate to a folder where you can execute git clone<\/code>.<\/p>\n\n\n\n
    mkdir c:\/fonts\ncd c:\/fonts\ngit clone https:\/\/github.com\/powerline\/fonts.git\ncd fonts\n.\\install.ps1<\/code><\/pre>\n\n\n\n
    That final step, will install the fonts onto your Windows installation. To have the Terminal use the newly installed fonts, we’ll need to add another line to our Terminal configuration:<\/p>\n\n\n\n
            {\n            \"guid\": \"{c6eaf9f4-32a7-5fdc-b5cf-066e8a4b1e40}\",\n            \"hidden\": false,\n            \"name\": \"Ubuntu-18.04\",\n            \"source\": \"Windows.Terminal.Wsl\",\n            \"colorScheme\" : \"wsl\",\n            \"fontFace\" : \"DejaVu Sans Mono for Powerline\"\n        }<\/code><\/pre>\n\n\n\n
    This is starting to look a bit better. There is one final change that I like to make personally, that changes my username background color and no longer shows the machine name. To do this, open up the agnoster theme file<\/p>\n\n\n\n
    vi ~\/.oh-my-zsh\/themes\/agnoster.zsh-theme<\/code><\/pre>\n\n\n\n
    and change line 92:<\/p>\n\n\n\n
    prompt_segment green black \"%(!.%{%F{yellow}%}.)%n\"<\/code><\/pre>\n\n\n\n
    Which should make it look like:<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Save the file, and open up a new terminal. This should look like this: <\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    One final thing I want to change here is to open the shell on the Linux home directory, not the Windows home directory. To do this, add this line to the ~\/.zshrc<\/code> file.<\/p>\n\n\n\n
    cd ~<\/code><\/p>\n\n\n\n
    This should make your terminal look like:<\/p>\n\n\n\n
    \"\"<\/figure>\n\n\n\n
    Which is what I was looking for.<\/p>\n\n\n\n
    Summary<\/h2>\n\n\n\n
    In this post I explained how I setup my development environment using WSL2, Windows Terminal and oh my zsh. There are many ways to configure oh my zsh, and I only covered my personal flavor. <\/p>\n","protected":false},"excerpt":{"rendered":"
    I recently re-imaged my laptop to a clean Windows 10. I haven’t yet taken the time to re-setup my Linux setup on top of Windows 10. In this post, I’ll walk you through how to setup WSL2, in combination with the (new) Windows Terminal and oh-my-zsh. WSL stands for the Windows Subsystem for Linux. WSL […]<\/p>\n","protected":false},"author":1,"featured_media":793,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[5,41],"tags":[84,83,82],"class_list":["post-778","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-open-source","category-windows","tag-oh-my-zsh","tag-terminal","tag-wsl"],"jetpack_featured_media_url":"https:\/\/nillsfblog.blob.core.windows.net\/media\/2020\/02\/image-47.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/778","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/comments?post=778"}],"version-history":[{"count":5,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/778\/revisions"}],"predecessor-version":[{"id":1159,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/778\/revisions\/1159"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/media\/793"}],"wp:attachment":[{"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/media?parent=778"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/categories?post=778"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nillsf.com\/index.php\/wp-json\/wp\/v2\/tags?post=778"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}