On 30/11/2022 at 18:59, Kenny McCormack wrote :
> Note: not looking for workarounds, got plenty of my own.
> In particular, if you have to code a loop, that takes the fun out of it.
>
> Anyway, suppose I do:
>
> $ set -- foo bar bletch
>
> I want to pass these args to a subprogram with "/*.c" appended to each.
>
> So, I'd like for:
>
> $ someCommand "${@/$/\/*.c}"
>
> to work, but it does not. This is b/c the above bash syntax doesn't deal
> in reg exps; it is some other kind of pattern matcher.
>
> I seem to remember that there is a way to do this, but I can't recall it
> ATM. Any ideas?
>

Hi,

$ set -- cp dd
$ echo ${@/%/\/*.c}
cp/cp.c cp/utils.c dd/args.c dd/conv.c dd/conv_tab.c dd/dd.c dd/gen.c
dd/misc.c dd/position.c
$ echo "${@/%/\/*.c}"
cp/*.c dd/*.c

/% means replace from the end
/# from the beginning

Regards,

Cyrille Lefevre.
--
mailto:Cyrille.Lefevre-news%nospam@laposte.net.invalid
remove "%nospam" and ".invalid" to answer me.

In article <653b39b4$0$7462$426a34cc@news.free.fr>,
Cyrille Lefevre <Cyrille.Lefevre-news%nospam@laposte.net.invalid> wrote:
>On 30/11/2022 at 18:59, Kenny McCormack wrote :
>> Note: not looking for workarounds, got plenty of my own.
>> In particular, if you have to code a loop, that takes the fun out of it.
>>
>> Anyway, suppose I do:
>>
>> $ set -- foo bar bletch
>>
>> I want to pass these args to a subprogram with "/*.c" appended to each.
>>
>> So, I'd like for:
>>
>> $ someCommand "${@/$/\/*.c}"
>>
>> to work, but it does not. This is b/c the above bash syntax doesn't deal
>> in reg exps; it is some other kind of pattern matcher.
>>
>> I seem to remember that there is a way to do this, but I can't recall it
>> ATM. Any ideas?
>>
>
>Hi,
>
>$ set -- cp dd
>$ echo ${@/%/\/*.c}
>cp/cp.c cp/utils.c dd/args.c dd/conv.c dd/conv_tab.c dd/dd.c dd/gen.c
>dd/misc.c dd/position.c
>$ echo "${@/%/\/*.c}"
>cp/*.c dd/*.c
>
>/% means replace from the end
>/# from the beginning

Yes! Thank you! This is Usenet working as it was intended. A rarity
these days!

And, indeed, I found this in "man bash":

${parameter/pattern/string}
Pattern substitution. The pattern is expanded to produce a pat-
tern just as in pathname expansion. Parameter is expanded and
the longest match of pattern against its value is replaced with
string. If pattern begins with /, all matches of pattern are
replaced with string. Normally only the first match is
replaced. If pattern begins with #, it must match at the begin-
ning of the expanded value of parameter. If pattern begins with
%, it must match at the end of the expanded value of parameter.
If string is null, matches of pattern are deleted and the / fol-
lowing pattern may be omitted. If parameter is @ or *, the sub-
stitution operation is applied to each positional parameter in
turn, and the expansion is the resultant list. If parameter is
an array variable subscripted with @ or *, the substitution
operation is applied to each member of the array in turn, and
the expansion is the resultant list.

The bit about % and # is there in the text. I just never noticed it before.

--
Life's big questions are big in the sense that they are momentous. However, contrary to
appearances, they are not big in the sense of being unanswerable. It is only that the answers
are generally unpalatable. There is no great mystery, but there is plenty of horror.
(https://en.wikiquote.org/wiki/David_Benatar)