Re: Wanted: quoted param expansion that expands to nothing if no params

> On Mar 23, 2021, at 11:43 PM, Eli Schwartz wrote: > > On 3/23/21 11:24 PM, L A Walsh wrote: >> Too often I end up having to write something like >> if (($#)); then "$@" >> else # = function or executable call >> fi >> >> It would be nice to have a expansion that preserves arg boundaries

Re: Wanted: quoted param expansion that expands to nothing if no params

On 3/23/21 11:24 PM, L A Walsh wrote: > Too often I end up having to write something like > if (($#)); then "$@" > else   # = function or executable call > fi > > It would be nice to have a expansion that preserves arg boundaries > but that expands to nothing when there are 0 parameters > (be

Wanted: quoted param expansion that expands to nothing if no params

Too often I end up having to write something like if (($#)); then "$@" else # = function or executable call fi It would be nice to have a expansion that preserves arg boundaries but that expands to nothing when there are 0 parameters (because whatever gets called still sees "" as a paramet

Re: Redirection between assignment statement and command name prevents alias substitution

Date:Tue, 23 Mar 2021 20:27:27 +0200 From:=?UTF-8?B?T8SfdXo=?= Message-ID: | Apparently I couldn't make myself clear there, Perhaps, or I was just failing to understand. Never mind. But this (as you know) was nothing like I imagined you meant. | # doesn't wo

Redirection between assignment statement and command name prevents alias substitution

On Tue, Mar 23, 2021 at 8:14 PM Robert Elz wrote: > | (except aliases that > | appear in a place where only a here document body may appear, but no > shell > | does that the way I think they'd do, so..) > > What do you expect there? A here doc body comes after a newline after a > here doc

Re: Redirection between assignment statement and command name prevents alias substitution

Date:Tue, 23 Mar 2021 14:51:02 +0300 From:=?UTF-8?B?T8SfdXo=?= Message-ID: | (except aliases that | appear in a place where only a here document body may appear, but no shell | does that the way I think they'd do, so..) What do you expect there? A here doc b

Re: Redirection between assignment statement and command name prevents alias substitution

On Tue, Mar 23, 2021 at 2:26 PM Robert Elz wrote: > though the NetBSD sh does expand it dash and NetBSD sh do aliases just the way I expect (except aliases that appear in a place where only a here document body may appear, but no shell does that the way I think they'd do, so..), it's fascinatin

Re: Redirection between assignment statement and command name prevents alias substitution

Date:Tue, 23 Mar 2021 13:10:19 +0300 From:=?UTF-8?B?T8SfdXo=?= Message-ID: | $ echo a > a | $ echo b > b | $ alias l='< ' a=b | $ l a cat | a | | I can't think of any reason not to expand `a' there. I can think of a reason (though the NetBSD sh does

Re: Redirection between assignment statement and command name prevents alias substitution

On Tue, Mar 23, 2021 at 11:01 AM Robert Elz wrote: > Kind of interesting that ksh93 seems to do the same thing. > Yeah, I don't know, might be a coincidence. Another curious case where ksh93 differs in behavior from all other shells I have is this: $ echo a > a $ echo b > b $ alias l='< ' a=b $

Re: missing way to extract data out of data

On Mär 22 2021, Dale R. Worley wrote: > Greg Wooledge writes: >> Partly true. seq(1) is a Linux thing, and was never part of any >> tradition, until Linux people started doing it. > > Huh. I started with Ultrix, and then SunOS, but don't remember learning > seq at a later date. According to

Re: Redirection between assignment statement and command name prevents alias substitution

Date:Tue, 23 Mar 2021 08:43:54 +0200 From:=?UTF-8?B?T8SfdXo=?= Message-ID: | $ a=b >&2 u | No command u found, did you mean: Kind of interesting that ksh93 seems to do the same thing. No other shell I was able to test however (including ancient pdksh