Age | Commit message (Collapse) | Author |
|
It appears to be intermittently failing. Specifically, a2x seems to be
failing occasionally with no apparent reason why. The error message it
gives is inscrutable. Sigh.
|
|
It looks like `is_simple` wasn't quite correct.
I can't wait until this code is rewritten. It is still not quite clearly
correct to me.
Fixes #1537
|
|
PR #1536
|
|
In particular, this appears to fix an extremely annoying bug that was
causing PR builds to fail if they were re-run.
For more details:
https://github.com/actions/checkout/issues/23#issuecomment-572688577
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Add support for Gentoo's portage package manager spec files:
https://wiki.gentoo.org/wiki/Portage
|
|
It looks like a2x isn't working, so take a shot at fixing it.
|
|
|
|
|
|
In a prior commit, we fixed a performance problem with the -w flag by
doing a little extra work to extract literals. It turns out that using
literals in this case when the -w flag is NOT used results in a
performance regression. The reasoning is that we end up using a "fast"
regex as a prefilter when the regex engine itself uses its own
equivalent prefilter, so ripgrep ends up redoing a fair amount of work.
Instead, we only do this extra work when we know the -w flag is enabled.
|
|
PR #1528
|
|
... and don't replace them with anything because crates.io does not
support GitHub Actions yet. But it's almost there:
https://github.com/rust-lang/crates.io/pull/1838
Thanks @atouchet for noticing this.
|
|
This fixes fallout from fixing #1520.
|
|
We should not assume that the commondir file actually exists. If it
doesn't, then just move on. This otherwise emits an error message when
searching normal submodules, which is not OK.
This regression was introduced in #1446.
Fixes #1520
|
|
|
|
|
|
This is consistent with prior releases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This also updates the corpora used, so previous times (and counts) are
not comparable.
We also remove some tools, likt pt, sift and ucg, since they appear to
be no longer maintained. ag isn't really maintained either, but it still
has significant mind share, so we retain a benchmark for it.
We also upgrade ack to version 3, and remove the clarification on how
`-w` is implemented.
We also add `git grep -P` (uses PCRE2) which appears to be much faster
than `git grep -E`.
Finally, we add ugrep which is a new up and comer in this space.
Fixes #1474
|
|
If a literal is entirely whitespace, then it's quite likely that it is
very common. So when that case occurs, just don't do (inner) literal
optimizations at all.
The regex engine may still make sub-optimal decisions here, but that's a
problem for another day.
Fixes #1087
|
|
|
|
The purpose of this flag is to force ripgrep to ignore all --ignore-file
flags (whether they come before or after --no-ignore-files).
This flag can be overridden with --ignore-files.
Fixes #1466
|
|
Fixes #1442, Fixes #1478
|
|
It doesn't really belong in the man page since it's an artifact of a
build/runtime configuration. Moreover, it inhibits reproducible builds.
Fixes #1441
|
|
Fixes #1439
|
|
This permits switching between the different regex engine modes that
ripgrep supports. The purpose of this flag is to make it easier to
extend ripgrep with additional regex engines.
Closes #1488, Closes #1502
|
|
This is in preparation for adding a new --engine flag which is intended
to eventually supplant --auto-hybrid-regex.
While there are no immediate plans to add more regex engines to ripgrep,
this is intended to make it easier to maintain a patch to ripgrep with
an additional regex engine. See #1488 for more details.
|
|
|
|
This adds one new dependency, maybe-uninit, which is brought in by
crossbeam-channel[1]. This is to apparently fix some unsound code
without bumping the MSRV. Since ripgrep uses the latest stable release
of Rust, the maybe-uninit crate should compile down to nothing and just
re-export std's `MaybeUninit` type.
[1] - https://github.com/crossbeam-rs/crossbeam/pull/458
|
|
This corrects an oversight when the repo was re-organized to
have its crates moved into a 'crates' sub-directory.
PR #1505
|
|
PR #1504
|
|
It's not clear why removing this makes things work. I've submitted
PRs that passed CI with fetch-depth=1. Maybe it only fails when
PRs are submitted from external contributors?
Either way, for now, we remove this and absorb the extra cost in
order to get PRs passing CI again.
PR #1501
|
|
The existing vagueness was not enough to prevent people from lawyering
me over it.
|
|
PR #1492
|
|
|
|
Again, thanks to @zsugabubus!
|
|
We can just ask the channel whether any work has been loaded. Normally
querying a channel for its length is a strong predictor of bugs, but in
this case, we do it before we ever attempt a `recv`, so it should work.
Kudos to @zsugabubus for suggesting this!
|
|
|