My Windows Terminal Settings profile with elevated prompt for PowerShell via gsudo.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // latest version is now here: | |
| // https://github.com/thushan/dotfiles/blob/main/windows/windows-terminal/settings.json | |
Great idea @JohnLGalt, I've moved my terminal settings to git under a proper dotfiless now.
Using gsudo makes life a lot easier until elevation is supported natively on Windows Terminal.
Agreed. Nice move to the git, that should help some folks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Nice. I ran across this blog post to accomplish pretty much the same thing.
I created 2 sets on modifications for both PowerShell and CMD in Terminal Preview, one with gsudo and one with gsudo -s (giving highest privileges, as System). Just in case I ever need such abominably high privileges on the machine.