why do you use two "**" together,

For Eample:
app.config.excludes.prod=**/log4j.dev.xml **/log4j.qa.xml **/
log4j.stg.xml **/log4j.ito.xml


Thanks

On 24 mar, 22:10, ushi <azhar....@gmail.com> wrote:
> why do you use two "**" together,
>
> For Eample:
> app.config.excludes.prod=**/log4j.dev.xml **/log4j.qa.xml **/
> log4j.stg.xml **/log4j.ito.xml
>
> Thanks

I can't remember where I read ** says like * but with possible '/'
embembed, like multiple directories expansion allowed. I suppose same
programs uses it (not bash).

* ushi <azhar.rao@gmail.com>:
> why do you use two "**" together,
>
> For Eample:
> app.config.excludes.prod=**/log4j.dev.xml **/log4j.qa.xml **/
> log4j.stg.xml **/log4j.ito.xml
>
>
> Thanks

Zsh interprets '**/' as a globbing operator that expands recursively. I
am unaware of other usages, but they may exist.

--
James Michael Fultz <xyzzy@sent.as.invalid>
Remove this part when replying ^^^^^^^^

2008-03-24, 19:47(-05), James Michael Fultz:
> * ushi <azhar.rao@gmail.com>:
>> why do you use two "**" together,
>>
>> For Eample:
>> app.config.excludes.prod=**/log4j.dev.xml **/log4j.qa.xml **/
>> log4j.stg.xml **/log4j.ito.xml
[...]
> Zsh interprets '**/' as a globbing operator that expands recursively. I
> am unaware of other usages, but they may exist.

**/ in zsh is a shortcut for (*/)# (that is 0 or more level of
subdirectories)

Recent versions of ksh93 also support ** with set -G, but it's
slightly different (** in ksh93 is **/* in zsh for instance, so
** is more like "any path"). ksh93 doesn't support *** (for
recursing into symlinks to directories as well) nor globbing
qualifiers.

In other shells, ** is like *.

--
Stéphane