Question about extended globbing

Question about extended globbing

[David Gómez]

Hi all ;),

I'm trying to create a pattern to match a given set of files that do not
match some pattern. I found that the ^ globbing operator, with the option
extended_glob set would help me to do this, but the thing is that i don't
know how to make two patterns to be affected by this operator,

I tried something like:

grep something $FOO/^{*txt,*info}

but it didn't work. How can I achieve to include several alternatives with
the ^ operator?

Thanks,

-- 
David Gómez

"The question of whether computers can think is just like the question of
whether submarines can swim." -- Edsger W. Dijkstra

Re: Question about extended globbing

[DervishD]

    Hi David :)

 * Davilín <david@pleyades.net> dixit:
> grep something $FOO/^{*txt,*info}
> 
> but it didn't work. How can I achieve to include several alternatives with
> the ^ operator?

    Like this: grep something $FOO/^(*txt|*info)

    I may be wrong, of course, but I think that the braces you are
using are took literally in the pattern, or they are used just for
brace expansion, generating something like:

    grep something $FOO/^*txt $FOO/^*info

    That way, when filename generation takes place, it expands the
first expression, which include any *info file, and then it expands
the second expression, which contains any *txt file.

    I think we are in the second case, brace expansion and after that
filename generation. See if you have dupes in the generated file list
(use 'print' instead of grep. I've done and I have two lists, the
first doesn't include any *txt file, the second doesn't include any
*info file).

    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: Question about extended globbing

[David Gómez]

Hi Raúl ;),

>  * Davilín <david@pleyades.net> dixit:
> > grep something $FOO/^{*txt,*info}
> > 
> > but it didn't work. How can I achieve to include several alternatives with
> > the ^ operator?
> 
>     Like this: grep something $FOO/^(*txt|*info)

I knew that the answer had to be simple ;), i just was to sleepy yesterday
to think of this solution ;)).

>     grep something $FOO/^*txt $FOO/^*info
> 
>     That way, when filename generation takes place, it expands the
> first expression, which include any *info file, and then it expands
> the second expression, which contains any *txt file.

I see...

>     I think we are in the second case, brace expansion and after that
> filename generation. 

I think they're are took literally. If a type 'grep something $FOO/^*txt' or
the solution you gave me above, the filenames are generated when Tab is
pressed, but not in the case of the braces, it seems they're are ignored
after the ^ operator.

> See if you have dupes in the generated file list

It works great ;), thanks for your help.


-- 
David Gómez

"The question of whether computers can think is just like the question of
whether submarines can swim." -- Edsger W. Dijkstra

Re: Question about extended globbing

[DervishD]

    Hi David :)

 * Davilín <david@pleyades.net> dixit:
> >     I think we are in the second case, brace expansion and after that
> > filename generation. 
> I think they're are took literally.

    Not, at least not for me: two lists, with the appropriate pattern
removed, are generated.

> If a type 'grep something $FOO/^*txt' or
> the solution you gave me above, the filenames are generated when Tab is
> pressed, but not in the case of the braces, it seems they're are ignored
> after the ^ operator.

    Then you don't have RC_EXPAND_PARAM set. That way, you get:

    grep $FOO^*txt *info

    after the expansion, prior to filename generation ;)
 
    Raúl Núñez de Arenas Coronado

-- 
Linux Registered User 88736
http://www.pleyades.net & http://raul.pleyades.net/

Re: Question about extended globbing

[David Gómez]

Hi Raúl ;),

> > If a type 'grep something $FOO/^*txt' or
> > the solution you gave me above, the filenames are generated when Tab is
> > pressed, but not in the case of the braces, it seems they're are ignored
> > after the ^ operator.
> 
>     Then you don't have RC_EXPAND_PARAM set. That way, you get:

I didn't know that option ;)... Ok, i just have found it in the
documentation, so i'll give it a look.

Thanks :)

-- 
David Gómez

"The question of whether computers can think is just like the question of
whether submarines can swim." -- Edsger W. Dijkstra