Commander also supports adding different shells like git bash, WSL, or PowerShell but I used the cmd shell which has been enriched with a lot more useful commands. The latter is a great help when working with git I missed that in the other terminals. The git support not only integrates the git CLI, but it also shows the current branch in the prompt: Because of that, I was using cmder (), a great terminal with useful Linux commands and great support for git. PowerShell and oh-my-poshĪctually, working in the console doesn't work for me with the regular cmd.exe and I completely understand why developers on Windows still prefer using windows based tools for git and docker, and so on.

Follow the links to learn more about the tools. It is just a small portrait of what I'm going to use.

This post is not a tutorial on how to install and use the tools I'm going to mention here. I even used the console to install, update or uninstall tools using Chocolatey (). I'm navigating my folders using the console. I'm using git and docker in the console only. The readers of this block already know that I'm a console guy. I'm thinking about changing the console setup I use for some development tasks on Windows. Windows Terminal, PowerShell, oh-my-posh, and Winget

Winget powershell