website

The "print lines by number" was there because earlier versions of ack had a `--line=N` feature, where you could say "ack --line=15-18" and print those four lines. I dropped it because it was hardly any better than using sed. If you've got suggestions on improvements, please submit an issue. I'd love to hear them. https://github.com/beyondgrep/website/issues

That's how I had it at first. I originally had it as a "phrasebook" of how to do the same thing in the different tools, but it was really ugly and took up a lot of horizontal space, and I figured it was more useful as a chart of yes/no. Also, there were cases where two tools had pretty much the same feature, but not exactly, so just listing flags didn't make sense. I've still got a lot of the data of the switches in the JSON file that I build the chart from. https://github.com/beyondgrep/website/blob/dev/features.json If you've got ideas on how to bring back the phrasebook format, either integrated into this page, or as a separate standalone page, I'd love to hear them. Maybe the phrasebook isn't best done as a table like this, for example. Open a ticket in GitHub and let me know your thoughts.

You can update the page with pull requests to this repo: https://github.com/beyondgrep/website

Please note that the chart is a bit out of date. ripgrep has some features that aren't shown on the chart yet. Patches welcome if anyone wants to help. https://github.com/beyondgrep/website

That table is quite out of date for ripgrep, which has added a number of features. See: https://github.com/beyondgrep/website/issues/97

Please let me know what's new so that I can update the chart. Dumping into an issue will do, and then I can worry about getting it into chart format. https://github.com/beyondgrep/website/issues

I'm going to be making a new chart that is more about features than command flags. I'll include the licensing information. Thanks. https://github.com/beyondgrep/website/issues/80

It's going to be two pages ultimately. If you're comparing features, you don't care about the how. Right now we're keeping all the data in a JSON file that we massage into a chart. Massaging it into a true feature comparison chart, along with a rosetta stone, should be a simple matter of programming. Same thing with the GNU/POSIX/BSD rosetta stone we're working on. https://github.com/beyondgrep/website/blob/dev/comparison.js...

The table doesn't yet distinguish between lacking a command line flag due to absence of a feature vs due to the feature being the default. This is similar to the situation with case-sensitive search in GNU grep, which ends up with a blank cell even though it is the default. See: https://github.com/beyondgrep/website/issues/72 It's a fair criticism but I don't think it is designed to be misleading.