cascalgary.blogg.se

I duplicated the existing PowerShell core one.

You can either duplicate an existing profile or create a blank one. Scroll down to the bottom and click “Add new profile”. In Windows Terminal, go to the arrow on the tab bar, then Settings. I’m doing this for PowerShell core, but you could do the same for PowerShell or CMD (or any other process). Now we have gsudo installed, it’s simple to set up a new admin terminal. This will elevate for the duration of the command, then de-elevate. Or you can install it from GitHub using this PowerShell get-process

The first thing you need to do is install gsudo. This makes it trivial to add an admin tab to Windows terminal. Gsudo is marketed as a sudo equivalent for windows, making it easier to run individual commands as admin, or the whole shell. On the surface, this is a thread stating that admin mode is not coming to Windows Terminal, but one comment suggests using a tool called gsudo. I revisited this today when I got annoyed again about needing to launch a new window and came across this GitHub issue. In Windows terminal, I needed to either drop out to a separate PowerShell window I used the “run as admin” right-click command on or configure a tab to execute a script that would launch another window as admin. While I’m not advocating for using admin mode in your day-to-day terminal-based work, you sometimes need to elevate for installing software, running commands that require admin rights, etc. However, the one thing I did miss from Cmder was the built-in support for having a terminal tab run in UAC Administrator mode. It had many features that Windows Terminal now has, and when that came out, I switched over. Before Windows Terminal existed, I used to use Cmder as my terminal of choice.