filepattern: File path glob-like matching

[ bsd3, development, filepath, library ] [ Propose Tags ]

A library for matching files using patterns such as "src/**/*.png" for all .png files recursively under the src directory. Features:

Originally taken from the Shake library.

[Skip to Readme]
Versions [faq] 0.1, 0.1.1, 0.1.2
Change log CHANGES.txt
Dependencies base (==4.*), directory, extra (>=1.6.2), filepath, semigroups (>=0.18) [details]
License BSD-3-Clause
Copyright Neil Mitchell 2011-2020
Author Neil Mitchell <>, Evan Rutledge Borden <>
Maintainer Neil Mitchell <>
Category Development, FilePath
Home page
Bug tracker
Source repo head: git clone
Uploaded by NeilMitchell at 2020-02-26T21:11:57Z
Distributions Arch:0.1.2, Fedora:0.1.2, LTSHaskell:0.1.1, NixOS:0.1.2, Stackage:0.1.1, openSUSE:0.1.2
Downloads 7431 total (441 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs available [build log]
Last success reported on 2020-02-26 [all 1 reports]


[Index] [Quick Jump]


Maintainer's Corner

For package maintainers and hackage trustees

Readme for filepattern-0.1.2

[back to package description]

FilePattern Hackage version Stackage version Linux build status Windows build status

A library for matching files using patterns such as src/**/*.png for all .png files recursively under the src directory. There are two special forms:

  • * matches part of a path component, excluding any separators.
  • ** as a path component matches an arbitrary number of path components.

Some examples:

  • test.c matches test.c and nothing else.
  • *.c matches all .c files in the current directory, so file.c matches, but file.h and dir/file.c don't.
  • **/*.c matches all .c files anywhere on the filesystem, so file.c, dir/file.c, dir1/dir2/file.c and /path/to/file.c all match, but file.h and dir/file.h don't.
  • dir/*/* matches all files one level below dir, so dir/one/file.c and dir/two/file.h match, but file.c, one/dir/file.c, dir/file.h and dir/one/two/file.c don't.

More complete semantics are given in the documentation for the matching function ?==.


  • All matching is O(n). Most functions precompute some information given only one argument. There are also functions to provide bulk matching of many patterns against many paths simultaneously, see step and matchMany.
  • You can obtain the parts that matched the * and ** special forms using match, and substitute them into other patterns using substitute.
  • You can search for files using a minimal number of IO operations, using the System.FilePattern.Directory module.

Related work

  • Another Haskell file pattern matching library is Glob, which aims to be closer to the POSIX glob() function, with forms such as *, ?, **/ (somewhat different to the filepattern equivalent) and [:alpha:]. A complete guide is in the documentation. Compared to filepattern, the Glob library is closer to a regular expression library - definitely more powerful, potentially harder to use.
  • The shake library has contained a FilePattern type since the beginning. This library evolved from that code, with significant improvements.
  • The semantics are heavily inspired by VS Code, Git and the NPM package Glob.