I’m using Windows 10 for my current project after more than a decade on macOS / Linux.
cmd seems to have come on a bit from Windows XP days, but I’m having one particular problem.
On macOS’s Terminal if I scroll back up to check something, when I want to go back I can fling the scroll in the other direction and it will stop at the end of the current text where the cursor is. If I do the same in Command Prompt it turns out there’s thousands of lines of blank text at the bottom beyond the cursor and I need to carefully scroll back through it to get back to the cursor. Typing something will refocus to the correct line, but only if there’s a cursor; if I’m running my test suite it waits for commands without dropping back to the shell, and won’t scroll to the correct point on typing.
I’ve been through the settings and can’t see anything obvious to change. Is there any way I can change the behaviour to match macOS’s Terminal, or am I going to have to relearn my muscle memory?