Peng Yu wrote:
Hi,
http://mywiki.wooledge.org/ProcessSubstitution
The above webpage says the following.
commandA <(commandB; [commandB's exit code is available here from $?])
[commandB's exit code cannot be obtained from here. $? holds
commandA's exit code]
Does anybody have a good solu
Chet Ramey wrote:
Thanks for the report. This isn't a bug; it's intentional behavior. You
have presented bash with an ambiguous situation: it doesn't know whether
or not you want to look for a filename in the current directory or perform
variable expansion.
Bash assumes you want filename c
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -
DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-l$
uname output: Linux josua 3.13.0-46-generic #79-Ubuntu SMP Tue Ma
On Sat, 14 Mar 2015 15:17:24 +0100, kont...@marcbihlmaier.de wrote:
> Description:
> exec hangs up when using "exec 2>SOMETHING". Just tested on
> Ubuntu 14.04, Ubuntu 12.04, Debian7
> working when just using "exec 1>SOMETHING"
>
> Repeat-By:
> using in a script for loggin
On Sat, Mar 14, 2015 at 8:46 AM, Linda Walsh wrote:
>
>
> Peng Yu wrote:
>>
>> Hi,
>>
>> http://mywiki.wooledge.org/ProcessSubstitution
>>
>> The above webpage says the following.
>>
>> commandA <(commandB; [commandB's exit code is available here from $?])
>> [commandB's exit code cannot be obtain
On 3/14/15 10:12 AM, Linda Walsh wrote:
>
>
> Chet Ramey wrote:
>
>>
>> Thanks for the report. This isn't a bug; it's intentional behavior. You
>> have presented bash with an ambiguous situation: it doesn't know whether
>> or not you want to look for a filename in the current directory or perf
On 3/13/15 6:15 PM, isabella parakiss wrote:
> This works as I would expect:
>
> $ arr=(a b c); IFS=+; echo "${arr[*]/a/x}"
> x+b+c
>
>
> But for some reason, this ignores IFS:
>
> $ arr=(a b c); IFS=+; arr=${arr[*]/a/x}; echo "$arr"
> x b c
Because it doesn't occur within a double-quoted stri
