"csearch -n" output is 0-based, not 1-based

[GoogleCodeExporter]

Maybe this works as designed, but it caught me off guard. The line numbers 
reported by "csearch -n" seem to start at 0 instead of 1. This is at odds with 
e.g. grep, to which csearch compares itself in its help output. This makes it 
somewhat awkward to use "csearch -n" in emacs (and presumably other editors) 
since it numbers its lines starting at 1.

Original issue reported on code.google.com by austin.bingham on 11 Oct 2012 at 10:41

• Merged into: cgrep line numbers are 0-indexed #4

[GoogleCodeExporter]

This was fixed in 
http://code.google.com/p/codesearch/source/detail?r=409f3e2a1a0d84a7c692aa7530d3
17f931c496e7 , but no new binary release has been produced.  Building your own 
from source will fix this issue, and provide a few other fixes that have been 
commited since January.

If you have Go installed, try running:
go get code.google.com/p/codesearch/cmd/{cindex,csearch}

Original comment by dgryski on 11 Oct 2012 at 1:04

• Changed state: Duplicate