Steffen Daode Nurpmeso dixit: >Well, the minimal code to reproduce is
> |So this is probably a TNF-local problem. Doesn’t happen here… > |This may (or may not) be related to the followin feature request: > |https://bugs.launchpad.net/mksh/+bug/1064726 … which is why I suspect this one. Apparently TNF is sensible wrt. that sort of behaviour (there’s a lot of, hard to digest, information linked from that). >This will be interesting to read tomorrow. All this is very >complicated and hopeless (i *hate* signals and jumps), but in the Yeah, me too… >end i really don't think that a login shell should terminate when >a child process receives SIGINT. The problem here, if it’s that issue, is that TNF switched to requiring certain behaviour which, while it may (or may not) be better, breaks with traditional Unix semantics, which other shells may implement, and thus forces all shells to behave like that. One thing I’d really like to know is whether implementing that linked feature request would introduce any regressions on other operating environments… > |If you suspect this is the case, you’re welcome to help develop > |and test a patch. > >Uuh, mksh(1) is a complex and grown codebase, but maybe i'll be >able to overcome it :) It’s still pretty small, somewhat structured and, except for a few size hacks, well-readable code ([email protected] says so too). >Yeaaah... the user experience would be even better if the website >would describe how to subscribe to miros-mksh@. It says: “In order to subscribe, send a mail to [44]the postmaster.” (Using /etc/mail/aliases as mailing list software has benefits… especially on a good old Pentium MMX.) (Or just use GMane, be it NNTP, Web or RSS…) bye, //mira“postmaster”bilos -- „nein: BerliOS und Sourceforge sind Plattformen für Projekte, github ist eine Plattform für Einzelkämpfer“ -- dieses Zitat ist ein Beweis dafür, daß auch ein blindes Huhn mal ein Korn findet, bzw. – in diesem Fall – Recht haben kann
