Re: $() parsing still broken

2009-09-20 Thread Jan Schampera
Jan Schampera schrieb: It was a "fresh" install. Unpacking source + applying pathces, then build *scratches beard*. And it was done without bison - my bad. Works now. Jan

Re: ulimit and ssh?

2009-09-20 Thread peter360
In my case, I just got $ ssh localhost bash -x -c 'ulimit -a' unlimited + ulimit Not very informative. Marc Herbert-6 wrote: > > peter360 a écrit : > >> Thanks for the explanation. So my understanding of the way ssh works is >> still incorrect. I am confused about at which point the two

Re: ulimit and ssh?

2009-09-20 Thread peter360
That makes sense. So the "feature" is to split all parameters on space even if they are quoted? I would vote to remove this "feature" in ssh. Thanks for the explanation. Greg Wooledge wrote: > > On Tue, Sep 08, 2009 at 11:39:02AM -0700, peter360 wrote: >> Thanks for the explanation. So my

Re: $() parsing still broken

2009-09-20 Thread Christian Weisgerber
Chet Ramey: > >> I suppose the only real variable is the revision of bison: > > > > 2.4.1 and 2.3 on my FreeBSD and OpenBSD box, respectively. > > Try 1.875 and see if the problems go away. Red herring. I found the problem, it is embarrassingly stupid, and Andreas was right. The fault lies wi

Re: $() parsing still broken

2009-09-20 Thread Chet Ramey
Christian Weisgerber wrote: > Chet Ramey: > >> I suppose the only real variable is the revision of bison: > > 2.4.1 and 2.3 on my FreeBSD and OpenBSD box, respectively. Try 1.875 and see if the problems go away. That version worked for me on FreeBSD; my Mac OS X boxes use 2.0 Chet -- ``The ly

Re: $() parsing still broken

2009-09-20 Thread Christian Weisgerber
Chet Ramey: > I suppose the only real variable is the revision of bison: 2.4.1 and 2.3 on my FreeBSD and OpenBSD box, respectively. -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: $() parsing still broken

2009-09-20 Thread Chet Ramey
Christian Weisgerber wrote: > Chet Ramey: > >> Christian Weisgerber wrote: >>> Even in the latest bash, 4.0.33, $() parsing is still broken: >>> >>> $ bash -c 'echo $(echo \|)' >>> bash: -c: line 0: unexpected EOF while looking for matching `)' >>> bash: -c: line 1: syntax error: unexpected end of

Re: $() parsing still broken

2009-09-20 Thread Jan Schampera
Andreas Schwab schrieb: Jan Schampera writes: I can reproduce it. What can I do to help tracking it down? Make sure the parser was regenerated after applying patch 1. It was a "fresh" install. Unpacking source + applying pathces, then build *scratches beard*. Jan aka TheBonsai

Re: $() parsing still broken

2009-09-20 Thread Christian Weisgerber
Chet Ramey: > Christian Weisgerber wrote: > > Even in the latest bash, 4.0.33, $() parsing is still broken: > > > > $ bash -c 'echo $(echo \|)' > > bash: -c: line 0: unexpected EOF while looking for matching `)' > > bash: -c: line 1: syntax error: unexpected end of file > > > > And yes, this is

Re: $() parsing still broken

2009-09-20 Thread Andreas Schwab
Jan Schampera writes: > I can reproduce it. What can I do to help tracking it down? Make sure the parser was regenerated after applying patch 1. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something co

Re: $() parsing still broken

2009-09-20 Thread Jan Schampera
Hey Chet, I can reproduce it. What can I do to help tracking it down? bon...@core:~/devel/bash-4.0$ ./bash -c 'echo $(echo \|)' ./bash: command substitution: line 1: syntax error near unexpected token `)' ./bash: command substitution: line 1: `echo \|)' bon...@core:~/devel/bash-4.0$ ./bash -c 'e