Once complete you can start installing scripts like so, Install-Module -Name WifiTools Set-Theme Paradox Incorporating packagesīefore we start importing packages we need to get PowerShellGet setup, installation steps can be found here Installing PowerShellGet.

If you followed the prerequisites, your profile file will be mostly empty except perhaps a command to set the theme in oh-my-posh. It's from this file we can begin importing in scripts and adding custom functions.

You can find your profile directory location by typing the following in your console, $PROFILE Added oh-my-posh, for better git branch information.īefore your Powershell window starts, any code in your Powershell profile is executed first.Added Cascadia Ligature Font, for more compact and expressive text.This article assumes you have already read Hanselman's article and kitted your terminal out with the following (if not do so): This article is about my journey from reading this blog post 'How to make a pretty prompt in Windows Terminal with Powerline, Nerd Fonts, Cascadia Code, WSL, and oh-my-posh' by Scott Hanselman, to taking the experience one step further to evolve my terminal. There must be some things here we can use. Looking at Powershells Gallery, they have a total of 7,091 unique packages. This got me thinking.Ĭan I evolve my Powershell console experience in the same way I can with WSL? Running the same app in Powershell would start up in a fraction of the time. Having tried using this for react apps I found the experience really slow when building apps. Incorporating WSL (Windows Subsystem for Lynx) really helped bridge that gap as it opens up console experience that makes use of apt-get use the plethora of packages available. As a windows user the terminal experience has always been lacking, up till the new windows terminal was released.

Windows terminal download powershell