On Tue, 31 Mar 2015 15:39:13 -0500, John McKown wrote:
> Hum, on my system, I get the message you are expecting. Transcript:
<-snip->
And, here...
This is puzzling.
On an older Ubuntu 10.04 system I still use (I know, I know...) I
get _no_ response. But the return code appears correct:
jonesy@n
On Wed, Apr 01, 2015 at 05:21:42PM +, Allodoxaphobia wrote:
> On an older Ubuntu 10.04 system I still use (I know, I know...) I
> get _no_ response. But the return code appears correct:
>
> jonesy@nix4:~$ uname -a
> Linux nix4 2.6.32-39-generic #86-Ubuntu SMP Mon Feb 13 21:47:32 UTC 2012 i686
Hi, This was noticed in a comment to a github issue. Just forwarding it along.
$ for ((; 1>(1) ;)); do break; done
-bash: syntax error near unexpected token `newline'
$ echo "$BASH_VERSION"
4.3.33(1)-release
https://github.com/koalaman/shellcheck/issues/255#issuecomment-88452555
Already fixed:
dualbus@yaqui:~/local/src/gnu/bash$ for ((; 1>(1) ;)); do break; done
dualbus@yaqui:~/local/src/gnu/bash$
GNU bash, version 4.4.0(1)-devel (x86_64-unknown-linux-gnu)
On Wed, Apr 01, 2015 at 12:53:16PM -0500, Dan Douglas wrote:
> Hi, This was noticed in a comment to a github issue.
On Wed, Apr 1, 2015 at 1:01 PM, Eduardo A. Bustamante López
wrote:
> Already fixed:
>
> dualbus@yaqui:~/local/src/gnu/bash$ for ((; 1>(1) ;)); do break; done
> dualbus@yaqui:~/local/src/gnu/bash$
> GNU bash, version 4.4.0(1)-devel (x86_64-unknown-linux-gnu)
>
> On Wed, Apr 01, 2015 at 12:53:16PM -
