Bernd Eggink wrote:
> GNU bash, Version 4.0.17(1)-release (i686-pc-linux-gnu)
>
> The shell doesn't recognize the closing parenthesis of a command
> substitution if a 'case' command is included and 'esac' is preceded by
> newline. Example:
>
> x=$(case $a in
>> (1) echo one
>> esac
>> )
>>
>
Tr
seren...@exscape.org wrote:
> Bash Version: 4.0
> Patch Level: 17
> Release Status: release
>
> Description:
> When using [a-*] globbing options, the very last UPPERCASE letter is
> not matched, however all other ones are.
>
> Repeat-By:
> mkdir test; cd test; for LETTER in {a..f};
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: x86_64-pc-linux-gnu-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/s
GNU bash, Version 4.0.17(1)-release (i686-pc-linux-gnu)
The shell doesn't recognize the closing parenthesis of a command
substitution if a 'case' command is included and 'esac' is preceded by
newline. Example:
x=$(case $a in
> (1) echo one
> esac
> )
>
You can enter as many ')' as you like,
On Wed, Apr 15, 2009 at 02:46:45PM +0200, Anakim Border wrote:
> is there any way to notice commands exiting with a non-zero status
> inside a process substitution?
>
> For example:
>
> $ cat <(exit 1)
>
> ignores the exit status of "exit":
The whole point of the process substitution syntax is
Hi,
is there any way to notice commands exiting with a non-zero status
inside a process substitution?
For example:
$ cat <(exit 1)
ignores the exit status of "exit":
$ echo $?
0
I'm searching for something like "set -e" (doesn't work in this case)
to make the whole command fail.
I'm using b
