In bash, the profile is a bash script located at ~/.bashrc.īy default it contains a lot of stuff already, so I like to add my changes to the bottom of the Profile script without having to create a new terminal instance. I also add a reloadĪlias which simply reloads the shell using the profile script. This is great because now I don't need to remember where my profile isĮver again, I can just run profile and can start editing it right away. Next, I add the profile alias which opens the profile script in my editor (the editor alias isĪlready coming in handy!). It also means I can create moreĪliases that open the editor without having to change all of them if I change my editor. The reason I create an alias for my editor command is so that I can change the editor at any timeĪnd not have to change my muscle memory to use the new command. That said, if you wanted to use VSCode, you could replace nano with code. I prefer to use a terminal editor instead of a GUI editor because it reducesĬontext switching when working in the terminal, and is much faster to load the file to make a quickĮdit. First of all, I am creating a couple aliases ( editor and edit) for Set-Alias -Name reload -Value reload_alias Set-Alias -Name profile -Value profile_alias Now to create my PowerShell 7 profile, I added the following object to the profiles array: ![]() Header bar and then Settings or Ctrl+ ,). To do this, simplyĪdd the "hidden": true property to the profiles in the WT settings file (click the dropdown in the Using PowerShell 7 instead of PowerShell, so I disabled all but the WSL shell. I'm not interested in using cmd or Azure Cloud Shell, and I'm going to be By default, WT creates a profile for WSL, PowerShell, cmd,Īnd Azure Cloud Shell. ![]() Going, I also installed the latest PowerShell Nice experience as well, so I wanted to make sure my PowerShell terminal was great too. To get my beautiful terminal going, I installed WindowsĪwesome new terminal experience for Windows from Microsoft.Īlthough I wanted WSL to be my primary dev environment, I still wanted working in Windows to be a The WSL filesystem seamlessly with VSCode. With this extension pack installed, you can edit files in Next I installed VSCode, and the Remote Development extension You can find instructions on installing WSL and/or I've had the most experience with in the past. I went with an Ubuntu distro because that's what To achieve this, I started by installing WSL 2. Opportunity to create a dev environment I would love. I recently got the chance to completely reset my Windows 10 machine, and took advantage of the ![]()
0 Comments
Leave a Reply. |