I've noticed a frustrating difference when using PowerShell in Windows Terminal as compared to the CMD console. When I have a lot of code on the screen and it scrolls past the top line, in CMD.exe, I can double press HOME to scroll right to the top. However, in Windows Terminal, it simply brings me to the top visible line and then beeps, which isn't helpful. I can't seem to scroll to or edit the 'hidden' lines either. I've checked Get-PSReadLineKeyHandler, and the settings seem the same in both environments. Also, the CMD console doesn't support Nerd Fonts, so my oh-my-posh prompt doesn't look great there. My questions are: 1) Is there a way to access and edit the lines above the visible area in Windows Terminal? 2) Can I enable Nerd Fonts in CMD console for oh-my-posh to work properly? 3) I found that I can detect if I'm in Windows Terminal using $env:WT_SESSION, but can PowerShell tell if it's running in CMD.exe?
2 Answers
I’m not in front of a Windows PC right now, but can’t you right-click the title bar in Windows Terminal and access a settings menu like the old CMD console to adjust scroll buffers? Just a thought!
You should definitely report the scrolling issue to the Windows Terminal team. They can confirm if it's intentional or not, and if there's a setting or bug involved. Check out their GitHub page to submit your feedback! Also, just a heads up, the old console is actually called 'conhost', so it might be helpful to refer to it properly when reporting your issue.
Sadly, that just brings me to Windows Terminal settings, which don’t have those options.