>>>>> "CR" == Chet Ramey <chet.ra...@case.edu> writes: CR> Is everything you don't like that's not explicitly documented a bug? In CR> any case, a little thought should tell you why having the shell stick CR> around long enough to catch the child's death makes a difference.
With me you can exclude the concept of thought. Never had, never will. Therefore we need hard details on the man page. E.g., "make sure there is at least a /bin/echo, or better yet sleep 0 after your command, not just a ':' or echo, or else the shell might finish too quick to see the message". "To always not see the message, kill(1) with -SIG..." CR> And what is the `set +mb promise'? OK, I thought those messages had to do with job control.
