This has JUST started to happen to me recently a few months ago, when sshing into a server and running screen with an emacs inside. When I reconnect and restar

This has JUST started to happen to me recently a few months ago, when sshing into a server and running screen with an emacs inside. When I reconnect and restart screen back into emacs, ^S pauses output instead of doing an incremental search. I have to pop out of screen with the right escape sequence to get to the login shell I ran it in, then go "stty -ixon" to disable XON/XOFF flow control. Or always remember to do that before running "screen -RD". But I never ASKED for flow control, and it has worked PERFECTLY for decades without ever getting into +ixon mode, until just a few months ago, and now it happens every single time. Did something change recently, is ubuntu auto-installing earth shattering patches that maliciously change the default tty settings behind my back (because XON/XOFF flow control suddenly became cool again?), or did I take a walk on a foggy night and accidentally slip into an alternate universe where it's always been that way for everyone else, and I'm about to be seized by silent men in white coats and taken asylum which turns out to be a rehab clinic for people who can't read minds? https://en.wikipedia.org/wiki/All_the_Myriad_Ways https://en.wikipedia.org/wiki/All_the_Myriad_Ways I finally gave up and put an "stty -ixon" in my .bashrc, but I get the ominous feeling that's one of those tempting but dangerous kludges you're not supposed to do -- Isn't there a superstition about never touching your tty in an rc file? Or is that never touching your pp in a login file? -- that can come back and bite you in the ass later when you least expect it. It seems like this is just the latest in a long series of cascading ass bites.