mmalecki/ngrep — Issue #1: Script name conflicts with existing, popular script
Author: Rylab
Created: 2012-02-22 02:50:51+00:00
State: open

First off, this is a cool little utility. However in order to use it, I had to build with an alternate project name, as I already use the (no offense to you!) already widely accepted "ngrep" seen at http://ngrep.sourceforge.net and http://en.wikipedia.org/wiki/Ngrep

I totally get where the name choice came from, since it's built on Node and all. But it may make sense to rename the project officially so as not to conflict, if wider adoption is planned.

When looking into it quickly, some other obvious choices are also all taken (eg. "agrep" (async grep), my first alternate-name idea, is already taken by a script which does a fuzzy "approximate grep").

Personally, I ended up naming this script "grepa" (grep-async). Don't expect that to be officially adopted, just putting it out there in case anyone else runs into the same issue.

Also since I know this is an annoying issue, I am following it up with two simple little bug fix / error checks I added when either the script is called with insufficient args, or the target path doesn't exist.