process substition and "source"

In the following example, I expected the commands in the here-documents to be interpreted in the current shell, but it seems they weren't. Is it my misunderstanding, a feature, or a bug? bash-3.2$ echo $BASH_VERSION 3.2.39(1)-release bash-3.2$ . <(cat <

Re: some variable level issues

On 2008-06-29, Matt Zyzik wrote: > bug-bash, > 2. $( want any newlines chopped off. So to remedy this, I do the > following: "IFS='' read -r -d '' var < file". Firstly, is this safe > to do, and are there any other ways? Secondly, it appears to be very > slow compared to $(http://Woodbine-Gerr

bash --noediting killed by O_NONBLOCK

Configuration Information [Automatically generated, do not change]: Machine: i686 OS: linux-gnu Compiler: i686-pc-linux-gnu-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/lo

Re: Problem with expansion of empty elements in ${arrays[*]:0}

Vítor De Araújo wrote: Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/sh

Re: Unsubstituted variables in "jobs" output

On Mon, Jun 30, 2008 at 9:23 PM, Chet Ramey <[EMAIL PROTECTED]> wrote: >> Consider the following: >> $ AA=aa; BB=bb; (sleep 10; echo $AA $BB) & jobs >> [1] 6626 >> [1]+ Running ( sleep 10; echo $AA $BB ) & >> If there any way tell jobs command to output AA and BB substituted with

Re: Unsubstituted variables in "jobs" output

> Consider the following: > $ AA=aa; BB=bb; (sleep 10; echo $AA $BB) & jobs > [1] 6626 > [1]+ Running ( sleep 10; echo $AA $BB ) & > If there any way tell jobs command to output AA and BB substituted with > their values? The variables are expanded in the subshell, not in the pare

Re: time command

Chuck Swiger wrote: On Jun 24, 2008, at 7:47 AM, Sam Steingold wrote: I would like all long-running commands to be auto-timed. i.e., all commands I type at the prompt should be run as if with "time" built-in, but if the real or user time is smaller than some value (specified by the user in an en

Unsubstituted variables in "jobs" output

Consider the following: $ AA=aa; BB=bb; (sleep 10; echo $AA $BB) & jobs [1] 6626 [1]+ Running ( sleep 10; echo $AA $BB ) & If there any way tell jobs command to output AA and BB substituted with their values? This is especially disturbing when doing something like this: for i i

Re: some variable level issues

Matt Zyzik wrote: 1. I noticed bash variables don't support null characters (0x00). This is unlike perl and other languages. Will this ever change? Have people requested or wanted this feature? Probably not; it would require considerable reworking of the variable internals. 2. $( Probably.