Re: Passing list of filename suffixes to script.

[Alex fxmbsw7 Ratchev]

if it is separation of stuffix types, you need to ( separate )
one is *.c the other -i,v ( *,v ? )

you at at most combine all together at the end, before, together all
in-each-type and you can generate ( or use {brace,expand} )

what i try to say is, you can at most together-in-one-step one type of
stuffix, or common ones, erm..

call_that -i{.{c,h},\,v}

On Sat, Jul 24, 2021 at 7:23 PM Greg Wooledge <greg@wooledge.org> wrote:
>
> On Sat, Jul 24, 2021 at 07:11:58PM +0200, dora-solomon@brusseler.com wrote:
> > call_rsync -i{.c,.f} -- more here for rsync
> >
> > There is the problem of how to pass ,v and other non-period suffixes.
>
> Oh, so the original problem specification was all wrong?  You're NOT
> actually passing a list of suffixes to a script, and then trying to
> generate a command dynamically from the positional parameters within
> the script?
>
> That would have been good to know.
>
> It sounds like the new problem specification is:
>
> "I have a known list of suffixes that I want to pass to rsync, and I
> have been using the bash brace expansion syntax to do it, but it
> doesn't work when my suffixes contain literal commas."
>
> Simply stop using the brace expansion syntax within your script.  Write
> the arguments out explicitly instead.
>
> call_rsync -i.c -i.f -i,v
>