glob(7)

๐Ÿฆ‹ NAME ๐Ÿฆ‹

glob โ€” globbing pathnames ๐Ÿ’… welcome to the glob(7) page, bestie, straight outta the Miscellaneous Information Manual and into ur heart ๐Ÿซถ


๐ŸŒธ DESCRIPTION ๐ŸŒธ

okay so storytime โœจ Long ago, in UNIX V6, there was a program /etc/glob that would expand wildcard patterns. Soon afterward this became a shell built-in. iconic behavior honestly ๐Ÿ‘‘

These days there is also a library routine glob(3) that will perform this function for a user program. so if ur writing C, she's right there for u ๐Ÿ’–

The rules are as follows (POSIX.2, 3.13). no cap, this is the whole syllabus ๐Ÿ“š

โœจ Wildcard matching โœจ

A string is a wildcard pattern if it contains one of the characters ?, *, or [. Globbing is the operation that expands a wildcard pattern into the list of pathnames matching the pattern. Matching is defined by:

A ? (not between brackets) matches any single character. exactly one, no more no less, she's picky ๐Ÿ’…

A * (not between brackets) matches any string, including the empty string. yes even nothing. the empty string counts. generous queen ๐ŸŒˆ

๐ŸŽ€ Character classes ๐ŸŽ€

An expression [...] where the first character after the leading [ is not an ! matches a single character, namely any of the characters enclosed by the brackets. The string enclosed by the brackets cannot be empty; therefore ] can be allowed between the brackets, provided that it is the first character. (Thus, [][!] matches the three characters [, ], and !.) yes that's a lot of brackets, breathe, it's fine ๐Ÿ˜ญ

๐Ÿ“ Ranges ๐Ÿ“

There is one special convention: two characters separated by - denote a range. (Thus, [A-Fa-f0-9] is equivalent to [ABCDEFabcdef0123456789].) One may include - in its literal meaning by making it the first or last character between the brackets. (Thus, []-] matches just the two characters ] and -, and [--0] matches the three characters -, ., and 0, since / cannot be matched.) put the dash at the ends if u want her to chill and be literal, periodt โœจ

๐Ÿฆ‹ Complementation ๐Ÿฆ‹

An expression [!...] matches a single character, namely any character that is not matched by the expression obtained by removing the first ! from it. (Thus, [!]a-] matches any single character except ], a, and -.) it's giving "everyone EXCEPT these guys" energy ๐Ÿ’€

One can remove the special meaning of ?, *, and [ by preceding them by a backslash, or, in case this is part of a shell command line, enclosing them in quotes. Between brackets these characters stand for themselves. Thus, [[?*\] matches the four characters [, ?, *, and \. the backslash is ur escape hatch bestie, don't sleep on it ๐Ÿ™ˆ

๐ŸŒˆ Pathnames ๐ŸŒˆ

Globbing is applied on each of the components of a pathname separately. A / in a pathname cannot be matched by a ? or * wildcard, or by a range like [.-0]. A range containing an explicit / character is syntactically incorrect. (POSIX requires that syntactically incorrect patterns are left unchanged.)

If a filename starts with a ., this character must be matched explicitly. (Thus, rm * will not remove .profile, and tar c * will not archive all your files; tar c . is better.) so if ur files are mysteriously missing from ur glob, check for a leading dot, that's the vibe check u failed ๐Ÿ”ฅ

๐Ÿ’œ Empty lists ๐Ÿ’œ

The nice and simple rule given above: "expand a wildcard pattern into the list of matching pathnames" was the original UNIX definition. It allowed one to have patterns that expand into an empty list, as in

xv -wait 0 *.gif *.jpg

where perhaps no *.gif files are present (and this is not an error). However, POSIX requires that a wildcard pattern is left unchanged when it is syntactically incorrect, or the list of matching pathnames is empty. With bash one can force the classical behavior using this command:

shopt -s nullglob

(Similar problems occur elsewhere. For example, where old scripts have

rm `find . -name "*~"`

new scripts require

rm -f nosuchfile `find . -name "*~"`

to avoid error messages from rm called with an empty argument list.)

โš ๏ธ main character warning: an empty list is NOT an error in the classical behaviour, but POSIX says leave the pattern alone if nothing matches or it's syntactically incorrect. know which one ur shell is doing or u WILL be confused at 3am ๐Ÿ˜ญ

๐ŸŒŸ NOTES ๐ŸŒŸ

๐Ÿงš Regular expressions ๐Ÿงš

Note that wildcard patterns are not regular expressions, although they are a bit similar. First of all, they match filenames, rather than text, and secondly, the conventions are not the same: for example, in a regular expression * means zero or more copies of the preceding thing. two totally different girls, do not mix them up bestie ๐Ÿ’…

Now that regular expressions have bracket expressions where the negation is indicated by a ^, POSIX has declared the effect of a wildcard pattern [^...] to be undefined. undefined fr fr, so don't go relying on it ๐Ÿ˜ฌ

๐ŸŒ Character classes and internationalization ๐ŸŒ

Of course ranges were originally meant to be ASCII ranges, so that [ -%] stands for [ !"#$%] and [a-z] stands for "any lowercase letter". Some UNIX implementations generalized this so that a range X-Y stands for the set of characters with code between the codes for X and for Y. However, this requires the user to know the character coding in use on the local system, and moreover, is not convenient if the collating sequence for the local alphabet differs from the ordering of the character codes. Therefore, POSIX extended the bracket notation greatly, both for wildcard patterns and for regular expressions. In the above we saw three types of items that can occur in a bracket expression: namely (i) the negation, (ii) explicit single characters, and (iii) ranges. POSIX specifies ranges in an internationally more useful way and adds three more types:

  • (iii) Ranges X-Y comprise all characters that fall between X and Y (inclusive) in the current collating sequence as defined by the LC_COLLATE category in the current locale. ๐ŸŒ
  • (iv) Named character classes, like
[:alnum:]  [:alpha:]  [:blank:]  [:cntrl:]
[:digit:]  [:graph:]  [:lower:]  [:print:]
[:punct:]  [:space:]  [:upper:]  [:xdigit:]

so that one can say [[:lower:]] instead of [a-z], and have things work in Denmark, too, where there are three letters past z in the alphabet. These character classes are defined by the LC_CTYPE category in the current locale. she's international, she's multilingual, she ate ๐ŸŒ๐Ÿ’–

  • (v) Collating symbols, like [.ch.] or [.a-acute.], where the string between [. and .] is a collating element defined for the current locale. Note that this may be a multicharacter element. yes, MULTI. character. element. she's not like other elements ๐Ÿ˜Œ
  • (vi) Equivalence class expressions, like [=a=], where the string between [= and =] is any collating element from its equivalence class, as defined for the current locale. For example, [[=a=]] might be equivalent to [aรกร รครข], that is, to [a[.a-acute.][.a-grave.][.a-umlaut.][.a-circumflex.]]. look at her go, all those accents living their best life together ๐ŸŽ€

๐Ÿ‘‘ SEE ALSO ๐Ÿ‘‘

sh(1), fnmatch(3), glob(3), locale(7), regex(7) โ€” go read the whole friend group, they're all iconic ๐Ÿซถ


and that's the whole page bestie!! โœจ this was glob(7) from Linux man-pages 6.20, dated 2026-02-08 ๐Ÿ’– now go forth and glob responsibly, u absolute legend ๐Ÿฆ‹๐ŸŒธ๐Ÿ’…

๐Ÿ“ฆ where this page comes from
  • arch rolling: man-pages 6.20-1 ยท BSD-2-Clause AND BSD-3-Clause AND BSD-4.3TAHOE AND BSD-4-Clause-UC AND GPL-1.0-or-later AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-3.0-linking-exception AND LGPL-3.0-or-later AND LicenseRef-Public-Domain AND LicenseRef-UltraPermissive AND Linux-man-pages-1-para AND Linux-man-pages-copyleft AND Linux-man-pages-copyleft-2-para AND Linux-man-pages-copyleft-var AND MIT AND Spencer-94
  • nixpkgs unstable: man-pages 6.20
  • ๐Ÿ“œ the page's license: GPL-2.0-or-later
  • ๐Ÿ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms