Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14950
| From | Bize Ma <binaryzebra@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: write() not retried after EINTR in printf and echo |
| Date | 2018-12-25 16:01 -0400 |
| Message-ID | <mailman.6270.1545768091.1284.bug-bash@gnu.org> (permalink) |
| References | <CAFra36hm9XcAgwqr7Yp_giX+kiSEp__x4Mc5Qn=eqgUdSdLA7Q@mail.gmail.com> <eefa8e88-104a-1fd3-b505-a279778ba291@case.edu> <CAFra36izjDTTFBsRfzsgCr8YGk+n=7O=FiMVX=ivuh5Ejw5MAQ@mail.gmail.com> <996dc3ea-0718-481b-3dc7-4fd358a3a64e@case.edu> |
Chet Ramey (<chet.ramey@case.edu>) wrote: > On 12/19/18 10:15 PM, Bize Ma wrote: > > Ah, now we're moving the goalposts. No, that is not the intent. I merely failed to correctly convey the perception that others have of your code: https://unix.stackexchange.com/a/487260/265604 And, having failed, I am trying again. But, probably, I should just not inform you of what others think given your upfront rejection to any (constructive) criticism. There's a case to be made for doing > that, I suppose, but I'd rather defer to the system's default handling > for a particular signal. > Do as you wish, we will still be able to form our own opinion about buggy code.
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: write() not retried after EINTR in printf and echo Bize Ma <binaryzebra@gmail.com> - 2018-12-25 16:01 -0400
csiph-web