Steffen Nurpmeso wrote in <20240827234659.1xfh6CZb@steffen%sdaoden.eu>: ... |..and it seems that if bash starts a normal process then ICRNL is |set, but if it starts a (process)& or only process&, then not!
Yeah, and it seems to me it should not, since programs have to fetch the terminal defaults in order to be able to properly restore them, and unfortunately we restored without ICRNL thus. I consider to do ./lib/sh/shtty.c: ttp->c_iflag |= ICRNL; /* make sure we get CR->NL on input */ myself always, but of course then *i* as a secondary (at best) process modify the terminal settings in a way others could fail to correct. (I mean, surely, a job control shell will fix that, but it is not nice, anyway.) Ciao! --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
