Message219842
Example that prompted this idea due to difficulty of scanning results. The code lines are relatively long and the hit range from first to (almost) last word in the line.
Searching 'future' in F:\Python\dev\2\py27\*.c...
...
F:\Python\dev\2\py27\Mac\Modules\cg\CFMLateImport.c: 53: // future expansion of the APIs for things like CFMLateImportSymbol
F:\Python\dev\2\py27\Modules\_ctypes\libffi\src\dlmalloc.c: 3715: /* On failure, disable autotrim to avoid repeated failed future calls */
F:\Python\dev\2\py27\Modules\fcntlmodule.c: 235: behavior will change in future releases of Python.\n\
...
Hits found: 130
I presume that is should be easy to tag hits both in first line (instead of marking with '') and the remainder and lightly color all tagged items.
When a test is a added to test_grep, the file should be examines to see what else is still missing in light of the recent addition of an htest. |
|
Date |
User |
Action |
Args |
2014-06-05 20:09:58 | terry.reedy | set | recipients:
+ terry.reedy, Saimadhav.Heblikar |
2014-06-05 20:09:58 | terry.reedy | set | messageid: <1401998998.56.0.521906820097.issue21673@psf.upfronthosting.co.za> |
2014-06-05 20:09:58 | terry.reedy | link | issue21673 messages |
2014-06-05 20:09:58 | terry.reedy | create | |
|