Ralf Wildenhues wrote:
> I did that, but IMHO it's a bit inconsistent:
> $ echo 2> &1
> | bash: syntax error near unexpected token `&'
'>&' is an operator on its own, and '2>&1' is an idiom that doesn't require
spaces to be understandable.
Bruno
* Bruno Haible wrote on Tue, Nov 14, 2006 at 09:30:54PM CET:
>
> You also combined adjacent sed invocations. Which rule are you using here?
> When is it safe to combine
> sed -e "$expr1" | sed -e "$expr2"
> into
> sed -e "$expr1" -e "$expr2"
> ?
Erm, for example when all of the following
Bruno Haible <[EMAIL PROTECTED]> writes:
> You also combined adjacent sed invocations. Which rule are you using here?
> When is it safe to combine
> sed -e "$expr1" | sed -e "$expr2"
> into
> sed -e "$expr1" -e "$expr2"
> ?
That's a tricky question to answer in general, but if $expr1 and
Hello Ralf,
> The patch below shaves a couple of minutes off of MODULES.html.sh's
> roughly 5 minutes worth of execution time. Half of that is achieved
> by not calling gnulib-tool more often than necessary, the other by
> eliminating a couple of quadratic file list handlings.
These are good tr
