3 ms·
My biggest issue with the windows terminal is my programs pausing without me noticing. Took me forever to figure out disabling “quick edit” fixes this- apparent
by snailmailman 7y ago
My biggest issue with the windows terminal is my programs pausing without me noticing. Took me forever to figure out disabling “quick edit” fixes this- apparently programs just pause completely if you have text selected? Something I keep managing to do on accident without noticing. There is almost no indication, other than the fact my loading bar froze or my program appears to be stuck.
Disabling quick edit helps, but now I can’t select text at all.
Is this behavior changed in the new terminal?
- zadjii 7y agoIronically, this is actually a behavior lots of developers do want. The new Terminal fortunately gives us much more flexibility for customizing it's behavior with user settings, so we'll be able to support either pausing output or not, depending on what the user prefers.
- OJFord 7y agoLots of people want to select text as a trigger to pause the foreground process? I'm not sure which side is misrepresented, but it sounds mad from the outside!
- Doxin 7y agoHaving your selection reset because another line got added to the log you're tail-ing is maddening, having the output pause while you're selecting is convenient --though it probably should have a timeout or some such.
- OJFord 7y agoAh - I scroll up to avoid that (and have my term set not to auto return to new line).
- frosted-flakes 7y agoYeah, I've been caught out by this a few times. I've since acquired the habit of pressing Escape to de-select if I think something might be selected.
- ScottFree 7y agoAre you saying the app itself actually freezes? Or does the terminal not automatically scroll with the new app output?