Re: doesn't bash do variable subst. or quote removal on function statement

2016-01-12 Thread Linda Walsh
Greg Wooledge wrote: On Tue, Jan 12, 2016 at 11:52:47AM -0800, Linda Walsh wrote: Also, from a documentation standpoint, not all behaviors are documented in the manpage, like: echo $[1+2] as far as I can tell, isn't documented, yet not supporting its behavior would break many older

Re: doesn't bash do variable subst. or quote removal on function statement

2016-01-12 Thread Greg Wooledge
On Tue, Jan 12, 2016 at 11:52:47AM -0800, Linda Walsh wrote: > Also, from a documentation standpoint, not all behaviors are documented > in the manpage, like: > > echo $[1+2] > > as far as I can tell, isn't documented, yet not supporting > its behavior would break many older scripts That

Re: doesn't bash do variable subst. or quote removal on function statement

2016-01-12 Thread Linda Walsh
Chet Ramey wrote: No. The shell doesn't perform any word expansions on the `name' when executing a function definition command. Since the documentation doesn't say it performs any expansions, why would you assume it does? Because it does quote quote removal on other statements that

Re: implicit redirection of background within pipeline

2016-01-12 Thread Chet Ramey
On 1/10/16 2:23 AM, Martin D Kealey wrote: > Bash Version: 4.3 > Patch Level: 11 > Release Status: release > > Description: > The first backgrounded element within a pipeline component has its > stdin redirected to /dev/null; this does not apply to the second and > subsequent

Re: implicit redirection of background within pipeline

2016-01-12 Thread Martin Kealey
On Mon, 11 Jan 2016, Chet Ramey wrote: > "The standard input for an asynchronous list, before any explicit > redirections are performed, shall be considered to be assigned to a file > that has the same properties as /dev/null." I thought the (only) point of that to avoid a background job