I didn't really do anything to it, just waited. Looks like correct syntax to me, so now I'm even more confused why this issue is happening.Įdit 2: The terminal hanging just stopped after a while and now I'm able to do work on the terminal again. The only part that I edited was adding a new alias called starship, so just this part:Īlias starship='vi ~/.config/starship.toml' Any way to fix this issue other than reinstalling the whole distro?Įdit 1: I'm able to see the bashrc file through Windows File Explorer. bashrc file but I'm unable to even view that file, let alone edit and execute it. It's almost certain I made some sort of mistake while editing the.
I am unable to ctrl+C or ctrl+z my out of anything and no prompts show up to allow for any command typing. bashrc file on VIM where all I did was add in an alias for some ls command. My terminal for any new Ubuntu instance is completely frozen with the message "Vim: Warning: Output is not to a terminal" If you wanted to get fancy and use PowerShell ISE to find the PowerShell Core guid, you could also use the following code, at the NAME: prompt, type powershell 6.Distro: Ubuntu-18.04 (running on Windows 10 WSL2) You will use the highlighted portion of the string.Ĭomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\DAFA0C9613B26094DB3D0861ADDA28CB The ”Production” item, in the form of C:\WINDOWS\Installer\ \PowerShellExe.ico is what you want. The location for the PowerShell Core terminal is noted below. You will use the highlighted portion of the string, leaving out the CN=.Ĭomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateRepository\Cache\PackageFamily\Data\7dĬomputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateRepository\Cache\PackageFamily\Data\7e The ”Publisher” item, in the form of CN= 45FBC5C5-8DE5-4E85-AE6A-377002DA7605 is what you want. The location for the WSL terminals is noted below. The registry locations will vary for the different terminals, so you are going to have to search for them using the FIND or FIND NEXT tools under the EDIT menu. The quickest way to find the guid(s) that you will want to add is to use the Registry Editor to search for them. The guid for each terminal will be different and must be used when adding the code block to the PROFILES.JSON file to allow the Windows Terminal to find the terminal and insert it as a tabbed terminal window.
0 kommentar(er)
