In computer programming, glob (//) patterns specify sets of filenames with wildcard characters. For example, the Unix Bash shell command
mv *.txt textfiles/ moves (
mv) all files with names ending in
.txt from the current directory to the directory
* is a wildcard standing for "any string of characters except /" and
*.txt is a glob pattern. The other common wildcard is the question mark (
?), which stands for one character. For example,
mv ?.txt shorttextfiles/ will move all files named with a single character followed by
.txt from the current directory to directory
??.txt would match all files whose name consists of 2 characters followed by
In addition to matching filenames, globs are also used widely for matching arbitrary strings (wildcard matching). In this capacity a common interface is
The glob command, short for global, originates in the earliest versions of Bell Labs' Unix. The command interpreters of the early versions of Unix (1st through 6th Editions, 1969–1975) relied on a separate program to expand wildcard characters in unquoted arguments to a command: /etc/glob. That program performed the expansion and supplied the expanded list of file paths to the command for execution.
Glob was originally written in the B programming language. It was the first piece of mainline Unix software to be developed in a high-level programming language. Later, this functionality was provided as a C library function,
glob(), used by programs such as the shell. It is usually defined based on a function named
fnmatch(), which tests for whether a string matches a given pattern - the program using this function can then iterate through a series of strings (usually filenames) to determine which ones match. Both functions are a part of POSIX: the functions defined in POSIX.1 since 2001, and the syntax defined in POSIX.2. The idea of defining a separate match function started with wildmat (wildcard match), a simple library to match strings against Bourne Shell globs.
Traditionally, globs do not match hidden files in the form of Unix dotfiles; to match them the pattern must explicitly start with
.. For example,
* matches all visible files while
.* matches all hidden files.
The most common wildcards are
|Wildcard||Description||Example||Matches||Does not match|
||matches any number of any characters including none||
||matches any single character||
||matches one character given in the bracket||
||matches one character from the (locale-dependent) range given in the bracket||
|Wildcard||Description||Example||Matches||Does not match|
||matches one character that is not given in the bracket||
||matches one character that is not from the range given in the bracket||
The ranges are also allowed to include pre-defined character classes, equivalence classes for accented characters, and collation symbols for hard-to-type characters. They are defined to match up with the brackets in POSIX regular expressions.
Unix globbing is handled by the shell per POSIX tradition. Globbing is provided on filenames at the command line and in shell scripts. The POSIX-mandated
case statement in shells provides pattern-matching using glob patterns.
Some shells (such as the C shell and Bash) support additional syntax known as alternation or brace expansion. Because it is not part of the glob syntax, it is not provided in
case. It is only expanded on the command line before globbing.
The Bash shell also supports the following extensions:
- Extended globbing (extglob): allows other pattern matching operators to be used to match multiple occurrences of a pattern enclosed in parentheses, essentially providing the missing kleene star and alternation for describing regular languages. It can be enabled by setting the
extglobshell option. This option came from ksh93. The GNU fnmatch and glob has an identical extension.
- globstar: allows
**on its own as a name component to recursively match any number of layers of non-hidden directories. Also supported by the JS libraries and Python's glob.
Windows and DOS
The original DOS was a clone of CP/M designed to work on Intel's 8088 and 8086 processors. Windows shells, following DOS, do not traditionally perform any glob expansion in arguments passed to external programs. Shells may use an expansion for their own builtin commands:
- Windows PowerShell has all the common syntax defined as stated above without any additions.
- COMMAND.COM and cmd.exe have most of the common syntax with some limitations: There is no
[…]and for COMMAND.COM the
*may only appear at the end of the pattern. It can not appear in the middle of a pattern, except immediately preceding the filename extension separator dot.
Windows and DOS programs receive a long command-line string instead of argv-style parameters, and it is their responsibility to perform any splitting, quoting, or glob expansion. There is technically no fixed way of describing wildcards in programs since they are free to do what they wish. Two common glob expanders include:
- The Microsoft C Runtime (msvcrt) command-line expander, which only supports
*. Both ReactOS (crt/misc/getargs.c) and Wine (msvcrt/data.c) contain a compatible open-source implementation of
__getmainargs, the function operating under-the-hood, in their core CRT.
- The Cygwin and MSYS
dcrt0.cccommand-line expander, which uses the unix-style
glob()routine under-the-hood, after splitting the arguments.
Most other parts of Windows, including the Indexing Service, use the MS-DOS style of wildcards found in CMD. A relic of the 8.3 filename age, this syntax pays special attention to dots in the pattern and the text (filename). Internally this is done using three extra wildcard characters,
<>". On the Windows API end, the glob() equivalent is FindFirstFile, and fnmatch() corresponds to its underlying RtlIsNameInExpression. (Another fnmatch analogue is PathMatchSpec.) Both open-source msvcrt expanders use FindFirstFile, so 8.3 filename quirks will also apply in them.
LIKE operator has an equivalent to
* but not
|Common wildcard||SQL wildcard||Description|
||matches any single character|
||matches any number of any characters including none|
Standard SQL uses a glob-like syntax for simple string matching in its
LIKE operator, although the term "glob" is not generally used in the SQL community. The percent sign (
%) matches zero or more characters and the underscore (
_) matches exactly one.
Many implementations of SQL have extended the
LIKE operator to allow a richer pattern-matching language, incorporating character ranges (
[…]), their negation, and elements of regular expressions.
Compared to regular expressions
Globs do not include syntax for the Kleene star which allows multiple repetitions of the preceding part of the expression; thus they are not considered regular expressions, which can describe the full set of regular languages over any given finite alphabet.
|Common wildcard||Equivalent regular expression|
Globs attempt to match the entire string (for example,
S*.DOC matches S.DOC and SA.DOC, but not POST.DOC or SURREY.DOCKS), whereas, depending on implementation details, regular expressions may match a substring.
Implementing as regular expressions
The original Mozilla proxy auto-config implementation, which provides a glob-matching function on strings, uses a replace-as-RegExp implementation as above. The bracket syntax happens to be covered by regex in such an example.
Python's fnmatch uses a more elaborate procedure to transform the pattern into a regular expression.
Beyond their uses in shells, globs patterns also find use in a variety of programming languages, mainly to process human input. A glob-style interface for returning files or an fnmatch-style interface for matching strings are found in the following programming languages:
- C# has multiple libraries available through NuGet such as
- D has a
globMatchfunction in the
minimatchwhich is used internally by npm, and
micromatch, a purportedly more optimized, accurate and safer globbing implementation used by Babel and yarn.
- Go has a
Globfunction in the
- Java has a
Filesclass containing methods that operate on glob patterns.
- Haskell has a
Globpackage with the main module
System.FilePath.Glob. The pattern syntax is based on a subset of Zsh's. It tries to optimize the given pattern and should be noticeably faster than a naïve character-by-character matcher.
- Perl has both a
globfunction (as discussed in Larry Wall's book Programming Perl) and a Glob extension which mimics the BSD glob routine. Perl's angle brackets can be used to glob as well:
- PHP has a
- Python has a
globmodule in the standard library which performs wildcard pattern matching on filenames, and an
fnmatchmodule with functions for matching strings or filtering lists based on these same wildcard patterns. Guido van Rossum, author of the Python programming language, wrote and contributed a
globroutine to BSD Unix in 1986. There were previous implementations of
glob, e.g., in the ex and ftp programs in previous releases of BSD.
- Ruby has a
globmethod for the
Dirclass which performs wildcard pattern matching on filenames. Several libraries such as Rant and Rake provide a
FileListclass which has a glob method or use the method
- Rust has multiple libraries that can match glob patterns.
- SQLite has a
- Tcl contains a globbing facility.
- "First Edition Unix manual 'Miscellaneous' section (PDF)" (PDF). Archived from the original (PDF) on 2000-08-29. Retrieved 2011-05-11.
- McIlroy, M. D. (1987). A Research Unix reader: annotated excerpts from the Programmer's Manual, 1971–1986 (PDF) (Technical report). CSTR. Bell Labs. 139.
- Linux Programmer's Manual – Library Functions –
- Linux Programmer's Manual – Library Functions –
- [https://www.gnu.org/software/bash/manual/bash.html#Pattern-Matching Bash Reference Manual
- "The Open Group Base Specifications Issue 7 IEEE Std 1003.1, 2013 Edition, 2.13. Pattern Matching Notation".
- "Linux Programmer's Manual, GLOB(7)".
- The "Advanced Bash-Scripting Guide, Chapter 19.2: Globbing" (Mendel Cooper, 2003) has a concise set of examples of filename globbing patterns.
- "Bash globs". greg's bash knowledgebase. Retrieved 2019-11-25.
- "Pattern Matching". Bash Reference Manual.
- "Supporting Wildcard Characters in Cmdlet Parameters". Microsoft. Microsoft Developer Network.
- "Wildcard Expansion". Microsoft Developer Network. 2013.
- "Wildcard Expansion". docs.microsoft.com.
- Wildcards in Windows. MSDN Devblog.
- "LIKE (Transact-SQL)".
- Hopcroft, John E.; Motwani, Rajeev; Ullman, Jeffrey D. (2000). Introduction to Automata Theory, Languages, and Computation (2nd ed.). Addison-Wesley.
- "Lib/fnmatch.py". Python. 2021-01-20. Retrieved 2021-11-10.
- "kthompson/glob". GitHub. Retrieved 2020-11-06.
- "dazinator/dotnet.glob". GitHub. Retrieved 2022-06-22.
- "std.path - D Programming Language - Digital Mars". dlang.org. Retrieved 2014-09-08.
- "isaacs/minimatch". GitHub. Retrieved 2016-08-10.
- "jonschlinkert/micromatch". GitHub. Retrieved 2017-04-04.
- "Package filepath - The Go Programming Language". Golang.org. Retrieved 2011-05-11.
- "File Operations". Oracle. Retrieved 2013-12-16.
- "Glob-0.7.4: Globbing library". Retrieved 2014-05-07.
- "File::Glob - Perl extension for BSD glob routine". perldoc.perl.org. Retrieved 2011-05-11.
- "glob - Manual". PHP. 2011-05-06. Retrieved 2011-05-11.
- "10.7. glob — Unix style pathname pattern expansion — Python v2.7.1 documentation". Docs.python.org. Retrieved 2011-05-11.
- "'Globbing' library routine". Archived from the original on 2007-12-19. Retrieved 2011-05-11.
- "Class: Dir". Ruby-doc.org. Retrieved 2011-05-11.
- "#glob - Lib.rs". lib.rs. Retrieved 2021-11-12.
- "TCL glob manual page". Retrieved 2011-11-16.