On Wed, 2006-09-20 at 15:43 -0400, Ralf Wildenhues wrote:
> [ Behdad, this is:
> http://lists.gnu.org/archive/html/bug-gnulib/2006-09/msg00221.html ]
>
> Hello Paul,
>
> * Paul Eggert wrote on Tue, Sep 19, 2006 at 06:10:07PM CEST:
> > Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> >
> > > * gnu
Hello Paul,
* Paul Eggert wrote on Thu, Sep 21, 2006 at 12:18:31AM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> >> That doesn't sound like much of a real problem, but if it is, this
> >> looks to me like a band-aid that doesn't solve things; it'd cut down
> >> the number of bogus messa
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>> That doesn't sound like much of a real problem, but if it is, this
>> looks to me like a band-aid that doesn't solve things; it'd cut down
>> the number of bogus messages without eliminating them.
>
> This I don't understand. If I do the output with
[ Behdad, this is:
http://lists.gnu.org/archive/html/bug-gnulib/2006-09/msg00221.html ]
Hello Paul,
* Paul Eggert wrote on Tue, Sep 19, 2006 at 06:10:07PM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > * gnulib-tool (func_version): Create output all at once, to
> > avoid trigg
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> * gnulib-tool (func_version): Create output all at once, to
> avoid triggering unnecessary SIGPIPEs.
gnulib-tool doesn't trap SIGPIPE before invoking that code, so you
must be worried about the case where the caller traps SIGPIPE? That
do
Hello Paul,
* Paul Eggert wrote on Sat, Sep 16, 2006 at 10:34:52PM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > * gnulib-tool (func_exit): New function, to allow to pass the
> > exit status portably through the trap. Use everywhere.
> > (--help, --version): Signal a writ
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> * gnulib-tool (func_exit): New function, to allow to pass the
> exit status portably through the trap. Use everywhere.
> (--help, --version): Signal a write error.
> (trap): catch SIGPIPE, for write errors.
> Exit at the
