Hello Chet,
* Chet Ramey wrote on Mon, Jan 31, 2011 at 04:37:32PM CET:
> On 1/30/11 3:50 AM, Ralf Wildenhues wrote:
> >> On Sat, Jan 29, 2011 at 5:58 PM, Chet Ramey wrote:
> >>> On 1/25/11 10:08 PM, Peter O'Gorman wrote:
> >>>> for lt_wr_ar
Hello,
* Dan McGee wrote on Sun, Jan 30, 2011 at 01:04:17AM CET:
> On Sat, Jan 29, 2011 at 5:58 PM, Chet Ramey wrote:
> > On 1/25/11 10:08 PM, Peter O'Gorman wrote:
> >> for lt_wr_arg
> >> do
> >> case \$lt_wr_arg in
> >> --lt-*) ;;
> >> *) set x "$@" "$lt_wr_arg"; shift;;
> >>
Hello Andreas,
* Andreas Schwab wrote on Thu, Dec 11, 2008 at 10:13:18AM CET:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > foo: line 20: echo: write error: Broken pipe
> > foo: line 21: echo: write error: Broken pipe
> > Please also note that the above err
Hello bug-bash readers,
I noticed the following bash bug when using gnulib-tool. The script
below outputs
foo: line 20: echo: write error: Broken pipe
foo: line 21: echo: write error: Broken pipe
with bash 3.2.48(5)-release on GNU/Linux, whereas I think it should be
silent. Please note that th
* Stephane Chazelas wrote on Sun, Nov 02, 2008 at 09:53:15AM CET:
> On Sat, Nov 01, 2008 at 11:21:01PM -, Sven Mascheck wrote:
> [...]
> > : > stdout > stderr
> [...]
> > > It fails on old Ultrix sh, which can't redirect the same fd more than once
> > > in a single statement. But that pl
Hi Stephane,
* Stephane Chazelas wrote on Tue, Oct 28, 2008 at 11:26:18AM CET:
>
> I have to admit I would have thought the code above to be safe
> as well and I wonder if it's the same on all systems. But I can
> reproduce the problem on Linux. As far as I can tell, if you
> don't use O_APPEND,
Hello bug-bash readers,
in Autoconf, we've stumbled over a problem that has us a bit lost.
More precisely, it's output from asynchronous lists that gets lost
somewhere. I can't say whether it's due to the shell (it happens
with bash, pdksh, zsh, dash), due to the operating system (seen on
GNU/Lin
Hello everybody,
* Linda W wrote on Mon, Mar 20, 2006 at 10:16:44PM CET:
> Henrik Nordstrom wrote:
> >Note: As far as I can tell the echo tests in the configure script
> >generated by autoconf-2.59 tests for quite many things but not \digit as
> >far as I can tell. I have not yet looked into the C
* Ralf Wildenhues wrote on Tue, Mar 21, 2006 at 05:02:49PM CET:
>
> The issue is not in Autoconf, but in the macro AC_CREATE_PREFIX_CONFIG_H
[...]
> I will look into that, and post an update.
To finish this up for squid: Please install the patches below (it'd be
nice if you could
* Ralf Wildenhues wrote on Tue, Mar 21, 2006 at 05:02:49PM CET:
> FWIW, are there _any_ other shells that do not output \1 with
> echo "\\1"
> except for bash-3.0-with-xpg-echo?
Ouch. Never mind that stupid question, please.
_
Why does the shell snippet
exec 5>file
echo foo >&5
echo bar >&5
cause repeated dup()ing and close()ing of the file descriptor instead of
a simple write() to the already open file descriptor, as pointed out in
[1]?
Looks like a simple optimization to avoid 2 of 3 syscalls (disclaimer: I
hav
GNU Libtool suffers[1] from the fact that repeated concatenation
var=
for elem in $long_list
do
var="$var $elem"
done
scales quadratically in the number of list elements. Now while most if
not all common shells exhibit this behavior, and it happens even when
you append a constant str
12 matches
Mail list logo
