Awesome
<div align="center"> <h1> <code>bfs</code> <br clear="all"> <a href="https://github.com/tavianator/bfs/releases"><img src="https://img.shields.io/github/v/tag/tavianator/bfs?label=version" alt="Version" align="left"></a> <a href="/LICENSE"><img src="https://img.shields.io/badge/license-0BSD-blue.svg" alt="License" align="left"></a> <a href="https://github.com/tavianator/bfs/actions/workflows/ci.yml"><img src="https://github.com/tavianator/bfs/actions/workflows/ci.yml/badge.svg" alt="CI Status" align="right"></a> <a href="https://codecov.io/gh/tavianator/bfs"><img src="https://img.shields.io/codecov/c/github/tavianator/bfs?token=PpBVuozOVC" alt="Code coverage" align="right"/></a> </h1>Features • Installation • Usage • Building • Contributing • Changelog
<picture> <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/tavianator/bfs/gh-pages/animation-dark.svg"> <source media="(prefers-color-scheme: light)" srcset="https://raw.githubusercontent.com/tavianator/bfs/gh-pages/animation-light.svg"> <img alt="Screencast" src="https://raw.githubusercontent.com/tavianator/bfs/gh-pages/animation-light.svg"> </picture> <p></p> </div>bfs is a variant of the UNIX find command that operates breadth-first rather than depth-first.
It is otherwise compatible with many versions of find, including
POSIX • GNU • FreeBSD • OpenBSD • NetBSD • macOS
</div>If you're not familiar with find, the GNU find manual provides a good introduction.
Features
<details> <summary> <code>bfs</code> operates breadth-first, which typically finds the file(s) you're looking for faster. </summary> <p></p>Imagine the following directory tree:
<pre> haystack ├── deep │ └── 1 │ └── 2 │ └── 3 │ └── 4 │ └── ... └── shallow └── <strong>needle</strong> </pre>find will explore the entire deep directory tree before it ever gets to the shallow one that contains what you're looking for.
On the other hand, bfs lists files from shallowest to deepest, so you never have to wait for it to explore an entire unrelated subtree.
$ bfs haystack
haystack
haystack/deep
haystack/shallow
haystack/deep/1
haystack/shallow/needle
...
$ find haystack
haystack
haystack/deep
haystack/deep/1
haystack/deep/1/2
haystack/deep/1/2/3
haystack/deep/1/2/3/4
...
haystack/shallow
haystack/shallow/needle
For example, bfs is less picky about where you put its arguments:
$ bfs -L -name 'needle' haystack
haystack/needle
$ bfs haystack -L -name 'needle'
haystack/needle
$ bfs -L haystack -name 'needle'
haystack/needle
$ find -L -name 'needle' haystack
find: paths must precede expression: haystack
$ find haystack -L -name 'needle'
find: unknown predicate `-L'
$ find -L haystack -name 'needle'
haystack/needle
For example, bfs will detect and suggest corrections for typos:
$ bfs -nam needle
bfs: error: bfs -nam needle
bfs: error: ~~~~
bfs: error: Unknown argument; did you mean -name?
bfs also includes a powerful static analysis to help catch mistakes:
$ bfs -print -name 'needle'
bfs: warning: bfs -print -name needle
bfs: warning: ~~~~~~~~~~~~
bfs: warning: The result of this expression is ignored.
For example, the -exclude operator skips over entire subtrees whenever an expression matches.
-exclude is both more powerful and easier to use than the standard -prune action; compare
to the equivalent
<pre> $ find <strong>! \( -name .git -prune \)</strong> -name config </pre>As an additional shorthand, -nohidden skips over all hidden files and directories.
See the usage documentation for more about the extensions provided by bfs.
Installation
<details open> <summary> <code>bfs</code> may already be packaged for your operating system. </summary> <p></p> <table> <tbody> <tr><th>Linux</th><th>macOS</th></tr> <tr> <td width="506" valign="top" rowspan="3"> <pre> <strong><a href="https://pkgs.alpinelinux.org/packages?name=bfs">Alpine Linux</a></strong> # apk add bfs <strong><a href="https://archlinux.org/packages/extra/x86_64/bfs/">Arch Linux</a></strong> # pacman -S bfs <strong><a href="https://packages.debian.org/sid/bfs">Debian</a>/<a href="https://packages.ubuntu.com/kinetic/bfs">Ubuntu</a></strong> # apt install bfs <strong><a href="https://src.fedoraproject.org/rpms/bfs">Fedora Linux</a></strong> # dnf install bfs <strong><a href="https://packages.gentoo.org/packages/sys-apps/bfs">Gentoo</a></strong> # emerge sys-apps/bfs <strong><a href="https://packages.guix.gnu.org/packages/bfs/">GNU Guix</a></strong> # guix install bfs <strong><a href="https://search.nixos.org/packages?channel=unstable&show=bfs&from=0&size=1&sort=relevance&type=packages&query=bfs">NixOS</a></strong> # nix-env -i bfs <strong><a href="https://voidlinux.org/packages/?arch=x86_64&q=bfs">Void Linux</a></strong> # xbps-install -S bfs </pre> </td> <td width="506" valign="top"> <pre> <strong><a href="https://formulae.brew.sh/formula/bfs">Homebrew</a></strong> $ brew install bfs <strong><a href="https://ports.macports.org/port/bfs/">MacPorts</a></strong> # port install bfs </pre> </td> </tr> <tr><th height="1">BSD</th></tr> <tr> <td width="506" valign="top"> <pre> <strong><a href="https://www.freshports.org/sysutils/bfs">FreeBSD</a></strong> # pkg install bfs <strong><a href="https://openports.pl/path/sysutils/bfs">OpenBSD</a></strong> # pkg_add bfs </pre> </td> </tr> </tbody> </table> </details> <details> <summary> To build <code>bfs</code> from source, you may need to install some dependencies. </summary> <p></p>The only absolute requirements for building bfs are a C compiler, GNU make, and Bash.
These are installed by default on many systems, and easy to install on most others.
Refer to your operating system's documentation on building software.
bfs also depends on some system libraries for some of its features.
Here's how to install them on some common platforms:
These dependencies are technically optional, though strongly recommended. See the build documentation for how to disable them.
</details> <details> <summary> Once you have the dependencies, you can build <code>bfs</code>. </summary> <p></p>Download one of the releases or clone the git repo. Then run
$ ./configure
$ make
This will build the ./bin/bfs binary.
Run the test suite to make sure it works correctly:
$ make check
If you're interested in speed, you may want to build the release version instead:
$ ./configure --enable-release
$ make
Finally, if you want to install it globally, run
# make install