Globs

"Glob" is the common name for a set of Bash features that match or expand specific types of patterns. Some synonyms for globbing (depending on the context in which it appears) are pattern matching, pattern expansion, filename expansion, and so on. A glob may look like *.txt and, when used to match filenames, is sometimes called a "wildcard".

Traditional shell globs use a very simple syntax, which is less expressive than a RegularExpression. Most characters in a glob are treated literally, but a * matches 0 or more characters, a ? matches precisely one character, and [...] matches any single character in a specified set (see Ranges below). All globs are implicitly anchored at both start and end. For example:

Bash expands globs which appear unquoted in commands, by matching filenames relative to the current directory. The expansion of the glob results in 1 or more words (0 or more, if certain options are set), and those words (filenames) are used in the command. For example:

   1 tar xvf *.tar
   2 # Expands to: tar xvf file1.tar file2.tar file42.tar ...
   3 # (which is generally not what one wants)

Even if a file contains internal whitespace, the expansion of a glob that matches that file will still preserve each filename as a single word. For example,

   1 # This is safe even if a filename contains whitespace:
   2 for f in *.tar; do
   3     tar tvf "$f"
   4 done
   5 
   6 # But this one is not:
   7 for f in $(ls | grep '\.tar$'); do
   8     tar tvf "$f"
   9 done

In the second example above, the output of ls is filtered, and then the result of the whole pipeline is divided into words, to serve as iterative values for the loop. This word-splitting will occur at internal whitespace within each filename, which makes it useless in the general case. The first example has no such problem, because the filenames produced by the glob do not undergo any further word-splitting. For more such examples, see BashPitfalls.

Globs are also used to match patterns in a few places in Bash. The most traditional is in the case command:

   1 case "$input" in
   2     [Yy]|'') confirm=1;;
   3     [Nn]*) confirm=0;;
   4     *) echo "I don't understand.  Please try again.";;
   5 esac

Patterns (which are separated by | characters) are matched against the first word after the case itself. The first pattern which matches, "wins", causing the corresponding commands to be executed.

Bash also allows globs to appear on the right-hand side of a comparison inside a [[ command:

   1 if [[ $output = *[Ee]rror* ]]; then ...

Finally, globs are used during parameter expansion to indicate patterns which may be stripped out, or replaced, during a substitution. Simple examples (there are many more on the previously referenced page):

   1 filename=${path##*/}    # strip leading pattern that matches */ (be greedy)
   2 dirname=${path%/*}      # strip trailing pattern matching /* (non-greedy)
   3 
   4 printf '%s\n' "${arr[@]}"          # dump an array, one element per line
   5 printf '%s\n' "${arr[@]/error*/}"  # dump array, removing error* if matched

(Reference: Arrays Quotes printf.)

Ranges

Globs can specify a range or class of characters, using square brackets. This gives you the ability to match against a set of characters. For example:

In most shell implementations, one may also use ^ as the range negation character, e.g. [^[:space:]]. However, POSIX specifies ! for this role, and therefore ! is the standard choice.

globasciiranges (since bash 4.3-alpha)

Interprets [a-d] as [abcd]. To match a literal -, include it as first or last character.

For older versions

Note that Implementation-defined means it may work as you expect on one machine, but give completely different results on another machine. Do not use the m-n syntax unless you have explicitly set your locale to C first, or you may get unexpected results. The POSIX character class expressions should be preferred whenever possible.

Options which change globbing behavior

extglob

In addition to the traditional globs (supported by all Bourne-family shells) that we've seen so far, Bash (and Korn Shell) offers extended globs, which have the expressive power of regular expressions. Korn shell enables these by default; in Bash, you must run the command

   1 shopt -s extglob

in your shell (or at the start of your script -- see note on parsing below) to use them. The pattern matching reference describes the syntax, which is reproduced here:

?(pattern-list)

Matches zero or one occurrence of the given patterns.

*(pattern-list)

Matches zero or more occurrences of the given patterns.

+(pattern-list)

Matches one or more occurrences of the given patterns.

@(pattern-list)

Matches one of the given patterns.

!(pattern-list)

Matches anything except one of the given patterns.

Patterns in a list are separated by | characters.

Extended globs allow you to solve a number of problems which otherwise require a rather surprising amount of ugly hacking; for example,

   1 # To remove all the files except ones matching *.jpg:
   2 rm !(*.jpg)
   3 # All except *.jpg and *.gif and *.png:
   4 rm !(*.jpg|*.gif|*.png)

   1 # To copy all the MP3 songs except one to your device
   2 cp !(04*).mp3 /mnt

To use an extglob in a parameter expansion (this can also be done in one BASH statement with read):

   1 # To trim leading and trailing whitespace from a variable
   2 x=${x##+([[:space:]])}; x=${x%%+([[:space:]])}

Extended glob patterns can be nested, too.

   1 [[ $fruit = @(ba*(na)|a+(p)le) ]] && echo "Nice fruit"

extglob changes the way certain characters are parsed. It is necessary to have a newline (not just a semicolon) between shopt -s extglob and any subsequent commands to use it. You cannot enable extended globs inside a group command that uses them, because the entire block is parsed before the shopt is evaluated. Note that the typical function body is a group command. An unpleasant workaround could be to use a subshell command list as the function body.

Therefore, if you use this option in a script, it is best put right under the shebang line.

   1 #!/usr/bin/env bash
   2 shopt -s extglob   # and others, such as nullglob dotglob

If your code must be sourced and needs extglob, ensure it preserves the original setting from your shell:

   1 # remember whether extglob was originally set, so we know whether to unset it
   2 shopt -q extglob; extglob_set=$?
   3 # set extglob if it wasn't originally set.
   4 ((extglob_set)) && shopt -s extglob
   5 # Note, 0 (true) from shopt -q is "false" in a math context.
   6 
   7 # The basic concept behind the following is to delay parsing of the globs until evaluation.
   8 # This matters at group commands, such as functions in { } blocks
   9 
  10 declare -a s='( !(x) )'
  11 echo "${s[@]}"
  12 
  13 echo "${InvalidVar:-!(x)}"
  14 
  15 eval 'echo !(x)'  # using eval if no other option.
  16 
  17 # unset extglob if it wasn't originally set
  18 ((extglob_set)) && shopt -u extglob

This should also apply for other shell options.

nullglob

nullglob expands non-matching globs to zero arguments, rather than to themselves.

   1 $ ls *.c
   2 ls: cannot access *.c: No such file or directory
   3 
   4 # with nullglob set
   5 shopt -s nullglob
   6 ls *.c
   7 # Runs "ls" with no arguments, and lists EVERYTHING

Typically, nullglob is used to count the number of files matching a pattern:

   1 shopt -s nullglob
   2 files=(*)
   3 echo "There are ${#files[@]} files in this directory."

Without nullglob, the glob would expand to a literal * in an empty directory, resulting in an erroneous count of 1.

Warning

Enabling nullglob on a wide scope can trigger bugs caused by bad programming practices. It "breaks" the expectations of many utilities.

Removing array elements:

   1 shopt -s nullglob
   2 unset array[1]
   3 #unsets nothing
   4 unset -v "array[1]"
   5 #correct

Array member assignments in compound form using subscripts:

   1 shopt -s nullglob
   2 array=([1]=*)
   3 #results in an empty array

This was reported as a bug in 2012, yet is unchanged to this day.

Apart from few builtins that use modified parsing under special conditions (e.g. declare) always use Quotes when arguments to simple commands could be interpreted as globs.

Enabling failglob, nullglob, or both during development and testing can help catch mistakes early. To prevent pathname expansion occuring in unintended places, you can set failglob. However, you must then guarantee all intended globs match at least one file. Also note that the result of a glob expansion does not always differ from the glob itself. failglob won't distinguish echo ? from echo '?' in a directory containing only a file named ?. nullglob will.

Portability

"null globbing" is not specified by POSIX. In portable scripts, you must explicitly check that a glob match was successful by checking that the files actually exist.

   1 # POSIX
   2 
   3 for x in *; do
   4     [ -e "$x" ] || break
   5     ...
   6 done
   7 
   8 f() {
   9     [ -e "$1" ] || return 1
  10 
  11     for x; do
  12         ...
  13     done
  14 }
  15 
  16 f * || echo "No files found"

Some modern POSIX-compatible shells allow null globbing as an extension.

   1 # Bash
   2 shopt -s nullglob

In ksh93, there is no toggle-able option. Rather, that the "nullglob" behavior is to be enabled is specified inline using the "N" option to the ∼() sub-pattern syntax.

   1 # ksh93
   2 
   3 for x in ~(N)*; do
   4     ...
   5 done

In zsh, an toggle-able option(NULL_GLOB) or a glob qualifier(N) can be used.

   1 # zsh
   2 for x in *(N); do ...; done # or setopt NULL_GLOB

mksh doesn't yet support nullglob (maintainer says he'll think about it).

dotglob

By convention, a filename beginning with a dot is "hidden", and not shown by ls. Globbing uses the same convention -- filenames beginning with a dot are not matched by a glob, unless the glob also begins with a dot. Bash has a dotglob option that lets globs match "dot files":

   1 shopt -s dotglob nullglob
   2 files=(*)
   3 echo "There are ${#files[@]} files here, including dot files and subdirs"

It should be noted that when dotglob is enabled, * will match files like .bashrc but not the . or .. directories. This is orthogonal to the problem of matching "just the dot files" -- a glob of .* will match . and .., typically causing problems.

globstar (since bash 4.0-alpha)

globstar recursively repeats a pattern containing '**'.

   1 $ shopt -s globstar; tree
   2 .
   3 ├── directory2
   4 │   ├── directory3
   5 │   ├── file1.c
   6 │   └── file2
   7 ├── file1
   8 └── file2.c
   9 
  10 # Suppose that for the following examples.

Matching files:

   1 $ files=(**)
   2 # equivalent to: files=(* */* */*/*)
   3 # finds all files recursively
   4 
   5 $ files=(**/*.c)
   6 # equivalent to: files=(*.c */*.c */*/*.c)
   7 # finds all *.c files recursively
   8 # corresponds to: find -name "*.c"
   9 # Caveat: **.c will not work, as it expands to *.c/*.c/…

Just like '*', '**' followed by a '/' will only match directories:

   1 $ files=(**/)
   2 # finds all subdirectories
   3 
   4 $ files=(. **/)
   5 # finds all subdirectories, including the current directory
   6 # corresponds to: find -type d

failglob

If a pattern fails to match, bash reports an expansion error. This can be useful at the commandline:

   1 # Good at the command line!
   2 $ > *.foo # creates file '*.foo' if glob fails to match
   3 $ shopt -s failglob
   4 $ > *.foo # doesn't get executed
   5 -bash: no match: *.foo

GLOBIGNORE

The Bash variable (not shopt) GLOBIGNORE allows you to specify patterns a glob should not match. This lets you work around the infamous "I want to match all of my dot files, but not . or .." problem:

   1 $ echo .*
   2 . .. .bash_history .bash_logout .bashrc .inputrc .vimrc
   3 $ GLOBIGNORE=.:..
   4 $ echo .*
   5 .bash_history .bash_logout .bashrc .inputrc .vimrc

Unset GLOBIGNORE

   1 $ GLOBIGNORE=
   2 $ echo .*
   3 . .. .bash_history .bash_logout .bashrc .inputrc .vimrc

nocasematch

Globs inside [[ and case commands are matched case-insensitive:

   1 foo() {
   2    local f r=0 nc=0
   3    shopt -q nocasematch && nc=1 || shopt -s nocasematch
   4    for f; do
   5       [[ $f = *.@(txt|jpg) ]] || continue
   6       cmd -on "$f" || r=1
   7    done
   8    ((nc)) || shopt -u nocasematch
   9    return $r
  10 }

This is conventionally done this way:

   1 case $f in
   2     *.[Tt][Xx][Tt]|*.[Jj][Pp][Gg]) : ;;
   3     *) continue
   4 esac

and in earlier versions of bash we'd use a similar glob:

   1 [[ $f = *.@([Tt][Xx][Tt]|[Jj][Pp][Gg]) ]] || continue

or with no extglob:

   1 [[ $f = *.[Tt][Xx][Tt] ]] || [[ $f = *.[Jj][Pp][Gg] ]] || continue

Here, one might keep the tests separate for maintenance; they can be easily reused and dropped,

• without having to concern oneself with where they fit in relation to an internal ||.

Note also:

   1 [[ $f = *.@([Tt][Xx][Tt]|[Jj][Pp]?([Ee])[Gg]) ]]

Variants left as an exercise.

nocaseglob (since bash 2.02-alpha1)

This option makes pathname expansion case-insensitive. In contrast, nocasematch operates on matches in [[ and case commands.

CategoryShell