| Age | Commit message (Collapse) | Author |
|---|
|
We test the release process in Travis by setting TRAVIS_TAG explicitly.
We test the release process in Appveyor by switching to a branch test.
|
|
Remove some outdated comments and unused config. Also, make the regex for
matching tags a bit more specific.
|
|
Travis docs[1] say this is ignore when 'tags' is used.
[1] - https://docs.travis-ci.com/user/deployment/#conditional-releases-with-on
|
|
This commit adds Bash, zsh and fish completions to the Debian binary
package.
Fixes #1032
|
|
I don't think every change here is needed, but this ensures we're using
the latest version of every direct dependency.
|
|
|
|
This is a preliminary script to copy example code from a Markdown file
into a crate's example directory.
This is intended to be used for the upcoming libripgrep guide, but we
don't commit any examples yet.
|
|
|
|
These are (or will be) used in grep's examples.
|
|
We initially did not have this impl because the first revision of the Sink
trait was much more complicated. In particular, each method was
parameterized over a Matcher. But not every Sink impl actually needs a
Matcher, and it is just as easy to borrow a Matcher explicitly, so the
added parameterization wasn't holding its own.
This does permit Sink implementations to be used as trait objects. One
key use case here is to reduce compile times, since there is quite a bit
of code inside grep-searcher that is parameterized on Sink. Unfortunately,
that code is *also* parameterized on Matcher, and the various printers in
grep-printer are also parameterized on Matcher, which means Sink trait
objects are necessary but no sufficient for a major reduction in compile
times. Unfortunately, the path to making Matcher object safe isn't quite
clear. Extension traits maybe? There's also stuff in the Serde ecosystem
that might help, but the type shenanigans can get pretty gnarly.
|
|
|
|
|
|
This centralizes the logic for checking whether a line has a line
terminator or not.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The --pre-glob flag is like the --glob flag, except it applies to filtering
files through the preprocessor instead of for search. This makes it
possible to apply the preprocessor to only a small subset of files, which
can greatly reduce the process overhead of using a preprocessor when
searching large directories.
|
|
These flags provide granular control over ripgrep's buffering strategy.
The --line-buffered flag can be genuinely useful in certain types of shell
pipelines. The --block-buffered flag has a murkier use case, but we add it
for completeness.
|
|
This commit moves a lot of "utility" code from ripgrep core into
grep-cli. Any one of these things might not be worth creating a new
crate, but combining everything together results in a fair number of a
convenience routines that make up a decent sized crate.
There is potentially more we could move into the crate, but much of what
remains in ripgrep core is almost entirely dealing with the number of
flags we support.
In the course of doing moving things to the grep-cli crate, we clean up
a lot of gunk and improve failure modes in a number of cases. In
particular, we've fixed a bug where other processes could deadlock if
they write too much to stderr.
Fixes #990
|
|
PR #1036
|
|
|
|
|
|
|
|
|
|
This brings the changelog up to date with HEAD and rewords a few things.
|
|
This commit adds ignore::DirEntry::into_path to match
the corresponding method on walkdir::DirEntry.
|
|
Clarify that --byte-offset may be wrong if the source isn't being read
directly.
Also tweak the README a bit. And remove a damned Oxford comma.
|
|
This removes ripgrep-specific code for filtering files that correspond to
stdout and instead uses the 'ignore' crate's functionality for doing the
same.
|
|
This commit adds a new 'skip_stdout' option to the directory walker. When
enabled, it will skip yielding any directory entries that are believed to
correspond to stdout for the current process. This is useful for filtering
out 'results' in a command like 'grep -r foo > results' in order to avoid
an unbounded feedback mechanism.
|
|
|
|
These flags each accept one of five choices: none, path, modified,
accessed or created. The value indicates how the results are sorted.
For --sort, results are sorted in ascending order where as for --sortr,
results are sorted in descending order.
Closes #404
|
|
This permits callers to sort entries by their full file path, which makes
it easy to query for various file statistics.
It would have been better to provide a comparator on DirEntry itself,
similar to how walkdir does it, but this seems to require quite a bit of
work to make the types work out, assuming we want to continue to use
walkdir's sorting support (we do).
|
|
This commit adds a 'same_file_system' option to the walk builder. For
single threaded walking, it defers to the walkdir crate, which has the
same option. The bulk of this commit implements this flag for the parallel
walker. We add one very feeble test for this.
The parallel walker is now officially a complete mess.
Closes #321
|
|
|
|
|
|
This includes a new crate, winapi-util, that is now used in wincolor,
walkdir and same-file.
|
|
Fuchsia is a pain to spell.
PR #1026
|
|
You need a nightly compiler.
Ref #188
|
|
We'll want to be using the new `same_file_system` option soon.
|
|
This includes an update to walkdir 2.2.2, which includes a
`same_file_system` option.
|
|
Update clap to the latest version.
Also, drop the ansi_term dependency by disabling color output in clap's
error messages.
|
|
|
|
This commit fixes a bug where the first path always reported itself as
as symlink via `path_is_symlink`.
Part of this fix includes updating walkdir to 2.2.1, which also includes
a corresponding bug fix.
Fixes #984
|
|
This commit beefs up the package metadata used by the 'cargo deb' tool to
produce a binary dpkg. In particular, we now include ripgrep's man page.
This commit includes a new script, 'ci/build_deb.sh', which will handle
the build process for a dpkg, which has become a bit more nuanced than
just running 'cargo deb'. We don't (yet) run this script in CI.
Fixes #842
|
|
This now mentions PCRE2 support.
|
|
When emitting color, the printer wasn't checking whether the line
exceeded the maximum allowed length.
|
|
This fixes warnings and adds an additional invalid UTF-8 test that will
run on Windows.
|
