| grep parser / search tool usability [message #156758] |
Tue, 25 October 2005 15:02 |
Eclipse User |
|
|
|
Originally posted by: eclipse.dharty.com
Not sure where this falls, but I added grep as an external tool because
I don't like the search tool usability.
Location: C:\usr\cygwin\bin\grep.exe
WorkingDirectory: ${container_loc}
Arguments: -rn ${selected_text} *.[ch]*
"Searching" the files in a workspace for
GuidoStateVectorReportElementPointer gives me:
FLTPARAM.c - FlightSw/src
PldRptng.c - FlightSw/src
Rptrcvr.c - FlightSw/src
RptUtil.c - FlightSw/src (2 matches)
RptUtil.h - FlightSw/src
Its great that I can see how many occurrences of something there are in
a file, but I would prefer to see the line item like in grep:
FLTPARAM.c:3035: return GuidoStateVectorReportElementPointer
PldRptng.c:137: return GuidoStateVectorReportElementPointer
RptUtil.c:194: double* GuidoStateVectorReportElementPointer
RptUtil.c:271: } // GuidoStateVectorReportElementPointer
RptUtil.h:47:double* GuidoStateVectorReportElementPointer(
Rptrcvr.c:379: pVal = GuidoStateVectorReportElementPointer(
Here, I can easily see the context of the match and decide which match
it is that I am interested in. The "Search" tool forces me to open up
each file, and then step to each occurrence in each file to find the one
I want.
So I have two questions:
First, is there a way to get "search" to output the line context?
Second, if not, is there a way I could right a parser for grep that
would allow me to click on grep results and go to the file and
linenumber? I've written an error parser before, but grep results
aren't really errors as such, right?
Thanks,
David
|
|
|
Powered by
FUDForum. Page generated in 0.05299 seconds
Home