On Thu, Aug 12, 2010 at 01:23:20PM +1000, Martin Schwenke wrote:
> Description:
> I don't believe that the following behaviour is sensible or
> matches the standard/documentation:
>
> $ f () { { echo 1 ; echo 2 ; } | while read line ; do echo $line ;
> return 0 ; done ; echo f
> On Thu, Aug 12, 2010 at 1:46 PM, Jan Schampera wrote:
> >> while read -d'' -n1 ch; do
On Thu, Aug 12, 2010 at 01:50:34PM +0800, Sharuzzaman Ahmat Raslan wrote:
> Which part is the mistake, and what is the solution?
If you want the argument of -d to be an empty string, you have to separate
the
On 8/9/10 12:02 PM, Egmont Koblinger wrote:
> Hello,
>
> I've found a weird behavior. In some circumstances, if I use TAB completion
> during typing a command line, the final command is parsed differently than
> if I typed it all along.
>
> I'm on Ubuntu Lucid. The bug described below occurs on
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc -I/usr/src/packages/BUILD/bash-4.1
-L/usr/src/packages/BUILD/bash-4.1/../readline-6.1
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MAC
On Thu, 12 Aug 2010 08:16:21 -0400, Greg Wooledge
wrote:
> You already know the reason it behaves the way it does, so I'm not
> quite sure what answer you expect to receive. It's not a bug -- it's
> the normal behavior of every shell.
>
> imadev:~$ sh -c 'f() { (return 0); return 1; }; f; echo
On 8/12/10 6:37 PM, lstee...@gmail.com wrote:
> Bash Version: 4.1
> Patch Level: 7
> Release Status: release
>
> Description:
> PIPESTATUS never shows more than 1 array element after executing a
> multiple command pipe
>
> Repeat-By:
> Execute the following script:
>
> #!/bin/bash
