5 ms·
The opposite happens in CMD on Windows, at least in the past. Applications that wrote a lot to the logscreen were slowed down by it. While writing to stdout is
by OptionOfT 2y ago
The opposite happens in CMD on Windows, at least in the past.
Applications that wrote a lot to the logscreen were slowed down by it. While writing to stdout is buffered, it seems that the rendering itself runs in the same thread as the application.
Making a selection freezes the terminal and this stops the rendering, allowing the application to run much faster.
Removing the selection (by pressing escape) rerendered the window (and the buffer), and it went back to its original slowness.
- cr__ 2y agoBack in the day making a selection would actually freeze the process in some cases.
- TowerTall 2y agoTo this day I still attempt never to click inside a running cmd / powershell console. Too many times script execution has been halted by this. It is probably something that has been fixed long time ago but I am still a bit paranoid about it.
- raxxorraxor 2y agoIt isn't a bug, you could actually toggle this behavior. Don't know how the option was called and cannot find it in Windows 11. But it certainly was still there in the latest Win10 build. I think it was called something like quick edit or similar.
- junon 2y agoStill does in CMD.exe
- dimava 2y agoI guess it is intentional, otherwise you couldn't select and copy stuff at all
- raxxorraxor 2y agoThere is even an option to change the behavior so that the window doesn't freeze if you select anything. Batches freeze completely when you clicked anywhere and I found out the hard way. Probably some feature that John requested because he couldn't read some output quickly enough. I don't understand how this can be the default behavior.
- lousken 2y agoi always thought freezing the terminal causes a pause of the app as well, is it just the rendering?