ripgrep recursively searches directories for a regex pattern while respecting your gitignore

Andrew Gallant

Last update: Jan 2, 2023

Related tags

Static Code Auditing gitignore search cli command-line regex recursively-search command-line-tool grep ripgrep

Overview

ripgrep (rg)

ripgrep is a line-oriented search tool that recursively searches the current directory for a regex pattern. By default, ripgrep will respect gitignore rules and automatically skip hidden files/directories and binary files. ripgrep has first class support on Windows, macOS and Linux, with binary downloads available for every release. ripgrep is similar to other popular search tools like The Silver Searcher, ack and grep.

Dual-licensed under MIT or the UNLICENSE.

CHANGELOG

Please see the CHANGELOG for a release history.

Documentation quick links

Screenshot of search results

Quick examples comparing tools

This example searches the entire Linux kernel source tree (after running make defconfig && make -j8) for [A-Z]+_SUSPEND, where all matches must be words. Timings were collected on a system with an Intel i7-6900K 3.2 GHz.

Please remember that a single benchmark is never enough! See my blog post on ripgrep for a very detailed comparison with more benchmarks and analysis.

Tool	Command	Line count	Time
ripgrep (Unicode)	`rg -n -w '[A-Z]+_SUSPEND'`	452	0.136s
git grep	`git grep -P -n -w '[A-Z]+_SUSPEND'`	452	0.348s
ugrep (Unicode)	`ugrep -r --ignore-files --no-hidden -I -w '[A-Z]+_SUSPEND'`	452	0.506s
The Silver Searcher	`ag -w '[A-Z]+_SUSPEND'`	452	0.654s
git grep	`LC_ALL=C git grep -E -n -w '[A-Z]+_SUSPEND'`	452	1.150s
ack	`ack -w '[A-Z]+_SUSPEND'`	452	4.054s
git grep (Unicode)	`LC_ALL=en_US.UTF-8 git grep -E -n -w '[A-Z]+_SUSPEND'`	452	4.205s

Here's another benchmark on the same corpus as above that disregards gitignore files and searches with a whitelist instead. The corpus is the same as in the previous benchmark, and the flags passed to each command ensure that they are doing equivalent work:

Tool	Command	Line count	Time
ripgrep	`rg -uuu -tc -n -w '[A-Z]+_SUSPEND'`	388	0.096s
ugrep	`ugrep -r -n --include='.c' --include='.h' -w '[A-Z]+_SUSPEND'`	388	0.493s
GNU grep	`egrep -r -n --include='.c' --include='.h' -w '[A-Z]+_SUSPEND'`	388	0.806s

And finally, a straight-up comparison between ripgrep, ugrep and GNU grep on a single large file cached in memory (~13GB, OpenSubtitles.raw.en.gz):

Tool	Command	Line count	Time
ripgrep	`rg -w 'Sherlock [A-Z]\w+'`	7882	2.769s
ugrep	`ugrep -w 'Sherlock [A-Z]\w+'`	7882	6.802s
GNU grep	`LC_ALL=en_US.UTF-8 egrep -w 'Sherlock [A-Z]\w+'`	7882	9.027s

In the above benchmark, passing the -n flag (for showing line numbers) increases the times to 3.423s for ripgrep and 13.031s for GNU grep. ugrep times are unaffected by the presence or absence of -n.

Why should I use ripgrep?

It can replace many use cases served by other search tools because it contains most of their features and is generally faster. (See the FAQ for more details on whether ripgrep can truly replace grep.)
Like other tools specialized to code search, ripgrep defaults to recursive directory search and won't search files ignored by your .gitignore/.ignore/.rgignore files. It also ignores hidden and binary files by default. ripgrep also implements full support for .gitignore, whereas there are many bugs related to that functionality in other code search tools claiming to provide the same functionality.
ripgrep can search specific types of files. For example, rg -tpy foo limits your search to Python files and rg -Tjs foo excludes JavaScript files from your search. ripgrep can be taught about new file types with custom matching rules.
ripgrep supports many features found in grep, such as showing the context of search results, searching multiple patterns, highlighting matches with color and full Unicode support. Unlike GNU grep, ripgrep stays fast while supporting Unicode (which is always on).
ripgrep has optional support for switching its regex engine to use PCRE2. Among other things, this makes it possible to use look-around and backreferences in your patterns, which are not supported in ripgrep's default regex engine. PCRE2 support can be enabled with -P/--pcre2 (use PCRE2 always) or --auto-hybrid-regex (use PCRE2 only if needed). An alternative syntax is provided via the --engine (default|pcre2|auto-hybrid) option.
ripgrep supports searching files in text encodings other than UTF-8, such as UTF-16, latin-1, GBK, EUC-JP, Shift_JIS and more. (Some support for automatically detecting UTF-16 is provided. Other text encodings must be specifically specified with the -E/--encoding flag.)
ripgrep supports searching files compressed in a common format (brotli, bzip2, gzip, lz4, lzma, xz, or zstandard) with the -z/--search-zip flag.
ripgrep supports arbitrary input preprocessing filters which could be PDF text extraction, less supported decompression, decrypting, automatic encoding detection and so on.

In other words, use ripgrep if you like speed, filtering by default, fewer bugs and Unicode support.

Why shouldn't I use ripgrep?

Despite initially not wanting to add every feature under the sun to ripgrep, over time, ripgrep has grown support for most features found in other file searching tools. This includes searching for results spanning across multiple lines, and opt-in support for PCRE2, which provides look-around and backreference support.

At this point, the primary reasons not to use ripgrep probably consist of one or more of the following:

You need a portable and ubiquitous tool. While ripgrep works on Windows, macOS and Linux, it is not ubiquitous and it does not conform to any standard such as POSIX. The best tool for this job is good old grep.
There still exists some other feature (or bug) not listed in this README that you rely on that's in another tool that isn't in ripgrep.
There is a performance edge case where ripgrep doesn't do well where another tool does do well. (Please file a bug report!)
ripgrep isn't possible to install on your machine or isn't available for your platform. (Please file a bug report!)

Is it really faster than everything else?

Generally, yes. A large number of benchmarks with detailed analysis for each is available on my blog.

Summarizing, ripgrep is fast because:

It is built on top of Rust's regex engine. Rust's regex engine uses finite automata, SIMD and aggressive literal optimizations to make searching very fast. (PCRE2 support can be opted into with the -P/--pcre2 flag.)
Rust's regex library maintains performance with full Unicode support by building UTF-8 decoding directly into its deterministic finite automaton engine.
It supports searching with either memory maps or by searching incrementally with an intermediate buffer. The former is better for single files and the latter is better for large directories. ripgrep chooses the best searching strategy for you automatically.
Applies your ignore patterns in .gitignore files using a RegexSet. That means a single file path can be matched against multiple glob patterns simultaneously.
It uses a lock-free parallel recursive directory iterator, courtesy of crossbeam and ignore.

Feature comparison

Andy Lester, author of ack, has published an excellent table comparing the features of ack, ag, git-grep, GNU grep and ripgrep: https://beyondgrep.com/feature-comparison/

Note that ripgrep has grown a few significant new features recently that are not yet present in Andy's table. This includes, but is not limited to, configuration files, passthru, support for searching compressed files, multiline search and opt-in fancy regex support via PCRE2.

Installation

The binary name for ripgrep is rg.

Archives of precompiled binaries for ripgrep are available for Windows, macOS and Linux. Linux and Windows binaries are static executables. Users of platforms not explicitly mentioned below are advised to download one of these archives.

If you're a macOS Homebrew or a Linuxbrew user, then you can install ripgrep from homebrew-core:

$ brew install ripgrep

If you're a MacPorts user, then you can install ripgrep from the official ports:

$ sudo port install ripgrep

If you're a Windows Chocolatey user, then you can install ripgrep from the official repo:

$ choco install ripgrep

If you're a Windows Scoop user, then you can install ripgrep from the official bucket:

$ scoop install ripgrep

If you're an Arch Linux user, then you can install ripgrep from the official repos:

$ pacman -S ripgrep

If you're a Gentoo user, you can install ripgrep from the official repo:

$ emerge sys-apps/ripgrep

If you're a Fedora user, you can install ripgrep from official repositories.

$ sudo dnf install ripgrep

If you're an openSUSE user, ripgrep is included in openSUSE Tumbleweed and openSUSE Leap since 15.1.

$ sudo zypper install ripgrep

If you're a RHEL/CentOS 7/8 user, you can install ripgrep from copr:

$ sudo yum-config-manager --add-repo=https://copr.fedorainfracloud.org/coprs/carlwgeorge/ripgrep/repo/epel-7/carlwgeorge-ripgrep-epel-7.repo
$ sudo yum install ripgrep

If you're a Nix user, you can install ripgrep from nixpkgs:

$ nix-env --install ripgrep
$ # (Or using the attribute name, which is also ripgrep.)

If you're a Debian user (or a user of a Debian derivative like Ubuntu), then ripgrep can be installed using a binary .deb file provided in each ripgrep release.

$ curl -LO https://github.com/BurntSushi/ripgrep/releases/download/12.1.1/ripgrep_12.1.1_amd64.deb
$ sudo dpkg -i ripgrep_12.1.1_amd64.deb

If you run Debian Buster (currently Debian stable) or Debian sid, ripgrep is officially maintained by Debian.

$ sudo apt-get install ripgrep

If you're an Ubuntu Cosmic (18.10) (or newer) user, ripgrep is available using the same packaging as Debian:

$ sudo apt-get install ripgrep

(N.B. Various snaps for ripgrep on Ubuntu are also available, but none of them seem to work right and generate a number of very strange bug reports that I don't know how to fix and don't have the time to fix. Therefore, it is no longer a recommended installation option.)

If you're a FreeBSD user, then you can install ripgrep from the official ports:

# pkg install ripgrep

If you're an OpenBSD user, then you can install ripgrep from the official ports:

$ doas pkg_add ripgrep

If you're a NetBSD user, then you can install ripgrep from pkgsrc:

# pkgin install ripgrep

If you're a Haiku x86_64 user, then you can install ripgrep from the official ports:

$ pkgman install ripgrep

If you're a Haiku x86_gcc2 user, then you can install ripgrep from the same port as Haiku x86_64 using the x86 secondary architecture build:

$ pkgman install ripgrep_x86

If you're a Rust programmer, ripgrep can be installed with cargo.

Note that the minimum supported version of Rust for ripgrep is 1.34.0, although ripgrep may work with older versions.
Note that the binary may be bigger than expected because it contains debug symbols. This is intentional. To remove debug symbols and therefore reduce the file size, run strip on the binary.

$ cargo install ripgrep

Building

ripgrep is written in Rust, so you'll need to grab a Rust installation in order to compile it. ripgrep compiles with Rust 1.34.0 (stable) or newer. In general, ripgrep tracks the latest stable release of the Rust compiler.

To build ripgrep:

$ git clone https://github.com/BurntSushi/ripgrep
$ cd ripgrep
$ cargo build --release
$ ./target/release/rg --version
0.1.3

If you have a Rust nightly compiler and a recent Intel CPU, then you can enable additional optional SIMD acceleration like so:

RUSTFLAGS="-C target-cpu=native" cargo build --release --features 'simd-accel'

The simd-accel feature enables SIMD support in certain ripgrep dependencies (responsible for transcoding). They are not necessary to get SIMD optimizations for search; those are enabled automatically. Hopefully, some day, the simd-accel feature will similarly become unnecessary. WARNING: Currently, enabling this option can increase compilation times dramatically.

Finally, optional PCRE2 support can be built with ripgrep by enabling the pcre2 feature:

$ cargo build --release --features 'pcre2'

(Tip: use --features 'pcre2 simd-accel' to also include compile time SIMD optimizations, which will only work with a nightly compiler.)

Enabling the PCRE2 feature works with a stable Rust compiler and will attempt to automatically find and link with your system's PCRE2 library via pkg-config. If one doesn't exist, then ripgrep will build PCRE2 from source using your system's C compiler and then statically link it into the final executable. Static linking can be forced even when there is an available PCRE2 system library by either building ripgrep with the MUSL target or by setting PCRE2_SYS_STATIC=1.

ripgrep can be built with the MUSL target on Linux by first installing the MUSL library on your system (consult your friendly neighborhood package manager). Then you just need to add MUSL support to your Rust toolchain and rebuild ripgrep, which yields a fully static executable:

$ rustup target add x86_64-unknown-linux-musl
$ cargo build --release --target x86_64-unknown-linux-musl

Applying the --features flag from above works as expected. If you want to build a static executable with MUSL and with PCRE2, then you will need to have musl-gcc installed, which might be in a separate package from the actual MUSL library, depending on your Linux distribution.

Running tests

ripgrep is relatively well-tested, including both unit tests and integration tests. To run the full test suite, use:

$ cargo test --all

from the repository root.

Vulnerability reporting

For reporting a security vulnerability, please contact Andrew Gallant, which has my email address and PGP public key if you wish to send an encrypted message.

Translations

The following is a list of known translations of ripgrep's documentation. These are unofficially maintained and may not be up to date.

Comments

add to package repositories

It'd be nice to at least get it into Ubuntu and homebrew. Sadly, I think either one of those will be quite difficult since Rust isn't packaged in either one of them.

The lowest hanging fruit is the Archlinux User Repository (AUR).

Fedora is getting Rust packaged soon, so that may be plausible.

Sadly, we may need to live with binaries distributed here for the time being.
enhancement

opened by BurntSushi 153
support searching across multiple lines
Say for example I'm trying to find instances of click that reside in a listeners block, like so:

listeners: { foo: ... click: .... }

According to the Rust regex docs, I should be able to do: rg '(?s)listeners.+click', but this doesn't seem to work. Does ripgrep not support multiline regex?
enhancement libripgrep
opened by isobit 103
Support persistent configuration (`.rgrc`?)

I'd love to keep different types for instance, and not have to specify --type-add each time.

My specific case is type zsh which searches zsh config files (.zshrc *.zsh, and some custom .zsh*).

Maybe it could support more stuff like no-heading, --heading etc as well, which would allow people to customize rg more.

(I know I can just alias rgzsh="rg --type-add 'zsh:*.zsh' --type-add 'zsh:.zshrc' --type zsh", but meh)

Loving the tool, btw!
question

opened by SimenB 91
Searching filenames (`-g` option in `ag`)

Ag supports using -g to recursively search filenames matching the provided pattern. Ripgrep doesn't have this feature (to the best of my knowledge; I've read the --help output three times looking for it); it's the only ag feature holding me back from fully switching to ripgrep. :)

Since ripgrep already has something unrelated mapped to -g, the option name should be something else. The incompatibility with ag will be unfortunate, but survivable.

opened by Valloric 61
maximum line length

I'd like ripgrep to have the ability to either hide or trim lines that are very long. Some lines take up my entire screen and are borderline useless to look at. It's possible that finding an intelligent way to shorten them would be best, since my guess is that the actual matched text is much smaller than the full line. However, this is harder to implement.

I don't think this should be enabled by default. It seems a little surprising for ripgrep to hide lines like that. In general, I like the work flow of, "run a search, see huge lines, confirm that I don't care about them and run ripgrep again with an option to hide them." It may however be plausible to enable this limit if results are being dumped to a terminal (we already enable colors, line numbers and file headings).
enhancement help wanted libripgrep

opened by BurntSushi 56
Add support for replace in files

One of the usecases that many people have is a simple search and replace in multiple files. Usually I achieve this functionality with xargs sed for example with ag -l 'hello' | xargs sed -i "s/hello/bye/g. Since rg contains the replace flag it will be nice to add support for this feature by replacing in the files directly.

This will be a nice addition after https://github.com/BurntSushi/ripgrep/issues/26

An example on how to do this with sed can be found in the comments here. https://github.com/BurntSushi/ripgrep/issues/74#issuecomment-376659557

opened by kfir-drivenets 53

Multiple testsuite failures on big-endian targets

The testsuite of ripgrep 0.10.0 is failing on all of Debian's big-endian targets:

failures:

---- feature::f34_only_matching_line_column stdout ----
thread 'feature::f34_only_matching_line_column' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sherlock:1:57:Sherlock
sherlock:3:49:Sherlock

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sherlock:1:57:Sherlock
sherlock:2:49:Sherlock

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/feature.rs:110:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::feature::f34_only_matching_line_column::{{closure}}
             at tests/feature.rs:110
   8: integration::feature::f34_only_matching_line_column
             at tests/macros.rs:7
   9: integration::feature::f34_only_matching_line_column::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- feature::f917_trim stdout ----
thread 'feature::f917_trim' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2-For the Doctor Watsons of this world, as opposed to the Sherlock
3:Holmeses, success in the province of detective work must always
4-be, to a very large extent, the result of luck. Sherlock Holmes
5-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2-For the Doctor Watsons of this world, as opposed to the Sherlock
2:Holmeses, success in the province of detective work must always
2-be, to a very large extent, the result of luck. Sherlock Holmes
2-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/feature.rs:591:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::feature::f917_trim::{{closure}}
             at tests/feature.rs:591
   8: integration::feature::f917_trim
             at tests/macros.rs:7
   9: integration::feature::f917_trim::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- feature::f917_trim_match stdout ----
thread 'feature::f917_trim_match' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2-For the Doctor Watsons of this world, as opposed to the Sherlock
3:Holmeses, success in the province of detective work must always
4-be, to a very large extent, the result of luck. Sherlock Holmes
5-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2-For the Doctor Watsons of this world, as opposed to the Sherlock
2:Holmeses, success in the province of detective work must always
2-be, to a very large extent, the result of luck. Sherlock Holmes
2-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/feature.rs:619:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::feature::f917_trim_match::{{closure}}
             at tests/feature.rs:619
   8: integration::feature::f917_trim_match
             at tests/macros.rs:7
   9: integration::feature::f917_trim_match::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- json::basic stdout ----
thread 'json::basic' panicked at 'assertion failed: `(left == right)`
  left: `Context { path: Some(Text { text: "sherlock" }), lines: Text { text: "Holmeses, success in the province of detective work must always\n" }, line_number: Some(1), absolute_offset: 65, submatches: [] }`,
 right: `Context { path: Some(Text { text: "sherlock" }), lines: Text { text: "Holmeses, success in the province of detective work must always\n" }, line_number: Some(2), absolute_offset: 65, submatches: [] }`', tests/json.rs:151:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::json::basic::{{closure}}
             at tests/json.rs:151
   8: integration::json::basic
             at tests/macros.rs:7
   9: integration::json::basic::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- misc::after_context_line_numbers stdout ----
thread 'misc::after_context_line_numbers' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
2-Holmeses, success in the province of detective work must always
3:be, to a very large extent, the result of luck. Sherlock Holmes
4-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
1-Holmeses, success in the province of detective work must always
2:be, to a very large extent, the result of luck. Sherlock Holmes
3-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/misc.rs:427:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::misc::after_context_line_numbers::{{closure}}
             at tests/misc.rs:427
   8: integration::misc::after_context_line_numbers
             at tests/macros.rs:7
   9: integration::misc::after_context_line_numbers::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- misc::before_context_line_numbers stdout ----
thread 'misc::before_context_line_numbers' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
2-Holmeses, success in the province of detective work must always
3:be, to a very large extent, the result of luck. Sherlock Holmes

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
1-Holmeses, success in the province of detective work must always
2:be, to a very large extent, the result of luck. Sherlock Holmes

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/misc.rs:451:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::misc::before_context_line_numbers::{{closure}}
             at tests/misc.rs:451
   8: integration::misc::before_context_line_numbers
             at tests/macros.rs:7
   9: integration::misc::before_context_line_numbers::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- misc::columns stdout ----
thread 'misc::columns' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:57:For the Doctor Watsons of this world, as opposed to the Sherlock
3:49:be, to a very large extent, the result of luck. Sherlock Holmes

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:57:For the Doctor Watsons of this world, as opposed to the Sherlock
2:49:be, to a very large extent, the result of luck. Sherlock Holmes

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/misc.rs:49:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::misc::columns::{{closure}}
             at tests/misc.rs:49
   8: integration::misc::columns
             at tests/macros.rs:7
   9: integration::misc::columns::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- misc::context_line_numbers stdout ----
thread 'misc::context_line_numbers' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
2-Holmeses, success in the province of detective work must always
--
5-but Doctor Watson has to have it taken out for him and dusted,
6:and exhibited clearly, with a label attached.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
1-Holmeses, success in the province of detective work must always
--
3-but Doctor Watson has to have it taken out for him and dusted,
3:and exhibited clearly, with a label attached.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/misc.rs:479:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::misc::context_line_numbers::{{closure}}
             at tests/misc.rs:479
   8: integration::misc::context_line_numbers
             at tests/macros.rs:7
   9: integration::misc::context_line_numbers::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- misc::inverted_line_numbers stdout ----
thread 'misc::inverted_line_numbers' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2:Holmeses, success in the province of detective work must always
4:can extract a clew from a wisp of straw or a flake of cigar ash;
5:but Doctor Watson has to have it taken out for him and dusted,
6:and exhibited clearly, with a label attached.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:Holmeses, success in the province of detective work must always
3:can extract a clew from a wisp of straw or a flake of cigar ash;
3:but Doctor Watson has to have it taken out for him and dusted,
3:and exhibited clearly, with a label attached.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/misc.rs:121:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::misc::inverted_line_numbers::{{closure}}
             at tests/misc.rs:121
   8: integration::misc::inverted_line_numbers
             at tests/macros.rs:7
   9: integration::misc::inverted_line_numbers::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- misc::line_numbers stdout ----
thread 'misc::line_numbers' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
3:be, to a very large extent, the result of luck. Sherlock Holmes

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:For the Doctor Watsons of this world, as opposed to the Sherlock
2:be, to a very large extent, the result of luck. Sherlock Holmes

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/misc.rs:38:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::misc::line_numbers::{{closure}}
             at tests/misc.rs:38
   8: integration::misc::line_numbers
             at tests/macros.rs:7
   9: integration::misc::line_numbers::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- misc::vimgrep stdout ----
thread 'misc::vimgrep' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sherlock:1:16:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:1:57:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:3:49:be, to a very large extent, the result of luck. Sherlock Holmes
sherlock:5:12:but Doctor Watson has to have it taken out for him and dusted,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sherlock:1:16:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:1:57:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:2:49:be, to a very large extent, the result of luck. Sherlock Holmes
sherlock:3:12:but Doctor Watson has to have it taken out for him and dusted,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/misc.rs:775:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::misc::vimgrep::{{closure}}
             at tests/misc.rs:775
   8: integration::misc::vimgrep
             at tests/macros.rs:7
   9: integration::misc::vimgrep::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- multiline::context stdout ----
thread 'multiline::context' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1-For the Doctor Watsons of this world, as opposed to the Sherlock
2:Holmeses, success in the province of detective work must always
3:be, to a very large extent, the result of luck. Sherlock Holmes
4-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1-For the Doctor Watsons of this world, as opposed to the Sherlock
1:Holmeses, success in the province of detective work must always
2:be, to a very large extent, the result of luck. Sherlock Holmes
3-can extract a clew from a wisp of straw or a flake of cigar ash;

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/multiline.rs:108:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::multiline::context::{{closure}}
             at tests/multiline.rs:108
   8: integration::multiline::context
             at tests/macros.rs:7
   9: integration::multiline::context::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- multiline::only_matching stdout ----
thread 'multiline::only_matching' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:Watson
1:Sherlock
2:Holmes
3:Sherlock Holmes
5:Watson

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1:Watson
1:Sherlock
2:Holmes
2:Sherlock Holmes
3:Watson

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/multiline.rs:59:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::multiline::only_matching::{{closure}}
             at tests/multiline.rs:59
   8: integration::multiline::only_matching
             at tests/macros.rs:7
   9: integration::multiline::only_matching::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic

---- multiline::vimgrep stdout ----
thread 'multiline::vimgrep' panicked at '
printed outputs differ!

expected:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sherlock:1:16:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:1:57:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:2:57:Holmeses, success in the province of detective work must always
sherlock:3:49:be, to a very large extent, the result of luck. Sherlock Holmes
sherlock:5:12:but Doctor Watson has to have it taken out for him and dusted,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

got:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
sherlock:1:16:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:1:57:For the Doctor Watsons of this world, as opposed to the Sherlock
sherlock:2:57:Holmeses, success in the province of detective work must always
sherlock:2:49:be, to a very large extent, the result of luck. Sherlock Holmes
sherlock:3:12:but Doctor Watson has to have it taken out for him and dusted,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
', tests/multiline.rs:77:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
   1: std::sys_common::backtrace::print
   2: std::panicking::default_hook::{{closure}}
   3: std::panicking::default_hook
   4: std::panicking::rust_panic_with_hook
   5: std::panicking::continue_panic_fmt
   6: std::panicking::begin_panic_fmt
   7: integration::multiline::vimgrep::{{closure}}
             at tests/multiline.rs:77
   8: integration::multiline::vimgrep
             at tests/macros.rs:7
   9: integration::multiline::vimgrep::{{closure}}
             at tests/macros.rs:5
  10: core::ops::function::FnOnce::call_once
             at libcore/ops/function.rs:238
  11: <F as alloc::boxed::FnBox<A>>::call_box
  12: __rust_maybe_catch_panic


failures:
    feature::f34_only_matching_line_column
    feature::f917_trim
    feature::f917_trim_match
    json::basic
    misc::after_context_line_numbers
    misc::before_context_line_numbers
    misc::columns
    misc::context_line_numbers
    misc::inverted_line_numbers
    misc::line_numbers
    misc::vimgrep
    multiline::context
    multiline::only_matching
    multiline::vimgrep

test result: FAILED. 173 passed; 14 failed; 0 ignored; 0 measured; 0 filtered out

Full build logs here: https://buildd.debian.org/status/package.php?p=rust-ripgrep&suite=sid

Click on the "Build-Attempted" fields in the "Status" column for more information.

For access to a big-endian Linux machine to be able to debug the issue, you can request an account from the gcc compile farm (https://gcc.gnu.org/wiki/CompileFarm) and test on Linux/sparc64, for example.

question

opened by glaubitz 52

preserve order of input files in output without sacrificing parallelism

There should be a way to tell rg to preserve the order of input files specified on the command line in the output.

E.g., if I'm searching a bunch of files which are in chronological order, I want the output to be in chronological order.
enhancement

opened by jikamens 45

ripgrep much slower than (rip)grep

What version of ripgrep are you using?

ripgrep 11.0.1 -SIMD -AVX (compiled) +SIMD -AVX (runtime)

How did you install ripgrep?

pacman -S ripgrep

What operating system are you using ripgrep on?

Arch Linux

Describe your question, feature request, or bug.

ripgrep is 3-4-5 times slower than GNU grep on simple string pattern.

If this is a bug, what is the actual behavior?

grep file\.php -r .  0.19s user 0.10s system 98% cpu 0.298 total
rg (--no-ignore) file\.php  3.68s user 0.45s system 365% cpu 1.129 total
rg --debug --hidden --no-ignore file\.php  6.12s user 0.42s system 383% cpu 1.706 total
DEBUG|grep_regex::literal|grep-regex/src/literal.rs:115: required literal found: "file"
DEBUG|globset|globset/src/lib.rs:435: built glob set; 0 literals, 0 basenames, 11 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
DEBUG|globset|globset/src/lib.rs:435: built glob set; 0 literals, 0 basenames, 11 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
DEBUG|globset|globset/src/lib.rs:435: built glob set; 0 literals, 0 basenames, 11 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
DEBUG|globset|globset/src/lib.rs:435: built glob set; 0 literals, 0 basenames, 11 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes
DEBUG|globset|globset/src/lib.rs:435: built glob set; 0 literals, 0 basenames, 11 extensions, 0 prefixes, 0 suffixes, 0 required extensions, 0 regexes

As I tried to find one-by-one what top-level file (or directory) causes the slowdown, I came to the conclusion: none. Ripgrep should be faster... So I did this table: (Sorry, for hiding the names, I'm not sure if I'm allowed to show them.)

#!/bin/sh
$ echo GREPWHAT=$GREPWHAT RGFLAGS=$RGFLAGS GREPFLAGS=$GREPFLAGS; find -maxdepth 1 | xargs -I{} sh -c 'echo $(echo {} | tr a-z x):$(du -sh {} | cut -f1):$(find {} | wc -l):$( ( time rg "$GREPWHAT" $RGFLAGS {} &>/dev/null ) 2>&1 | tr \\t\\n \  ):$( ( time find -mindepth 1 -maxdepth 1 -not -path {} | xargs rg "$GREPWHAT" $RGFLAGS  &>/dev/null ) 2>&1 | tr \\t\\n \  ):$( ( time grep "$GREPWHAT" $GREPFLAGS -r {} &>/dev/null ) 2>&1 | tr \\t\\n \ ):$( ( time find -mindepth 1 -maxdepth 1 -not -path {} | xargs grep "$GREPWHAT" $GREPFLAGS -r &>/dev/null ) 2>&1 | tr \\t\\n \  )' | column -ts: -Rsize,files,rgtime,rgwothistime,greptime,grepwothistime -Nname,size,files,rgtime,rgwothistime,greptime,grepwothistime

GREPWHAT=xxxxxxxxxxxxxxxxxxx.xxx RGFLAGS=-j1 GREPFLAGS=
name                  size  files                                      rgtime                                rgwothistime                                    greptime                             grepwothistime
.                     127M  12961   real 0m0.964s user 0m3.295s sys 0m0.348s    real 0m0.971s user 0m3.285s sys 0m0.388s    real 0m0.146s user 0m0.039s sys 0m0.100s    real 0m0.148s user 0m0.069s sys 0m0.078s
./xx                  4.0K      1   real 0m0.009s user 0m0.006s sys 0m0.003s    real 0m0.919s user 0m3.097s sys 0m0.406s    real 0m0.003s user 0m0.000s sys 0m0.003s    real 0m0.146s user 0m0.055s sys 0m0.089s
./_xxx_xxxxxx.xxx     428K      1   real 0m0.011s user 0m0.008s sys 0m0.004s    real 0m0.936s user 0m3.123s sys 0m0.388s    real 0m0.004s user 0m0.004s sys 0m0.000s    real 0m0.144s user 0m0.043s sys 0m0.100s
./xxxxxx               89M  11741   real 0m0.217s user 0m0.576s sys 0m0.211s    real 0m0.221s user 0m0.688s sys 0m0.109s    real 0m0.106s user 0m0.036s sys 0m0.064s    real 0m0.051s user 0m0.023s sys 0m0.029s
./xxxxx                16K      7   real 0m0.010s user 0m0.009s sys 0m0.004s    real 0m0.942s user 0m3.101s sys 0m0.418s    real 0m0.003s user 0m0.003s sys 0m0.000s    real 0m0.147s user 0m0.049s sys 0m0.098s
./xxxxxxx              52K     28   real 0m0.014s user 0m0.015s sys 0m0.004s    real 0m0.946s user 0m3.148s sys 0m0.418s    real 0m0.003s user 0m0.003s sys 0m0.000s    real 0m0.152s user 0m0.048s sys 0m0.099s
./xxxxxx.xxx          4.0K      1   real 0m0.008s user 0m0.006s sys 0m0.003s    real 0m0.929s user 0m3.113s sys 0m0.400s    real 0m0.003s user 0m0.000s sys 0m0.003s    real 0m0.143s user 0m0.051s sys 0m0.091s
./xxxxxx               20K      5   real 0m0.012s user 0m0.015s sys 0m0.000s    real 0m0.926s user 0m3.114s sys 0m0.421s    real 0m0.003s user 0m0.000s sys 0m0.003s    real 0m0.144s user 0m0.038s sys 0m0.105s
./xxxxxxxxx           248K     60   real 0m0.013s user 0m0.015s sys 0m0.005s    real 0m0.939s user 0m3.139s sys 0m0.384s    real 0m0.004s user 0m0.000s sys 0m0.004s    real 0m0.151s user 0m0.056s sys 0m0.095s
./xxxxxx.xx           4.0K      1   real 0m0.006s user 0m0.000s sys 0m0.006s    real 0m0.937s user 0m3.176s sys 0m0.413s    real 0m0.004s user 0m0.004s sys 0m0.000s    real 0m0.145s user 0m0.055s sys 0m0.089s
./xxxxxx               35M    522   real 0m0.068s user 0m0.138s sys 0m0.077s    real 0m0.227s user 0m0.639s sys 0m0.211s    real 0m0.036s user 0m0.025s sys 0m0.011s    real 0m0.114s user 0m0.031s sys 0m0.082s
./xxxx.xxx            4.0K      1   real 0m0.006s user 0m0.006s sys 0m0.001s    real 0m0.933s user 0m3.123s sys 0m0.408s    real 0m0.003s user 0m0.000s sys 0m0.003s    real 0m0.150s user 0m0.045s sys 0m0.104s
./xxxxxxx.xxx         4.0K      1   real 0m0.007s user 0m0.001s sys 0m0.006s    real 0m0.941s user 0m3.139s sys 0m0.409s    real 0m0.003s user 0m0.003s sys 0m0.000s    real 0m0.145s user 0m0.072s sys 0m0.072s
./xxxxx.xxx           4.0K      1   real 0m0.008s user 0m0.004s sys 0m0.004s    real 0m0.957s user 0m3.127s sys 0m0.419s    real 0m0.004s user 0m0.004s sys 0m0.000s    real 0m0.154s user 0m0.048s sys 0m0.101s
./xxxxxxxx            276K     52   real 0m0.013s user 0m0.016s sys 0m0.000s    real 0m1.037s user 0m2.956s sys 0m0.385s    real 0m0.004s user 0m0.004s sys 0m0.000s    real 0m0.147s user 0m0.036s sys 0m0.109s
./xxxxxx              128K     34   real 0m0.012s user 0m0.010s sys 0m0.005s    real 0m0.934s user 0m3.142s sys 0m0.398s    real 0m0.003s user 0m0.000s sys 0m0.003s    real 0m0.146s user 0m0.062s sys 0m0.083s
./xxxxxxxx.xxxx       212K      1   real 0m0.009s user 0m0.005s sys 0m0.004s    real 0m0.924s user 0m3.123s sys 0m0.362s    real 0m0.004s user 0m0.000s sys 0m0.003s    real 0m0.147s user 0m0.063s sys 0m0.083s
./xxxxxxxx.xxxx       4.0K      1   real 0m0.008s user 0m0.003s sys 0m0.005s    real 0m0.928s user 0m3.067s sys 0m0.422s    real 0m0.004s user 0m0.004s sys 0m0.000s    real 0m0.151s user 0m0.057s sys 0m0.088s
./xxxxxx              1.2M    294   real 0m0.018s user 0m0.027s sys 0m0.008s    real 0m0.852s user 0m2.761s sys 0m0.476s    real 0m0.007s user 0m0.000s sys 0m0.007s    real 0m0.141s user 0m0.033s sys 0m0.108s
./xxxxxxxxx            12K      5   real 0m0.012s user 0m0.016s sys 0m0.000s    real 0m0.987s user 0m2.797s sys 0m0.365s    real 0m0.003s user 0m0.000s sys 0m0.003s    real 0m0.148s user 0m0.038s sys 0m0.109s
./xxxxxxx             4.0K      1   real 0m0.005s user 0m0.000s sys 0m0.005s    real 0m1.074s user 0m2.989s sys 0m0.386s    real 0m0.005s user 0m0.004s sys 0m0.000s    real 0m0.143s user 0m0.057s sys 0m0.085s
./xxx                 764K    198   real 0m0.014s user 0m0.011s sys 0m0.012s    real 0m0.970s user 0m2.792s sys 0m0.481s    real 0m0.005s user 0m0.005s sys 0m0.000s    real 0m0.201s user 0m0.065s sys 0m0.133s
./.xxxxxxxx.xxxx.xxx   44K      1   real 0m0.007s user 0m0.003s sys 0m0.003s    real 0m1.393s user 0m2.965s sys 0m0.569s    real 0m0.004s user 0m0.000s sys 0m0.003s    real 0m0.205s user 0m0.079s sys 0m0.119s
./.xxxxxxxxx          4.0K      1   real 0m0.007s user 0m0.001s sys 0m0.006s    real 0m1.140s user 0m2.975s sys 0m0.556s    real 0m0.004s user 0m0.000s sys 0m0.004s    real 0m0.156s user 0m0.051s sys 0m0.099s
./.xxxxxxxxxxxxx      4.0K      1   real 0m0.006s user 0m0.003s sys 0m0.003s    real 0m0.954s user 0m3.055s sys 0m0.484s    real 0m0.003s user 0m0.003s sys 0m0.000s    real 0m0.149s user 0m0.070s sys 0m0.078s
./.xxx.xxxxxxx        4.0K      1   real 0m0.007s user 0m0.004s sys 0m0.003s    real 0m0.956s user 0m3.130s sys 0m0.402s    real 0m0.003s user 0m0.003s sys 0m0.000s    real 0m0.149s user 0m0.068s sys 0m0.076s
$ # Note that the sum of ripgrep times doesn't match with . time.
$ # wothis means: grepping in the directory with that file excluded.
$ time tokei
-------------------------------------------------------------------------------
 Language            Files        Lines         Code     Comments       Blanks
-------------------------------------------------------------------------------
...
-------------------------------------------------------------------------------
 Total                9256      1221713       827992       262436       131285
-------------------------------------------------------------------------------

real    0m1.061s
user    0m3.384s
sys     0m0.295s
$ # Note that tokei has similar running time.
$ stat -f . | head -3
  File: "."
    ID: 0        Namelen: 255     Type: tmpfs
Block size: 4096       Fundamental block size: 4096
$ # Fast as hell tmpfs. Does it count?

Tomorrow I will make a line length statistics if it counts, but I think it should be an issue around directory listing. Anyway, I would like to help, so tell me what to do/share. --debug didn't help too much.

question

opened by zsugabubus 38

support searching compressed files using in-process decompression

I'd like to use ripgrep for grepping log files, because it's faster then grep. But my logs are gzipped, and if I zcat | rg them I'll loose log filenames in output.

Also, would be great if bzip2 and xz decompressors will be supported too with automatic archive type detection.
question icebox

opened by danbst 38
Color customization
We should definitely try to support customizing colors in the output similar to how ag does it. Currently they support 3 color customizations, as per this issue:

--colors-match

--colors-path

--colors-line-number

Implementing the part where we set colors based on an argument is not particularly hard (just a matter of translating user input to term::Attr enums). Parsing input in the bash terminal format like ag does was not difficult to implement. However, this limits Windows usage because we don't have an easy translation between those colors.

How should we go about supporting these color customizations for both Linux, Mac and Windows?
enhancement
opened by eugene-bulkin 38
fix(globset/serde1): allow deserializing owned strings into `Glob`

This PR modifies how Glob is deserialized such that it now allows for owned strings (previously, only borrowed) to be deserialized into Glob. This takes inspiration from what is done in the regex_serde crate.

For more details, see the discussion in #2386.

The first commit includes tests, which fail without the solution. The second commit include the solution.

This fixes #2386.

I'd be happy to hear from your thoughts and I'm open to any review :-)

opened by jeertmans 0
$support standard character escape sequences (e.g. \t, \x1D) in the replacement string$
support standard character escape sequences (e.g. \t, \x1D) in the replacement string
I'd like ripgrep to natively support replacements with common escape sequences (e.g --replace '\t' to replace with a horizontal tab)

It is quite unwieldy to have to write e.g. rg ... --replace ...$(echo -ne '\x1F')... instead of just being able to do rg ... --replace ...\x1F...

Additionally, being able to easily add '\x00' would be very nice in certain situations (for example, when delimiting the end of file names that contain enough special characters to make it quite annoying to deal with (since \0 is the only illegal character in filepaths)).

Perhaps you could simply implement the stuff described in https://docs.rs/regex/latest/regex/#escape-sequences (with perhaps the addition of a few others such as '\e' and '\0' for convenience, especially the ones available with echo -eat the typical shell)?

Personally, by far the most used of these for me would be \x1[C-F], \x1b (for highlighting sections of the output in the terminal), \t, \n, and \0, but I frequently wish to make use of this capability, and have to either resort to ugly workarounds like the one previously mentioned, or use a different program(s).

If you don't wish to modify the base functionality of --replace due to it possibly breaking existing scripts (though I'd think that because of the replacement string being evaluated at startup time, and the user presumably being the one providing the input, and the relevant characters themselves, breakage would likely be small and easily fixable), perhaps you can create --extended-replace <extended replacement string> as an alternative to the current --replace that supports standard character escapes, and allow doing -rx <extended replacement string> (with the shorthand explicitly having -r followed immediately by 'x' and then the replacement string being the next arg (unlike -r currently, which (somewhat confusingly) takes the rest of the current arg, if present as the replacement instead of the next argument) (I presume this could work due to rg's implementation. The use of 'x' is also kinda nice due to it being prominent in '\x' and "extend").

I figure this all wouldn't be too difficult to implement due to it mostly already being implemented elsewhere, would have a minimal (negative) impact on rg as a whole, and be quite useful in certain situations whilst adding functionality many people might expect to be present already, so is this something that could be added to rg, or would I have to maintain a fork of it if I want this?

Documentation could be something like

-rx, --extended-replace REPLACEMENT_TEXT Like --replace, but interprets various backslash escapes \x([0-9A-Fa-f]{2,}) for the UTF-8 character with hexadecimal value $1 Additionally, interprets \\ as a literal '\' \e as \x1b \0 as \x00 (the null byte) \t as \x09 (horizontal tab) \n ...
opened by mwaitzman 1
globset: `serde` feature - cannot deserialize `String` into `Glob`
Hi, I hope that posting issues about subcrates is ok.

What version of globset are you using?

globset = { version = "0.4.9", features = ["serde1"] }.

Describe your bug.

Because the implementation of trait Deserialize uses &str, it does not accept deserializing owned String.

https://github.com/BurntSushi/ripgrep/blob/61101289fabc032fd8e90009c41d0b78e6dfc9a2/crates/globset/src/serde_impl.rs#L15-L22

What are the steps to reproduce the behavior?

This problem occurred to me when I tried to parse Globs from a toml::Value object (already obtained from a file). As toml::Value owns strings, it caused a problem.

If needed, I can include a MWE (but quite large).

What is the actual behavior?

When parsing some globs, here is the error obtained:

Error: TomlDecode(Error { inner: ErrorInner { kind: Custom, line: None, col: 0, at: None, message: "invalid type: string \"src/**.rs\", expected a borrowed string", key: [] } })

What is the expected behavior?

Not sure if it is interesting performance-wise, but using a custom deserialize_with function, with String instead of &str, fixes the problem (glob.as_str()) has to be used afterward).

I can provide tests and make a PR if you are ok with this solution. Otherwise, I am also open to discussions :-)
opened by jeertmans 2
The `--pretty` option doesn't override config file
What version of ripgrep are you using?

ripgrep 13.0.0 -SIMD -AVX (compiled) +SIMD +AVX (runtime)

How did you install ripgrep?

Installed from Debian bookworm

What operating system are you using ripgrep on?

Debian

Describe your bug.

I use --no-heading \n --no-line-number in my config file referenced by RIPGREP_CONFIG_PATH. I can explicitly add the --heading etc. options for a one-off commandline execution, but --pretty doesn't work as expected. I'd expect to have it be a true "convenience alias" as documented.

Instead, the output continues to use the options from the config file, including neither heading nor line numbers.
bug
opened by mrjoel 4
Try harder to fix #916

The underlying Rust issue1 was recently re-introduced and re-fixed. Rather than wait for a new Rust release, apply effectively the same fix as a workaround in the ignore crate itself.

opened by tavianator 0
Option for writing results to file
Describe your feature request

An option --output or --outfile to write what ripgrep would print in a terminal to a file instead but byte-exact.

Usually, you would pipe the stdout to a file like rg "expr" infile.txt > outfile.txt to do this. However, there are circumstances where this doesn't work as expected:

Line breaks may not be preserved by the terminal as-is. Both cmd.exe (using conhost.exe) and PowerShell (pwsh using the Terminal app) on Windows turn \r and \n into \r\n. A sequence of \n\r ends up as \r\n\r\n. Furthermore, a trailing newline (\r\n) is appended.

Git Bash from Git for Windows leaves the line breaks as they are but appends a trailing \n.

\r makes the terminals on Windows write over the current line, but it's difficult to understand what's going on because redirecting the output to a file does not give you the exact byte stream either.

Special terminal characters can mess with the redirection https://github.com/BurntSushi/ripgrep/issues/1309#issuecomment-633927149

Spaces after the command might end up in the output (although this appears to be limited to spaces before | and cmd.exe) https://github.com/BurntSushi/ripgrep/issues/1500

enhancement help wanted
opened by Simran-B 2

Releases(13.0.0)

13.0.0(Jun 12, 2021)
ripgrep 13 is a new major version release of ripgrep that primarily contains bug fixes, some performance improvements and a few minor breaking changes. There is also a fix for a security vulnerability on Windows (CVE-2021-3013).

In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches the current directory for a regex pattern. By default, ripgrep will respect gitignore rules and automatically skip hidden files/directories and binary files.

Some highlights:

A new short flag, -., has been added. It is an alias for the --hidden flag, which instructs ripgrep to search hidden files and directories.

ripgrep is now using a new vectorized implementation of memmem, which accelerates many common searches. If you notice any performance regressions (or major improvements), I'd love to hear about them through an issue report!

Also, for Windows users targeting MSVC, Cargo will now build fully static executables of ripgrep. The release binaries for ripgrep 13 have been compiled using this configuration.

BREAKING CHANGES:

Binary detection output has changed slightly.

In this release, a small tweak has been made to the output format when a binary file is detected. Previously, it looked like this:

Binary file FOO matches (found "\0" byte around offset XXX)

Now it looks like this:

FOO: binary file matches (found "\0" byte around offset XXX)

vimgrep output in multi-line now only prints the first line for each match.

See issue 1866 for more discussion on this. Previously, every line in a match was duplicated, even when it spanned multiple lines. There are no changes to vimgrep output when multi-line mode is disabled.

In multi-line mode, --count is now equivalent to --count-matches.

This appears to match how pcre2grep implements --count. Previously, ripgrep would produce outright incorrect counts. Another alternative would be to simply count the number of lines---even if it's more than the number of matches---but that seems highly unintuitive.

FULL LIST OF FIXES AND IMPROVEMENTS:

Security fixes:

CVE-2021-3013: Fixes a security hole on Windows where running ripgrep with either the -z/--search-zip or --pre flags can result in running arbitrary executables from the current directory.

VULN #1773: This is the public facing issue tracking CVE-2021-3013. ripgrep's README now contains a section describing how to report a vulnerability.

Performance improvements:

PERF #1657: Check if a file should be ignored first before issuing stat calls.

PERF memchr#82: ripgrep now uses a new vectorized implementation of memmem.

Feature enhancements:

Added or improved file type filtering for ASP, Bazel, dvc, FlatBuffers, Futhark, minified files, Mint, pofiles (from GNU gettext) Racket, Red, Ruby, VCL, Yang.

FEATURE #1404: ripgrep now prints a warning if nothing is searched.

FEATURE #1613: Cargo will now produce static executables on Windows when using MSVC.

FEATURE #1680: Add -. as a short flag alias for --hidden.

FEATURE #1842: Add --field-{context,match}-separator for customizing field delimiters.

FEATURE #1856: The README now links to a Spanish translation.

Bug fixes:

BUG #1277: Document cygwin path translation behavior in the FAQ.

BUG #1739: Fix bug where replacements were buggy if the regex matched a line terminator.

BUG #1311: Fix multi-line bug where a search & replace for \n didn't work as expected.

BUG #1401: Fix buggy interaction between PCRE2 look-around and -o/--only-matching.

BUG #1412: Fix multi-line bug with searches using look-around past matching lines.

BUG #1577: Fish shell completions will continue to be auto-generated.

BUG #1642: Fixes a bug where using -m and -A printed more matches than the limit.

BUG #1703: Clarify the function of -u/--unrestricted.

BUG #1708: Clarify how -S/--smart-case works.

BUG #1730: Clarify that CLI invocation must always be valid, regardless of config file.

BUG #1741: Fix stdin detection when using PowerShell in UNIX environments.

BUG #1756: Fix bug where foo/** would match foo, but it shouldn't.

BUG #1765: Fix panic when --crlf is used in some cases.

BUG #1638: Correctly sniff UTF-8 and do transcoding, like we do for UTF-16.

BUG #1816: Add documentation for glob alternate syntax, e.g., {a,b,..}.

BUG #1847: Clarify how the --hidden flag works.

BUG #1866: Fix bug when computing column numbers in --vimgrep mode.

BUG #1868: Fix bug where --passthru and -A/-B/-C did not override each other.

BUG #1869: Clarify docs for --files-with-matches and --files-without-match.

BUG #1878: Fix bug where \A could produce unanchored matches in multiline search.

BUG 94e4b8e3: Fix column numbers with --vimgrep is used with -U/--multiline.

Source code(tar.gz)
Source code(zip)
ripgrep-13.0.0-arm-unknown-linux-gnueabihf.tar.gz(1.68 MB)
ripgrep-13.0.0-i686-pc-windows-msvc.zip(1.51 MB)
ripgrep-13.0.0-x86_64-apple-darwin.tar.gz(1.73 MB)
ripgrep-13.0.0-x86_64-pc-windows-gnu.zip(9.35 MB)
ripgrep-13.0.0-x86_64-pc-windows-msvc.zip(1.65 MB)
ripgrep-13.0.0-x86_64-unknown-linux-musl.tar.gz(2.01 MB)
ripgrep_13.0.0_amd64.deb(1.50 MB)
12.1.1(May 29, 2020)
ripgrep 12.1.1 is a patch release that fixes a couple small bugs. In particular, the ripgrep 12.1.0 release did not tag new releases for all of its in-tree dependencies. As a result, ripgrep built dependencies from crates.io would produce a different build than compiling ripgrep from source on the 12.1.0 tag. Namely, some crates like grep-cli had unreleased changes.

In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. By default, ripgrep will respect your gitignore rules and automatically skip hidden files/directories and binary files.

Bug fixes:

BUG #1581: Corrects some egregious markup output in --help.

BUG #1591: Mention the special $0 capture group in docs for the -r/--replace flag.

BUG #1602: Fix failing test resulting from out-of-sync dependencies.

Source code(tar.gz)
Source code(zip)
ripgrep-12.1.1-arm-unknown-linux-gnueabihf.tar.gz(1.75 MB)
ripgrep-12.1.1-i686-pc-windows-msvc.zip(1.58 MB)
ripgrep-12.1.1-x86_64-apple-darwin.tar.gz(1.79 MB)
ripgrep-12.1.1-x86_64-pc-windows-gnu.zip(9.08 MB)
ripgrep-12.1.1-x86_64-pc-windows-msvc.zip(1.75 MB)
ripgrep-12.1.1-x86_64-unknown-linux-musl.tar.gz(2.10 MB)
ripgrep_12.1.1_amd64.deb(1.38 MB)
12.1.0(May 9, 2020)
ripgrep 12.1.0 is a small minor version release that mostly includes bug fixes and documentation improvements. This release also contains some important notices for downstream packagers.

In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files.

Notices for downstream ripgrep package maintainers:

Fish shell completions will be removed in the ripgrep 13 release. See #1577 for more details.

ripgrep has switched from a2x to asciidoctor to generate the man page. If asciidoctor is not present, then ripgrep will currently fall back to a2x. Support for a2x will be dropped in the ripgrep 13 release. See #1544 for more details.

Feature enhancements:

FEATURE #1547: Support decompressing .Z files via uncompress.

Bug fixes:

BUG #1252: Add a section on the --pre flag to the GUIDE.

BUG #1339: Improve error message when a pattern with invalid UTF-8 is provided.

BUG #1524: Note how to escape a $ when using --replace.

BUG #1537: Fix match bug caused by inner literal optimization.

BUG #1544: ripgrep now uses asciidoctor instead of a2x to generate its man page.

BUG #1550: Substantially reduce peak memory usage when searching wide directories.

BUG #1571: Add note about configuration files in --type-{add,clear} docs.

BUG #1573: Fix incorrect --count-matches output when using look-around.

Source code(tar.gz)
Source code(zip)
ripgrep-12.1.0-arm-unknown-linux-gnueabihf.tar.gz(1.76 MB)
ripgrep-12.1.0-i686-pc-windows-msvc.zip(1.60 MB)
ripgrep-12.1.0-x86_64-apple-darwin.tar.gz(1.80 MB)
ripgrep-12.1.0-x86_64-pc-windows-gnu.zip(9.15 MB)
ripgrep-12.1.0-x86_64-pc-windows-msvc.zip(1.75 MB)
ripgrep-12.1.0-x86_64-unknown-linux-musl.tar.gz(2.11 MB)
ripgrep_12.1.0_amd64.deb(1.38 MB)
12.0.1(Mar 29, 2020)
ripgrep 12.0.1 is a small patch release that includes a minor bug fix relating to superfluous error messages when searching git repositories with sub-modules. This was a regression introduced in the 12.0.0 release.

In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files.

Bug fixes:

BUG #1520: Don't emit spurious error messages in git repositories with submodules.

Source code(tar.gz)
Source code(zip)
ripgrep-12.0.1-arm-unknown-linux-gnueabihf.tar.gz(1.76 MB)
ripgrep-12.0.1-i686-pc-windows-msvc.zip(1.60 MB)
ripgrep-12.0.1-x86_64-apple-darwin.tar.gz(1.86 MB)
ripgrep-12.0.1-x86_64-pc-windows-gnu.zip(9.35 MB)
ripgrep-12.0.1-x86_64-pc-windows-msvc.zip(1.76 MB)
ripgrep-12.0.1-x86_64-unknown-linux-musl.tar.gz(2.13 MB)
ripgrep_12.0.1_amd64.deb(1.39 MB)
12.0.0(Mar 16, 2020)
ripgrep 12 is a new major version release of ripgrep that contains many bug fixes, several important performance improvements and a few minor new features.

In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files.

In a near future release, I am hoping to add an indexing feature to ripgrep, which will dramatically speed up searching by building an index. Feedback would very much be appreciated, especially on the user experience which will be difficult to get right.

This release has no known breaking changes.

Deprecations:

The --no-pcre2-unicode flag is deprecated. Instead, use the --no-unicode flag, which applies to both the default regex engine and PCRE2. For now, --no-pcre2-unicode and --pcre2-unicode are aliases to --no-unicode and --unicode, respectively. The --[no-]pcre2-unicode flags may be removed in a future release.

The --auto-hybrid-regex flag is deprecated. Instead, use the new --engine flag with the auto value.

Performance improvements:

PERF #1087: ripgrep is smarter when detected literals are whitespace.

PERF #1381: Directory traversal is sped up with speculative ignore-file existence checks.

PERF cd8ec38a: Improve inner literal detection to cover more cases more effectively. e.g., +Sherlock Holmes + now has Sherlock Holmes extracted instead of .

PERF 6a0e0147: Improve literal detection when the -w/--word-regexp flag is used.

PERF ad97e9c9: Improve overall performance of the -w/--word-regexp flag.

Feature enhancements:

Added or improved file type filtering for erb, diff, Gradle, HAML, Org, Postscript, Skim, Slim, Slime, RPM Spec files, Typoscript, xml.

FEATURE #1370: Add --include-zero flag that shows files searched without matches.

FEATURE #1390: Add --no-context-separator flag that always hides context separators.

FEATURE #1414: Add --no-require-git flag to allow ripgrep to respect gitignores anywhere.

FEATURE #1420: Add --no-ignore-exclude to disregard rules in .git/info/exclude files.

FEATURE #1466: Add --no-ignore-files flag to disable all --ignore-file flags.

FEATURE #1488: Add '--engine' flag for easier switching between regex engines.

FEATURE 75cbe88f: Add --no-unicode flag. This works on all supported regex engines.

Bug fixes:

BUG #1291: ripgrep now works in non-existent directories.

BUG #1319: Fix match bug due to errant literal detection.

BUG #1335: Fixes a performance bug when searching plain text files with very long lines. This was a serious performance regression in some cases.

BUG #1344: Document usage of --type all.

BUG #1389: Fixes a bug where ripgrep would panic when searching a symlinked directory.

BUG #1439: Improve documentation for ripgrep's automatic stdin detection.

BUG #1441: Remove CPU features from man page.

BUG #1442, BUG #1478: Improve documentation of the -g/--glob flag.

BUG #1445: ripgrep now respects ignore rules from .git/info/exclude in worktrees.

BUG #1485: Fish shell completions from the release Debian package are now installed to /usr/share/fish/vendor_completions.d/rg.fish.

Source code(tar.gz)
Source code(zip)
ripgrep-12.0.0-arm-unknown-linux-gnueabihf.tar.gz(1.76 MB)
ripgrep-12.0.0-i686-pc-windows-msvc.zip(1.59 MB)
ripgrep-12.0.0-x86_64-apple-darwin.tar.gz(1.85 MB)
ripgrep-12.0.0-x86_64-pc-windows-gnu.zip(11.06 MB)
ripgrep-12.0.0-x86_64-pc-windows-msvc.zip(1.75 MB)
ripgrep-12.0.0-x86_64-unknown-linux-musl.tar.gz(2.12 MB)
ripgrep_12.0.0_amd64.deb(1.38 MB)
11.0.2(Aug 1, 2019)
ripgrep 11.0.2 is a new patch release that fixes a few bugs, including a performance regression and a matching bug when using the -F/--fixed-strings flag.

In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files.

Feature enhancements:

FEATURE #1293: Added --glob-case-insensitive flag that makes --glob behave as --iglob.

Bug fixes:

BUG #1246: Add translations to README, starting with an unofficial Chinese translation.

BUG #1259: Fix bug where the last byte of a -f file was stripped if it wasn't a \n.

BUG #1261: Document that no error is reported when searching for \n with -P/--pcre2.

BUG #1284: Mention .ignore and .rgignore more prominently in the README.

BUG #1292: Fix bug where --with-filename was sometimes enabled incorrectly.

BUG #1268: Fix major performance regression in GitHub x86_64-linux binary release.

BUG #1302: Show better error messages when a non-existent preprocessor command is given.

BUG #1334: Fix match regression with -F flag when patterns contain meta characters.

Source code(tar.gz)
Source code(zip)
ripgrep-11.0.2-arm-unknown-linux-gnueabihf.tar.gz(1.51 MB)
ripgrep-11.0.2-i686-pc-windows-gnu.zip(10.46 MB)
ripgrep-11.0.2-i686-pc-windows-msvc.zip(1.52 MB)
ripgrep-11.0.2-i686-unknown-linux-musl.tar.gz(1.94 MB)
ripgrep-11.0.2-x86_64-apple-darwin.tar.gz(1.81 MB)
ripgrep-11.0.2-x86_64-pc-windows-gnu.zip(10.69 MB)
ripgrep-11.0.2-x86_64-pc-windows-msvc.zip(1.68 MB)
ripgrep-11.0.2-x86_64-unknown-linux-musl.tar.gz(2.12 MB)
ripgrep_11.0.2_amd64.deb(1.39 MB)
11.0.1(Apr 16, 2019)
ripgrep 11.0.1 is a new patch release that fixes a search regression introduced in the previous 11.0.0 release. In particular, ripgrep can enter an infinite loop for some search patterns when searching invalid UTF-8.

Bug fixes:

BUG #1247: Fix search bug that can cause ripgrep to enter an infinite loop.

Source code(tar.gz)
Source code(zip)
ripgrep-11.0.1-arm-unknown-linux-gnueabihf.tar.gz(1.47 MB)
ripgrep-11.0.1-i686-pc-windows-gnu.zip(6.60 MB)
ripgrep-11.0.1-i686-pc-windows-msvc.zip(1.52 MB)
ripgrep-11.0.1-i686-unknown-linux-musl.tar.gz(1.90 MB)
ripgrep-11.0.1-x86_64-apple-darwin.tar.gz(1.86 MB)
ripgrep-11.0.1-x86_64-pc-windows-gnu.zip(6.75 MB)
ripgrep-11.0.1-x86_64-pc-windows-msvc.zip(1.68 MB)
ripgrep-11.0.1-x86_64-unknown-linux-musl.tar.gz(1.92 MB)
ripgrep_11.0.1_amd64.deb(1.36 MB)
11.0.0(Apr 15, 2019)
ripgrep 11 is a new major version release of ripgrep that contains many bug fixes, some performance improvements and a few feature enhancements. Notably, ripgrep's user experience for binary file filtering has been improved. See the guide's new section on binary data for more details.

In case you haven't heard of it before, ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files.

This release also marks a change in ripgrep's versioning. Where as the previous version was 0.10.0, this version is 11.0.0. Moving forward, ripgrep's major version will be increased a few times per year. ripgrep will continue to be conservative with respect to backwards compatibility, but may occasionally introduce breaking changes, which will always be documented in this CHANGELOG. See issue 1172 for a bit more detail on why this versioning change was made.

This release increases the minimum supported Rust version from 1.28.0 to 1.34.0.

BREAKING CHANGES:

ripgrep has tweaked its exit status codes to be more like GNU grep's. Namely, if a non-fatal error occurs during a search, then ripgrep will now always emit a 2 exit status code, regardless of whether a match is found or not. Previously, ripgrep would only emit a 2 exit status code for a catastrophic error (e.g., regex syntax error). One exception to this is if ripgrep is run with -q/--quiet. In that case, if an error occurs and a match is found, then ripgrep will exit with a 0 exit status code.

Supplying the -u/--unrestricted flag three times is now equivalent to supplying --no-ignore --hidden --binary. Previously, -uuu was equivalent to --no-ignore --hidden --text. The difference is that --binary disables binary file filtering without potentially dumping binary data into your terminal. That is, rg -uuu foo should now be equivalent to grep -r foo.

The avx-accel feature of ripgrep has been removed since it is no longer necessary. All uses of AVX in ripgrep are now enabled automatically via runtime CPU feature detection. The simd-accel feature does remain available (only for enabling SIMD for transcoding), however, it does increase compilation times substantially at the moment.

Performance improvements:

PERF #497, PERF #838: Make rg -F -f dictionary-of-literals much faster.

Feature enhancements:

Added or improved file type filtering for Apache Thrift, ASP, Bazel, Brotli, BuildStream, bzip2, C, C++, Cython, gzip, Java, Make, Postscript, QML, Tex, XML, xz, zig and zstd.

FEATURE #855: Add --binary flag for disabling binary file filtering.

FEATURE #1078: Add --max-columns-preview flag for showing a preview of long lines.

FEATURE #1099: Add support for Brotli and Zstd to the -z/--search-zip flag.

FEATURE #1138: Add --no-ignore-dot flag for ignoring .ignore files.

FEATURE #1155: Add --auto-hybrid-regex flag for automatically falling back to PCRE2.

FEATURE #1159: ripgrep's exit status logic should now match GNU grep. See updated man page.

FEATURE #1164: Add --ignore-file-case-insensitive for case insensitive ignore globs.

FEATURE #1185: Add -I flag as a short option for the --no-filename flag.

FEATURE #1207: Add none value to -E/--encoding to forcefully disable all transcoding.

FEATURE da9d7204: Add --pcre2-version for querying showing PCRE2 version information.

Bug fixes:

BUG #306, BUG #855: Improve the user experience for ripgrep's binary file filtering.

BUG #373, BUG #1098: ** is now accepted as valid syntax anywhere in a glob.

BUG #916: ripgrep no longer hangs when searching /proc with a zombie process present.

BUG #1052: Fix bug where ripgrep could panic when transcoding UTF-16 files.

BUG #1055: Suggest -U/--multiline when a pattern contains a \n.

BUG #1063: Always strip a BOM if it's present, even for UTF-8.

BUG #1064: Fix inner literal detection that could lead to incorrect matches.

BUG #1079: Fixes a bug where the order of globs could result in missing a match.

BUG #1089: Fix another bug where ripgrep could panic when transcoding UTF-16 files.

BUG #1091: Add note about inverted flags to the man page.

BUG #1093: Fix handling of literal slashes in gitignore patterns.

BUG #1095: Fix corner cases involving the --crlf flag.

BUG #1101: Fix AsciiDoc escaping for man page output.

BUG #1103: Clarify what --encoding auto does.

BUG #1106: --files-with-matches and --files-without-match work with one file.

BUG #1121: Fix bug that was triggering Windows antimalware when using the --files flag.

BUG #1125, BUG #1159: ripgrep shouldn't panic for rg -h | rg and should emit correct exit status.

BUG #1144: Fixes a bug where line numbers could be wrong on big-endian machines.

BUG #1154: Windows files with "hidden" attribute are now treated as hidden.

BUG #1173: Fix handling of ** patterns in gitignore files.

BUG #1174: Fix handling of repeated ** patterns in gitignore files.

BUG #1176: Fix bug where -F/-x weren't applied to patterns given via -f.

BUG #1189: Document cases where ripgrep may use a lot of memory.

BUG #1203: Fix a matching bug related to the suffix literal optimization.

BUG 8f14cb18: Increase the default stack size for PCRE2's JIT.

Source code(tar.gz)
Source code(zip)
ripgrep-11.0.0-arm-unknown-linux-gnueabihf.tar.gz(1.48 MB)
ripgrep-11.0.0-i686-pc-windows-gnu.zip(6.61 MB)
ripgrep-11.0.0-i686-pc-windows-msvc.zip(1.52 MB)
ripgrep-11.0.0-i686-unknown-linux-musl.tar.gz(1.90 MB)
ripgrep-11.0.0-x86_64-apple-darwin.tar.gz(1.85 MB)
ripgrep-11.0.0-x86_64-pc-windows-gnu.zip(6.75 MB)
ripgrep-11.0.0-x86_64-pc-windows-msvc.zip(1.68 MB)
ripgrep-11.0.0-x86_64-unknown-linux-musl.tar.gz(1.92 MB)
ripgrep_11.0.0_amd64.deb(1.36 MB)
0.10.0(Sep 7, 2018)
ripgrep is a line-oriented search tool that recursively searches your current directory for a regex pattern while respecting your gitignore rules. ripgrep has first class support on Windows, macOS and Linux, with binary downloads available for every release. ripgrep is similar to other popular search tools like The Silver Searcher, ack and grep.

This is a new minor version release of ripgrep that contains some major new features, a huge number of bug fixes, and is the first release based on libripgrep. The entirety of ripgrep's core search and printing code has been rewritten and generalized so that anyone can make use of it.

Major new features include PCRE2 support, multi-line search and a JSON output format.

BREAKING CHANGES:

The minimum version required to compile Rust has now changed to track the latest stable version of Rust. Patch releases will continue to compile with the same version of Rust as the previous patch release, but new minor versions will use the current stable version of the Rust compile as its minimum supported version.

The match semantics of -w/--word-regexp have changed slightly. They used to be \b(?:<your pattern>)\b, but now it's (?:^|\W)(?:<your pattern>)(?:$|\W). This matches the behavior of GNU grep and is believed to be closer to the intended semantics of the flag. See #389 for more details.

Feature enhancements:

FEATURE #162: libripgrep is now a thing. The primary crate is grep.

FEATURE #176: Add -U/--multiline flag that permits matching over multiple lines.

FEATURE #188: Add -P/--pcre2 flag that gives support for look-around and backreferences.

FEATURE #244: Add --json flag that prints results in a JSON Lines format.

FEATURE #321: Add --one-file-system flag to skip directories on different file systems.

FEATURE #404: Add --sort and --sortr flag for more sorting. Deprecate --sort-files.

FEATURE #416: Add --crlf flag to permit $ to work with carriage returns on Windows.

FEATURE #917: The --trim flag strips prefix whitespace from all lines printed.

FEATURE #993: Add --null-data flag, which makes ripgrep use NUL as a line terminator.

FEATURE #997: The --passthru flag now works with the --replace flag.

FEATURE #1038-1: Add --line-buffered and --block-buffered for forcing a buffer strategy.

FEATURE #1038-2: Add --pre-glob for filtering files through the --pre flag.

Bug fixes:

BUG #2: Searching with non-zero context can now use memory maps if appropriate.

BUG #200: ripgrep will now stop correctly when its output pipe is closed.

BUG #389: The -w/--word-regexp flag now works more intuitively.

BUG #643: Detection of readable stdin has improved on Windows.

BUG #441, BUG #690, BUG #980: Matching empty lines now works correctly in several corner cases.

BUG #764: Color escape sequences now coalesce, which reduces output size.

BUG #842: Add man page to binary Debian package.

BUG #922: ripgrep is now more robust with respect to memory maps failing.

BUG #937: Color escape sequences are no longer emitted for empty matches.

BUG #940: Context from the --passthru flag should not impact process exit status.

BUG #984: Fixes bug in ignore crate where first path was always treated as a symlink.

BUG #990: Read stderr asynchronously when running a process.

BUG #1013: Add compile time and runtime CPU features to --version output.

BUG #1028: Don't complete bare pattern after -f in zsh.

Source code(tar.gz)
Source code(zip)
ripgrep-0.10.0-arm-unknown-linux-gnueabihf.tar.gz(1.55 MB)
ripgrep-0.10.0-i686-pc-windows-gnu.zip(9.37 MB)
ripgrep-0.10.0-i686-pc-windows-msvc.zip(1.42 MB)
ripgrep-0.10.0-i686-unknown-linux-musl.tar.gz(1.93 MB)
ripgrep-0.10.0-x86_64-apple-darwin.tar.gz(1.87 MB)
ripgrep-0.10.0-x86_64-pc-windows-gnu.zip(9.48 MB)
ripgrep-0.10.0-x86_64-pc-windows-msvc.zip(1.57 MB)
ripgrep-0.10.0-x86_64-unknown-linux-musl.tar.gz(1.96 MB)
ripgrep_0.10.0_amd64.deb(1.39 MB)
0.9.0(Aug 3, 2018)
This is a new minor version release of ripgrep that contains some minor new features and a panoply of bug fixes.

Releases provided on Github for x86_64 will now work on all target CPUs, and will also automatically take advantage of features found on modern CPUs (such as AVX2) for additional optimizations.

This release increases the minimum supported Rust version from 1.20.0 to 1.23.0.

It is anticipated that the next release of ripgrep (0.10.0) will provide multi-line search support and a JSON output format.

BREAKING CHANGES:

When --count and --only-matching are provided simultaneously, the behavior of ripgrep is as if the --count-matches flag was given. That is, the total number of matches is reported, where there may be multiple matches per line. Previously, the behavior of ripgrep was to report the total number of matching lines. (Note that this behavior diverges from the behavior of GNU grep.)

Octal syntax is no longer supported. ripgrep previously accepted expressions like \1 as syntax for matching U+0001, but ripgrep will now report an error instead.

The --line-number-width flag has been removed. Its functionality was not carefully considered with all ripgrep output formats. See #795 for more details.

Feature enhancements:

Added or improved file type filtering for Android, Bazel, Fuschia, Haskell, Java and Puppet.

FEATURE #411: Add a --stats flag, which emits aggregate statistics after search results.

FEATURE #646: Add a --no-ignore-messages flag, which suppresses parse errors from reading .ignore and .gitignore files.

FEATURE #702: Support \u{..} Unicode escape sequences.

FEATURE #812: Add -b/--byte-offset flag that shows the byte offset of each matching line.

FEATURE #814: Add --count-matches flag, which is like --count, but for each match.

FEATURE #880: Add a --no-column flag, which disables column numbers in the output.

FEATURE #898: Add support for lz4 when using the -z/--search-zip flag.

FEATURE #924: termcolor has moved to its own repository: https://github.com/BurntSushi/termcolor

FEATURE #934: Add a new flag, --no-ignore-global, that permits disabling global gitignores.

FEATURE #967: Rename --maxdepth to --max-depth for consistency. Keep --maxdepth for backwards compatibility.

FEATURE #978: Add a --pre option to filter inputs with an arbitrary program.

FEATURE fca9709d: Improve zsh completion.

Bug fixes:

BUG #135: Release portable binaries that conditionally use SSSE3, AVX2, etc., at runtime.

BUG #268: Print descriptive error message when trying to use look-around or backreferences.

BUG #395: Show comprehensible error messages for regexes like \s*{.

BUG #526: Support backslash escapes in globs.

BUG #795: Fix problems with --line-number-width by removing it.

BUG #832: Clarify usage instructions for -f/--file flag.

BUG #835: Fix small performance regression while crawling very large directory trees.

BUG #851: Fix -S/--smart-case detection once and for all.

BUG #852: Be robust with respect to ENOMEM errors returned by mmap.

BUG #853: Upgrade grep crate to regex-syntax 0.6.0.

BUG #893: Improve support for git submodules.

BUG #900: When no patterns are given, ripgrep should never match anything.

BUG #907: ripgrep will now stop traversing after the first file when --quiet --files is used.

BUG #918: Don't skip tar archives when -z/--search-zip is used.

BUG #934: Don't respect gitignore files when searching outside git repositories.

BUG #948: Use exit code 2 to indicate error, and use exit code 1 to indicate no matches.

BUG #951: Add stdin example to ripgrep usage documentation.

BUG #955: Use buffered writing when not printing to a tty, which fixes a performance regression.

BUG #957: Improve the error message shown for --path separator / in some Windows shells.

BUG #964: Add a --no-fixed-strings flag to disable -F/--fixed-strings.

BUG #988: Fix a bug in the ignore crate that prevented the use of explicit ignore files after disabling all other ignore rules.

BUG #995: Respect $XDG_CONFIG_DIR/git/config for detecting core.excludesFile.

Source code(tar.gz)
Source code(zip)
ripgrep-0.9.0-arm-unknown-linux-gnueabihf.tar.gz(1.34 MB)
ripgrep-0.9.0-i686-pc-windows-gnu.zip(10.00 MB)
ripgrep-0.9.0-i686-pc-windows-msvc.zip(1.07 MB)
ripgrep-0.9.0-i686-unknown-linux-musl.tar.gz(1.46 MB)
ripgrep-0.9.0-x86_64-apple-darwin.tar.gz(1.35 MB)
ripgrep-0.9.0-x86_64-pc-windows-gnu.zip(10.35 MB)
ripgrep-0.9.0-x86_64-pc-windows-msvc.zip(1.16 MB)
ripgrep-0.9.0-x86_64-unknown-linux-musl.tar.gz(1.45 MB)
ripgrep_0.9.0_amd64.deb(6.91 MB)
0.8.1(Feb 21, 2018)
This is a patch release of ripgrep that primarily fixes regressions introduced in 0.8.0 (#820 and #824) in directory traversal on Windows. These regressions do not impact non-Windows users.

Feature enhancements:

Added or improved file type filtering for csv and VHDL.

FEATURE #798: Add underline support to termcolor and ripgrep. See documentation on the --colors flag for details.

Bug fixes:

BUG #684: Improve documentation for the --ignore-file flag.

BUG #789: Don't show (rev ) if the revision wasn't available during the build.

BUG #791: Add man page to ARM release.

BUG #797: Improve documentation for "intense" setting in termcolor.

BUG #800: Fix a bug in the ignore crate for custom ignore files. This had no impact on ripgrep.

BUG #807: Fix a bug where rg --hidden . behaved differently from rg --hidden ./.

BUG #815: Clarify a common failure mode in user guide.

BUG #820: Fixes a bug on Windows where symlinks were followed even if not requested.

BUG #824: Fix a performance regression in directory traversal on Windows.

Source code(tar.gz)
Source code(zip)
ripgrep-0.8.1-arm-unknown-linux-gnueabihf.tar.gz(1.21 MB)
ripgrep-0.8.1-i686-pc-windows-gnu.zip(9.53 MB)
ripgrep-0.8.1-i686-pc-windows-msvc.zip(987.14 KB)
ripgrep-0.8.1-i686-unknown-linux-musl.tar.gz(1.33 MB)
ripgrep-0.8.1-x86_64-apple-darwin.tar.gz(1.23 MB)
ripgrep-0.8.1-x86_64-pc-windows-gnu.zip(9.64 MB)
ripgrep-0.8.1-x86_64-pc-windows-msvc.zip(1.02 MB)
ripgrep-0.8.1-x86_64-unknown-linux-musl.tar.gz(1.30 MB)
ripgrep_0.8.1_amd64.deb(6.21 MB)
0.8.0(Feb 12, 2018)
This is a new minor version releae of ripgrep that satisfies several popular feature requests (config files, search compressed files, true colors), fixes many bugs and improves the quality of life for ripgrep maintainers. This release also includes greatly improved documentation in the form of a User Guide and a FAQ.

This release increases the minimum supported Rust version from 1.17 to 1.20.

BREAKING CHANGES:

Note that these are all very minor and unlikely to impact most users.

In order to support configuration files, flag overrides needed to be rethought. In some cases, this changed ripgrep's behavior. For example, in ripgrep 0.7.1, rg foo -s -i will perform a case sensitive search since the -s/--case-sensitive flag was defined to always take precedence over the -i/--ignore-case flag, regardless of position. In ripgrep 0.8.0 however, the override rule for all flags has changed to "the most recent flag wins among competing flags." That is, rg foo -s -i now performs a case insensitive search.

The -M/--max-columns flag was tweaked so that specifying a value of 0 now makes ripgrep behave as if the flag was absent. This makes it possible to set a default value in a configuration file and then override it. The previous ripgrep behavior was to suppress all matching non-empty lines.

In all globs, [^...] is now equivalent to [!...] (indicating class negation). Previously, ^ had no special significance in a character class.

For downstream packagers, the directory hierarchy in ripgrep's archive releases has changed. The root directory now only contains the executable, README and license. There is now a new directory called doc which contains the man page (previously in the root), a user guide (new), a FAQ (new) and the CHANGELOG (previously not included in release). The complete directory remains the same.

Feature enhancements:

Added or improved file type filtering for Apache Avro, C++, GN, Google Closure Templates, Jupyter notebooks, man pages, Protocol Buffers, Smarty and Web IDL.

FEATURE #196: Support a configuration file. See the new user guide for details.

FEATURE #261: Add extended or "true" color support. Works in Windows 10! See the FAQ for details.

FEATURE #539: Search gzip, bsip2, lzma or xz files when given -z/--search-zip flag.

FEATURE #544: Add support for line number alignment via a new --line-number-width flag.

FEATURE #654: Support linuxbrew in ripgrep's Brew tap.

FEATURE #673: Bring back .rgignore files. (A higher precedent, application specific version of .ignore.)

FEATURE #676: Provide ARM binaries. WARNING: This will be provided on a best effort basis.

FEATURE #709: Suggest -F/--fixed-strings flag on a regex syntax error.

FEATURE #740: Add a --passthru flag that causes ripgrep to print every line it reads.

FEATURE #785: Overhaul documentation. Cleaned up README, added user guide and FAQ.

FEATURE 7f5c07: Add hidden flags for convenient overrides (e.g., --no-text).

Bug fixes:

BUG #553: Permit flags to be repeated.

BUG #633: Fix a bug where ripgrep would panic on Windows while following symlinks.

BUG #649: Fix handling of !**/ in .gitignore.

BUG #663: BREAKING CHANGE: Support [^...] glob syntax (as identical to [!...]).

BUG #693: Don't display context separators when not printing matches.

BUG #705: Fix a bug that prevented ripgrep from searching OneDrive directories.

BUG #717: Improve --smart-case uppercase character detection.

BUG #725: Clarify that globs do not override explicitly given paths to search.

BUG #742: Write ANSI reset code as \x1B[0m instead of \x1B[m.

BUG #747: Remove yarn.lock from YAML file type.

BUG #760: ripgrep can now search /sys/devices/system/cpu/vulnerabilities/* files.

BUG #761: Fix handling of gitignore patterns that contain a /.

BUG #776: BREAKING CHANGE: --max-columns=0 now disables the limit.

BUG #779: Clarify documentation for --files-without-match.

BUG #780, BUG #781: Fix bug where ripgrep missed some matching lines.

Maintenance fixes:

MAINT #772: Drop env_logger in favor of simpler logger to avoid many new dependencies.

MAINT #772: Add git revision hash to ripgrep's version string.

MAINT #772: (Seemingly) improve compile times.

MAINT #776: Automatically generate man page during build.

MAINT #786: Remove use of unsafe in globset. :tada:

MAINT e9d448: Add an issue template (has already drastically improved bug reports).

MAINT ae2d03: Remove the compile script.

Friends of ripgrep:

I'd like to extend my gratitude to @balajisivaraman for their recent hard work in a number of areas, and in particular, for implementing the "search compressed files" feature. Their work in sketching out a specification for that and other work has been exemplary.

Thanks @balajisivaraman!
Source code(tar.gz)
Source code(zip)
ripgrep-0.8.0-arm-unknown-linux-gnueabihf.tar.gz(1.20 MB)
ripgrep-0.8.0-i686-pc-windows-gnu.zip(5.24 MB)
ripgrep-0.8.0-i686-pc-windows-msvc.zip(929.33 KB)
ripgrep-0.8.0-i686-unknown-linux-musl.tar.gz(1.33 MB)
ripgrep-0.8.0-x86_64-apple-darwin.tar.gz(1.22 MB)
ripgrep-0.8.0-x86_64-pc-windows-gnu.zip(5.21 MB)
ripgrep-0.8.0-x86_64-pc-windows-msvc.zip(974.54 KB)
ripgrep-0.8.0-x86_64-unknown-linux-musl.tar.gz(1.30 MB)
ripgrep_0.8.0_amd64.deb(6.21 MB)
0.7.1(Oct 22, 2017)
This is a patch release of ripgrep that includes a fix to very bad regression introduced in ripgrep 0.7.0.

Bug fixes:

BUG #648: Fix a bug where it was very easy to exceed standard file descriptor limits.

Source code(tar.gz)
Source code(zip)
ripgrep-0.7.1-i686-pc-windows-gnu.zip(5.46 MB)
ripgrep-0.7.1-i686-pc-windows-msvc.zip(887.01 KB)
ripgrep-0.7.1-i686-unknown-linux-musl.tar.gz(1.15 MB)
ripgrep-0.7.1-x86_64-apple-darwin.tar.gz(1.05 MB)
ripgrep-0.7.1-x86_64-pc-windows-gnu.zip(5.48 MB)
ripgrep-0.7.1-x86_64-pc-windows-msvc.zip(929.83 KB)
ripgrep-0.7.1-x86_64-unknown-linux-musl.tar.gz(1.12 MB)
0.7.0(Oct 22, 2017)
This is a new minor version release of ripgrep that includes mostly bug fixes.

ripgrep continues to require Rust 1.17, and there are no known breaking changes introduced in this release.

Feature enhancements:

Added or improved file type filtering for config & license files, Elm, Purescript, Standard ML, sh, systemd, Terraform

FEATURE #593: Using both -o/--only-matching and -r/--replace does the right thing.

Bug fixes:

BUG #200: ripgrep will stop when its pipe is closed.

BUG #402: Fix context printing bug when the -m/--max-count flag is used.

BUG #521: Fix interaction between -r/--replace and terminal colors.

BUG #559: Ignore test that tried reading a non-UTF-8 file path on macOS.

BUG #599: Fix color escapes on empty matches.

BUG #600: Avoid expensive (on Windows) file handle check when using --files.

BUG #618: Clarify installation instructions for Ubuntu users.

BUG #633: Faster symlink loop checking on Windows.

Source code(tar.gz)
Source code(zip)
ripgrep-0.7.0-i686-pc-windows-gnu.zip(5.47 MB)
ripgrep-0.7.0-i686-pc-windows-msvc.zip(887.06 KB)
ripgrep-0.7.0-i686-unknown-linux-musl.tar.gz(1.15 MB)
ripgrep-0.7.0-x86_64-apple-darwin.tar.gz(1.05 MB)
ripgrep-0.7.0-x86_64-pc-windows-gnu.zip(5.48 MB)
ripgrep-0.7.0-x86_64-pc-windows-msvc.zip(930.19 KB)
ripgrep-0.7.0-x86_64-unknown-linux-musl.tar.gz(1.12 MB)
0.6.0(Aug 24, 2017)
This is a new minor version release of ripgrep that includes many bug fixes and a few new features such as --iglob and -x/--line-regexp.

Note that this release increases the minimum supported Rust version from 1.12 to 1.17.

Feature enhancements:

Added or improved file type filtering for BitBake, C++, Cabal, cshtml, Julia, Make, msbuild, QMake, Yocto

FEATURE #163: Add an --iglob flag that is like -g/--glob, but matches globs case insensitively.

FEATURE #520: Add -x/--line-regexp flag, which requires a match to span an entire line.

FEATURE #551, FEATURE #554: ignore: add new matched_path_or_any_parents method.

Bug fixes:

BUG #342: Fix invisible text in some PowerShell environments by changing the default color scheme on Windows.

BUG #413: Release binaries on Unix are now strip'd by default. This decreases binary size by an order of magnitude.

BUG #483: When --quiet is passed, --files should be quiet.

BUG #488: When --vimgrep is passed, --with-filename should be enabled automatically.

BUG #493: Fix another bug in the implementation of the -o/--only-matching flag.

BUG #499: Permit certain flags to override others.

BUG #523: wincolor: Re-fetch Windows console on all calls.

BUG #523: --version now shows enabled compile-time features.

BUG #532, BUG #536, BUG #538, BUG #540, BUG #560, BUG #565: Improve zsh completion.

BUG #578: Enable SIMD for encoding_rs when appropriate.

BUG #580: Fix -w/--word-regexp in the presence of capturing groups.

BUG #581: Document that ripgrep may terminate unexpectedly when searching via memory maps (which can happen using default settings).

Friends of ripgrep:

I'd like to give a big Thank You to @okdana for their recent hard work on ripgrep. This includes new features like --line-regexp, heroic effort on zsh auto-completion and thinking through some thorny argv issues with me.

I'd also like to thank @ericbn for their work on improving ripgrep's argv parsing by allowing some flags to override others.

Thanks @okdana and @ericbn!
Source code(tar.gz)
Source code(zip)
ripgrep-0.6.0-i686-pc-windows-gnu.zip(5.34 MB)
ripgrep-0.6.0-i686-pc-windows-msvc.zip(912.59 KB)
ripgrep-0.6.0-i686-unknown-linux-musl.tar.gz(1.19 MB)
ripgrep-0.6.0-x86_64-apple-darwin.tar.gz(1.06 MB)
ripgrep-0.6.0-x86_64-pc-windows-gnu.zip(5.35 MB)
ripgrep-0.6.0-x86_64-pc-windows-msvc.zip(957.54 KB)
ripgrep-0.6.0-x86_64-unknown-linux-musl.tar.gz(1.15 MB)
0.5.2(May 11, 2017)
Feature enhancements:

Added or improved file type filtering for Nix.

FEATURE #362: Add --regex-size-limit and --dfa-size-limit flags.

FEATURE #444: Improve error messages for invalid globs.

Bug fixes:

BUG #442: Fix line wrapping in --help output.

BUG #451: Fix bug with duplicate output when using -o/--only-matching flag.

Source code(tar.gz)
Source code(zip)
ripgrep-0.5.2-i686-pc-windows-gnu.zip(4.88 MB)
ripgrep-0.5.2-i686-pc-windows-msvc.zip(863.55 KB)
ripgrep-0.5.2-i686-unknown-linux-musl.tar.gz(5.39 MB)
ripgrep-0.5.2-x86_64-apple-darwin.tar.gz(1.21 MB)
ripgrep-0.5.2-x86_64-pc-windows-gnu.zip(4.96 MB)
ripgrep-0.5.2-x86_64-pc-windows-msvc.zip(908.25 KB)
ripgrep-0.5.2-x86_64-unknown-linux-musl.tar.gz(5.35 MB)
0.5.1(Apr 9, 2017)
Feature enhancements:

Added or improved file type filtering for vim.

FEATURE #34: Add a -o/--only-matching flag.

FEATURE #377: Column numbers can now be customized with a color. (The default is no color.)

FEATURE #419: Added -0 short flag option for --null.

Bug fixes:

BUG #381: Include license text in all subcrates.

BUG #418, BUG #426, BUG #439: Fix a few bugs with -h/--help output.

Source code(tar.gz)
Source code(zip)
ripgrep-0.5.1-i686-pc-windows-gnu.zip(4.84 MB)
ripgrep-0.5.1-i686-pc-windows-msvc.zip(885.77 KB)
ripgrep-0.5.1-i686-unknown-linux-musl.tar.gz(5.38 MB)
ripgrep-0.5.1-x86_64-apple-darwin.tar.gz(1.20 MB)
ripgrep-0.5.1-x86_64-pc-windows-gnu.zip(4.93 MB)
ripgrep-0.5.1-x86_64-pc-windows-msvc.zip(929.96 KB)
ripgrep-0.5.1-x86_64-unknown-linux-musl.tar.gz(5.33 MB)
0.5.0(Mar 13, 2017)
This is a new minor version release of ripgrep that includes one minor breaking change, bug fixes and several new features including support for text encodings other than UTF-8.

A notable accomplishment with respect to Rust is that ripgrep proper now only contains a single unsafe use (for accessing the contents of a memory map).

The breaking change is:

FEATURE #380: Line numbers are now hidden by default when ripgrep is printing to a tty and the only thing searched is stdin.

Feature enhancements:

Added or improved file type filtering for Ceylon, CSS, Elixir, HTML, log, SASS, SVG, Twig

FEATURE #1: Add support for additional text encodings, including automatic detection for UTF-16 via BOM sniffing. Explicit text encoding support with the -E/--encoding flag was also added for latin-1, GBK, EUC-JP and Shift_JIS, among others. The full list can be found here: https://encoding.spec.whatwg.org/#concept-encoding-get

FEATURE #129: Add a new -M/--max-columns flag that omits lines longer than the given number of bytes. (Disabled by default!)

FEATURE #369: A new flag, --max-filesize, was added for limiting searches to files with a maximum file size.

Bug fixes:

BUG #52, BUG #311: Tweak how binary files are detected and handled. (We are slightly less conservative and will no longer use memory without bound.)

BUG #326: When --files flag is given, we should never attempt to parse positional arguments as regexes.

BUG #327: Permit the --heading flag to override the --no-heading flag.

BUG #340: Clarify that the -u/--unrestricted flags are aliases.

BUG #343: Global git ignore config should use $HOME/.config/git/ignore and not $HOME/git/ignore.

BUG #345: Clarify docs for -g/--glob flag.

BUG #381: Add license files to each sub-crate.

BUG #383: Use latest version of clap (for argv parsing).

BUG #392: Fix translation of set globs (e.g., {foo,bar,quux}) to regexes.

BUG #401: Add PowerShell completion file to Windows release.

BUG #405: Fix bug when excluding absolute paths with the -g/--glob flag.

Source code(tar.gz)
Source code(zip)
ripgrep-0.5.0-i686-pc-windows-gnu.zip(4.39 MB)
ripgrep-0.5.0-i686-pc-windows-msvc.zip(857.21 KB)
ripgrep-0.5.0-i686-unknown-linux-musl.tar.gz(5.35 MB)
ripgrep-0.5.0-x86_64-apple-darwin.tar.gz(1.20 MB)
ripgrep-0.5.0-x86_64-pc-windows-gnu.zip(4.49 MB)
ripgrep-0.5.0-x86_64-pc-windows-msvc.zip(902.40 KB)
ripgrep-0.5.0-x86_64-unknown-linux-musl.tar.gz(5.31 MB)
0.4.0(Jan 14, 2017)
This is a new minor version release of ripgrep that includes a couple very minor breaking changes, a few new features and lots of bug fixes.

This version of ripgrep upgrades its regex dependency from 0.1 to 0.2, which includes a few minor syntax changes:

POSIX character classes now require double bracketing. Previously, the regex [:upper:] would parse as the upper POSIX character class. Now it parses as the character class containing the characters :upper:. The fix to this change is to use [[:upper:]] instead. Note that variants like [[:upper:][:blank:]] continue to work.

The character [ must always be escaped inside a character class.

The characters &, - and ~ must be escaped if any one of them are repeated consecutively. For example, [&], [\&], [\&\&], [&-&] are all equivalent while [&&] is illegal. (The motivation for this and the prior change is to provide a backwards compatible path for adding character class set notation.)

Feature enhancements:

Added or improved file type filtering for Crystal, Kotlin, Perl, PowerShell, Ruby, Swig

FEATURE #83: Type definitions can now include other type definitions.

FEATURE #243: BREAKING CHANGE: The --column flag now implies --line-number.

FEATURE #263: Add a new --sort-files flag.

FEATURE #275: Add a new --path-separator flag. Useful in cygwin.

Bug fixes:

BUG #182: Redux: use more portable ANSI color escape sequences when possible.

BUG #258: Fix bug that caused ripgrep's parallel iterator to spin and burn CPU.

BUG #262: Document how to install shell completion files.

BUG #268: Make lack of backreference support more explicit.

BUG #271: Remove ~ dependency on clap.

BUG #277: Fix cosmetic issue in globset crate docs.

BUG #279: ripgrep did not terminate when -q/--quiet was given.

BUG #281: BREAKING CHANGE: Completely remove ^C handling from ripgrep.

BUG #284: Make docs for -g/--glob clearer.

BUG #286: When stdout is redirected to a file, don't search that file.

BUG #287: Fix ZSH completions.

BUG #295: Remove superfluous memmap dependency in grep crate.

BUG #308: Improve docs for -r/--replace.

BUG #313: Update bytecount dep to latest version.

BUG #318: Fix invalid UTF-8 output bug in Windows consoles.

Source code(tar.gz)
Source code(zip)
ripgrep-0.4.0-i686-pc-windows-gnu.zip(3.77 MB)
ripgrep-0.4.0-i686-pc-windows-msvc.zip(730.76 KB)
ripgrep-0.4.0-i686-unknown-linux-musl.tar.gz(4.55 MB)
ripgrep-0.4.0-x86_64-apple-darwin.tar.gz(1.01 MB)
ripgrep-0.4.0-x86_64-pc-windows-gnu.zip(3.89 MB)
ripgrep-0.4.0-x86_64-pc-windows-msvc.zip(781.98 KB)
ripgrep-0.4.0-x86_64-unknown-linux-musl.tar.gz(4.51 MB)
0.3.2(Dec 7, 2016)
Feature enhancements:

Added or improved file type filtering for Less, Sass, stylus, Zsh

Bug fixes:

BUG #229: Make smart case slightly less conservative.

BUG #247: Clarify use of --heading/--no-heading.

BUG #251, BUG #264, BUG #267: Fix matching bug caused by literal optimizations.

BUG #256: Fix bug that caused rg foo and rg foo/ to have different behavior when foo was a symlink.

BUG #270: Fix bug where patterns starting with a - couldn't be used with the -e/--regexp flag. (This resolves a regression that was introduced in ripgrep 0.3.0.)

Source code(tar.gz)
Source code(zip)
ripgrep-0.3.2-i686-pc-windows-gnu.zip(3.67 MB)
ripgrep-0.3.2-i686-pc-windows-msvc.zip(713.74 KB)
ripgrep-0.3.2-i686-unknown-linux-musl.tar.gz(4.20 MB)
ripgrep-0.3.2-x86_64-apple-darwin.tar.gz(1.02 MB)
ripgrep-0.3.2-x86_64-pc-windows-gnu.zip(3.74 MB)
ripgrep-0.3.2-x86_64-pc-windows-msvc.zip(749.50 KB)
ripgrep-0.3.2-x86_64-unknown-linux-musl.tar.gz(4.15 MB)
0.3.1(Nov 22, 2016)
Bug fixes:

BUG #242: ripgrep didn't respect --colors foo:none correctly. Now it does.

Source code(tar.gz)
Source code(zip)
ripgrep-0.3.1-i686-pc-windows-gnu.zip(3.70 MB)
ripgrep-0.3.1-i686-pc-windows-msvc.zip(710.32 KB)
ripgrep-0.3.1-i686-unknown-linux-musl.tar.gz(4.14 MB)
ripgrep-0.3.1-x86_64-apple-darwin.tar.gz(1.03 MB)
ripgrep-0.3.1-x86_64-pc-windows-gnu.zip(3.76 MB)
ripgrep-0.3.1-x86_64-pc-windows-msvc.zip(749.40 KB)
ripgrep-0.3.1-x86_64-unknown-linux-musl.tar.gz(4.08 MB)
0.3.0(Nov 20, 2016)
This is a new minor version release of ripgrep that includes two breaking changes with lots of bug fixes and some new features and performance improvements. Notably, if you had a problem with colors or piping on Windows before, then that should now be fixed in this release.

BREAKING CHANGES:

ripgrep now requires Rust 1.11 to compile. Previously, it could build on Rust 1.9. The cause of this was the move from Docopt to Clap for argument parsing.

The -e/--regexp flag can no longer accept a pattern starting with a -. There are two work-arounds: rg -- -foo and rg [-]foo or rg -e [-]foo will all search for the same -foo pattern. The cause of this was the move from Docopt to Clap for argument parsing. This may get fixed in the future..

Performance improvements:

PERF #33: ripgrep now performs similar to GNU grep on small corpora.

PERF #136: ripgrep no longer slows down because of argument parsing when given a large argument list.

Feature enhancements:

Added or improved file type filtering for Elixir.

FEATURE #7: Add a -f/--file flag that causes ripgrep to read patterns from a file.

FEATURE #51: Add a --colors flag that enables one to customize the colors used in ripgrep's output.

FEATURE #138: Add a --files-without-match flag that shows only file paths that contain zero matches.

FEATURE #230: Add completion files to the release (Bash, Fish and PowerShell).

Bug fixes:

BUG #37: Use correct ANSI escape sequences when TERM=screen.linux.

BUG #94: ripgrep now detects stdin on Windows automatically.

BUG #117: Colors should now work correctly and automatically inside mintty.

BUG #182: Colors should now work within Emacs. In particular, --color=always will emit colors regardless of the current environment.

BUG #189: Show less content when running rg -h. The full help content can be accessed with rg --help.

BUG #210: Support non-UTF-8 file names on Unix platforms.

BUG #231: Switch from block buffering to line buffering.

BUG #241: Some error messages weren't suppressed when --no-messages was used.

Source code(tar.gz)
Source code(zip)
ripgrep-0.3.0-i686-pc-windows-gnu.zip(3.70 MB)
ripgrep-0.3.0-i686-pc-windows-msvc.zip(709.14 KB)
ripgrep-0.3.0-i686-unknown-linux-musl.tar.gz(4.14 MB)
ripgrep-0.3.0-x86_64-apple-darwin.tar.gz(1.03 MB)
ripgrep-0.3.0-x86_64-pc-windows-gnu.zip(3.76 MB)
ripgrep-0.3.0-x86_64-pc-windows-msvc.zip(749.58 KB)
ripgrep-0.3.0-x86_64-unknown-linux-musl.tar.gz(4.08 MB)
0.2.9(Nov 10, 2016)

null
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.9-i686-pc-windows-gnu.zip(3.74 MB)
ripgrep-0.2.9-i686-pc-windows-msvc.zip(601.52 KB)
ripgrep-0.2.9-i686-unknown-linux-musl.tar.gz(3.74 MB)
ripgrep-0.2.9-x86_64-apple-darwin.tar.gz(951.78 KB)
ripgrep-0.2.9-x86_64-pc-windows-gnu.zip(3.83 MB)
ripgrep-0.2.9-x86_64-pc-windows-msvc.zip(652.78 KB)
ripgrep-0.2.9-x86_64-unknown-linux-musl.tar.gz(3.65 MB)
0.2.8(Nov 6, 2016)

null
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.8-i686-pc-windows-gnu.zip(3.74 MB)
ripgrep-0.2.8-i686-pc-windows-msvc.zip(601.90 KB)
ripgrep-0.2.8-i686-unknown-linux-musl.tar.gz(3.74 MB)
ripgrep-0.2.8-x86_64-apple-darwin.tar.gz(951.29 KB)
ripgrep-0.2.8-x86_64-pc-windows-gnu.zip(3.83 MB)
ripgrep-0.2.8-x86_64-pc-windows-msvc.zip(653.23 KB)
ripgrep-0.2.8-x86_64-unknown-linux-musl.tar.gz(3.65 MB)
0.2.6(Nov 1, 2016)

null
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.6-i686-pc-windows-gnu.zip(3.57 MB)
ripgrep-0.2.6-i686-pc-windows-msvc.zip(557.87 KB)
ripgrep-0.2.6-i686-unknown-linux-musl.tar.gz(3.47 MB)
ripgrep-0.2.6-x86_64-apple-darwin.tar.gz(868.85 KB)
ripgrep-0.2.6-x86_64-pc-windows-gnu.zip(3.66 MB)
ripgrep-0.2.6-x86_64-pc-windows-msvc.zip(605.84 KB)
ripgrep-0.2.6-x86_64-unknown-linux-musl.tar.gz(3.39 MB)
0.2.5(Oct 30, 2016)

null
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.5-i686-pc-windows-gnu.zip(3.57 MB)
ripgrep-0.2.5-i686-pc-windows-msvc.zip(557.30 KB)
ripgrep-0.2.5-i686-unknown-linux-musl.tar.gz(3.47 MB)
ripgrep-0.2.5-x86_64-apple-darwin.tar.gz(868.83 KB)
ripgrep-0.2.5-x86_64-pc-windows-gnu.zip(3.66 MB)
ripgrep-0.2.5-x86_64-pc-windows-msvc.zip(605.34 KB)
ripgrep-0.2.5-x86_64-unknown-linux-musl.tar.gz(3.39 MB)
0.2.3(Oct 11, 2016)

Automatically deployed release
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.3-i686-pc-windows-gnu.zip(3.37 MB)
ripgrep-0.2.3-i686-pc-windows-msvc.zip(535.03 KB)
ripgrep-0.2.3-i686-unknown-linux-musl.tar.gz(2.96 MB)
ripgrep-0.2.3-x86_64-apple-darwin.tar.gz(823.05 KB)
ripgrep-0.2.3-x86_64-pc-windows-gnu.zip(3.46 MB)
ripgrep-0.2.3-x86_64-pc-windows-msvc.zip(582.71 KB)
ripgrep-0.2.3-x86_64-unknown-linux-musl.tar.gz(2.91 MB)
0.2.2(Oct 11, 2016)

null
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.2-i686-pc-windows-gnu.zip(3.36 MB)
ripgrep-0.2.2-i686-pc-windows-msvc.zip(533.10 KB)
ripgrep-0.2.2-i686-unknown-linux-musl.tar.gz(2.96 MB)
ripgrep-0.2.2-x86_64-apple-darwin.tar.gz(819.50 KB)
ripgrep-0.2.2-x86_64-pc-windows-gnu.zip(3.45 MB)
ripgrep-0.2.2-x86_64-pc-windows-msvc.zip(580.45 KB)
ripgrep-0.2.2-x86_64-unknown-linux-musl.tar.gz(2.92 MB)
0.2.1(Sep 27, 2016)

Windows release
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.1-i686-apple-darwin.tar.gz(784.28 KB)
ripgrep-0.2.1-i686-pc-windows-gnu.zip(3.24 MB)
ripgrep-0.2.1-i686-pc-windows-msvc.zip(555.63 KB)
ripgrep-0.2.1-i686-unknown-linux-musl.tar.gz(2.76 MB)
ripgrep-0.2.1-x86_64-apple-darwin.tar.gz(790.83 KB)
ripgrep-0.2.1-x86_64-pc-windows-gnu.zip(3.32 MB)
ripgrep-0.2.1-x86_64-pc-windows-msvc.zip(585.82 KB)
ripgrep-0.2.1-x86_64-unknown-linux-musl.tar.gz(2.73 MB)
0.2.0(Sep 26, 2016)

Windows release
Source code(tar.gz)
Source code(zip)
ripgrep-0.2.0-i686-apple-darwin.tar.gz(793.99 KB)
ripgrep-0.2.0-i686-pc-windows-gnu.zip(3.28 MB)
ripgrep-0.2.0-i686-pc-windows-msvc.zip(569.50 KB)
ripgrep-0.2.0-i686-unknown-linux-musl.tar.gz(2.80 MB)
ripgrep-0.2.0-x86_64-apple-darwin.tar.gz(801.34 KB)
ripgrep-0.2.0-x86_64-pc-windows-gnu.zip(3.35 MB)
ripgrep-0.2.0-x86_64-pc-windows-msvc.zip(591.23 KB)
ripgrep-0.2.0-x86_64-unknown-linux-musl.tar.gz(2.77 MB)