mirror of
https://github.com/BurntSushi/ripgrep.git
synced 2025-04-02 20:45:38 +02:00
5af7707a35
If ripgrep was called in a way where the entire contents of a file aren't read (like --files-with-matches, among other methods), and if the file was read through an external process, then ripgrep would never reap that process. We fix this by introducing an explicit 'close' method, which we now call when using decompression or preprocessor searches. The implementation of 'close' is a little hokey. In particular, when we close stdout, this usually results in a broken pipe, and, consequently, a non-zero code returned once the child process is reaped. This is "situation normal," so we invent a (hopefully portable) heuristic for detecting it. Fixes #1766, Closes #1767
ripgrep core
This is the core ripgrep crate. In particular, main.rs is where the main
function lives.
Most of ripgrep core consists of two things:
- The definition of the CLI interface, including docs for every flag.
- Glue code that brings the
grep-matcher,grep-regex,grep-searcherandgrep-printercrates together to actually execute the search.
Currently, there are no plans to make ripgrep core available as an independent library. However, much of the heavy lifting of ripgrep is done via its constituent crates, which can be reused independent of ripgrep. Unfortunately, there is no guide or tutorial to teach folks how to do this yet.