coxley / codesearch Goto Github PK

If one line has multiple matches, looks like it'll print it more than once with different highlights.

Filenames inline with code worked great at Facebook because paths were more predictable, and didn't need to include repo information. Files spread across repos just have a lot of duplicate paths that get spread out.

Add an option that can be set as default for rg style. Something like...

>cs foo bar baz
path/to/file.ext
70:  foo bar baz
71: baz qux

path/to/other/file.ext
69: foo bar
72: baz

This has the added benefit of allowing the header to be the full URL without impacting legibility.

I often find myself doing a search, re-running the search with --count to see if it's the full picture or not, and then running again with an increased --limit.

Automatic paging could be a solution, but GitHub is quick to rate-limit. And much of the time I just want a quick look vs. exhaustive. Letting the user know that there could be more in yellow text is a decent trade-off.

Hi Codey, this project is amazing! Missing BigGrep so much.. Do you have any plans to add GitLab support as well?

Thank you

Facebook had a few variants for BigGrep tools. The main two I remember are:

• fbgs (search)
• fbgf (file)

Currently we're discarding filename matches because we're focused on source code. But I just hit a few snags where I have only a filename to match on so... yeah.

Good code, but what an awful dev.