Command line terminal in Windows and page navigation in it

[CyrilleB79]

I have recently switched from Windows 10 to Windows 11.

I am facing new difficulties navigating in command line output, especially when using commands producing page-by-page output such as git log.

1. How to go to the beginning of the current page? Before, with Windows 10 cmd.exe, I could just press shift+numpad7, and then use numpad7 or numpad9 to read the current page line by line. Now in Windows 11, either in Git bash or in standard command line console, either using cmd.exe or WindowsTerminal.exe, shift+numpad7 jumps at the top of the output buffer of all the commands, what is not user-friendly at all.

2. I have tried NVDA+pgUp and NVDA+pgDown commands, but in any case, there only seems to be one unique page. I thought that this hadd been implemented at the time to read the console page by page, but this does not seem to be the case. Where are these commands actually being used?

Could you please all report if you have a console navigation as efficient as in Windows 10 legacy console, and how?
And also if you use page review commands and where?

@codeofdusk you may have answers, as a console expert, and also because if I remember correctly, you have been involved in the implementation of NVDA+pgUp/Down commands.

Many thanks to all!

[Emil-18]

@CyrilleB79 Try the console toolkit add-on and check the "Override shift+numPad7 behavior to take review cursor to the first visible line" check box

[CyrilleB79]

Hello

This is also being discussed here.
The general feeling seems to be that the new environment with WindowsTerminal is less comfortable than the old cmd, at least when using NVDA without add-ons and with factory default config.

@codeofdusk could you tell us:

• is this feeling justified, or are we just using NVDA/WindowsTerminal the wrong way?
• is page navigation in console output working, and if yes, in which condition (UIA/no-UIA, cmd/WindowsTerminal, etc.)?
• what's the best way to efficiently use page output, e.g. "git log", "less", "more", etc., in WindowsTerminal?

[lpintes]

While using Windows 11 and command line, concretely git bash, I observed for example the following: <some command> |less works as expected, git log does not, I see whole output. Dňa 12. 9. 2025 o 9:30 Cyrille Bougot napísal(a):

…

Hello This is also being discussed here <https://nvda-addons.groups.io/g/nvda-addons/topic/getting_back_old_console/115193788>. The general feeling seems to be that the new environment with WindowsTerminal is less comfortable than the old cmd, at least when using NVDA without add-ons and with factory default config. @codeofdusk <https://github.com/codeofdusk> could you tell us: * is this feeling justified, or are we just using NVDA/WindowsTerminal the wrong way? * is page navigation in console output working, and if yes, in which condition (UIA/no-UIA, cmd/WindowsTerminal, etc.)? * what's the best way to efficiently use page output, e.g. "git log", "less", "more", etc., in WindowsTerminal? — Reply to this email directly, view it on GitHub <#18616 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATNYX5NREIISZXLKIAG5ZT3SJZBFAVCNFSM6AAAAACDEKJ6HSVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZYGE2TSNY>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>