On Tue, Sep 21, 2021 at 17:24:16 +0930, Brett Lymn wrote: > On Tue, Sep 21, 2021 at 07:08:16AM +0300, Valery Ushakov wrote: > > > > nl/nonl are defined to affect *input* translation, turning off ICRNL, > > so that apps can distinguish carriage return key. I *guess* that the > > code changes ONLCR in lockstep out of lazyness, so that for apps that > > run with echo/nl the nl->cr+nl on output is done by tty(4). Of course > > that bites back by messing up cud1. I would say this is saving a > > penny losing a pound. > > Well, ONLCR is not explicitly unset on start up AFAICT, the state is > noted and the refresh code handles it.
Right, right, but this is ... deeply embarassing. Please, can we get this fixed? -uwe
