Suppose I have these files:

foo/bar/baz/test.js
foo/bar/baz/test.min.js

If I run:

shopt -s globstar
shopt -s extglob
echo foo/bar/**/*!(.min).js

...that will nonetheless match the test.min.js file. How do I ignore it?

It seems to be a very useful feature. But I had to learn that it is often disabled by default. I though about enabling it on my system. But there is probably a good reason why it is disabled. Without knowning that, it seems unwise to enable it. Therefore my question: Why is the bash double star operator often disabled by default? I found multiple questions about how it is enabled, what the operator is named and how to use it. All of them mention that it has to be enabled first. But none of the questions explains *why* it is disabled by default.

i have several patterns that include ** wildcard, let them be: foo/**/bar.xml foo/**/baz.xml and i have an example dirtree: $ tree foo/ foo/ └── deep ├── baz.xml └── even └── deeper └── baz.xml what would be easiest way to check if any of those patterns is fulfilled? to be precise: return nonzero **only if none** is found. what I came up with so far is to use globstar and nullglob. But ls is not an option here, as if no pattern is satisfied, is lists current directory. So i had to utilize echo, like this: $ (shopt -s globstar nullglob; echo foo/**/bar.xml foo/**/baz.xml) | grep . foo/deep/baz.xml foo/deep/even/deeper/baz.xml $ echo $? 0 vs $ (shopt -s globstar nullglob; echo foo/**/bar.xml foo/**/beque.xml) | grep . $ echo $? 1 so yeah - it works. but maybe i missed something and there is **simpler/more elegant** way to achieve this?

I wanted to create a glob expression to ignore any file inside a dont_doc directory, but when I tried using using GLOBIGNORE to do it, it did not work:

$ GLOBIGNORE='**/dont_doc/**'
$ echo dont_doc/**
dont_doc/customBlockHelpers.hbs.js dont_doc/RoClasses.js dont_doc/RoEnums.js dont_doc/RoModules.js dont_doc/RoTypes.js

this is what I want to happen:

dont_doc/doc.js #Fail
dont_doc/lol/doc.js #Fail
lol/dont_doc/doc.js #Fail
lol/dont_doc/lol/doc.js #Fail
lol.js #Succsed
index.html #Fail
oof/lol.js #Succsed

how do I fix this? **Edit:** I also want to ignore the node_modules folder

I'm trying to use find with *globs* in a Bash shell script. I've tried to both sourcing it and running it, but the command fails every time.

#!/usr/bin/env bash
# glob-test.sh - a script to test globs in find
cd /to/a/windows/share-point
find ./**/*Some/*Place/**/ -iname "*.pdf"

# How about using foreign characters?
find ./**/*Söme/*Pläce/**/ -iname "*.pdf"

* From bash command line it works * I have tried different way of quoting it. * I have tried *sourcing* and *executing* the script. * I have tried turning on/off the *globstar* shell option, both inside and outside the script, but still no go. (shopt -s/u globstar) What is the problem and how to fix it?

Can using bash's globstar (**) operator cause an out of memory error? Consider something like:

for f in /**/*; do printf '%s\n' "$f"; done

When ** is being used to generate an enormous list of files, assuming the list is too large to fit in memory, will bash crash or does it have a mechanism to handle this? I know I've run ** on humongous numbers of files and haven't noticed a problem, so I am assuming that bash will use something like temporary files to store some of the list as it is being generated. Is that correct? Can bash's ** handle an arbitrary number of files or will it fail if the file list exceeds what can fit in memory? If it won't fail, what mechanism does it use for this? Something similar to the temp files generated by sort?

I have this directory structure: ~/tmp/globstar ɀ find dir -type f dir/file.ext dir/subdir1/file.ext dir/subdir2/file.ext and, with the globstar option enabled in Bash, I can say: ~/tmp/globstar ɀ ls -1 dir/**/*.ext dir/subdir1/file.ext dir/subdir2/file.ext My question is: why is dir/file.ext excluded from this list? Bash manual says this about globstar: > If set, the pattern ‘**’ used in a filename expansion context will match all files and zero or more directories and subdirectories. If the pattern is followed by a ‘/’, only directories and subdirectories match. “**zero**” in this paragraph let me with the impression that dir/file.ext should have been included; unless I’m hopefully missing something.