New submission from Terry J. Reedy: 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. ---------- assignee: terry.reedy messages: 219842 nosy: sahutd, terry.reedy priority: normal severity: normal stage: test needed status: open title: Idle: hilite search terms in hits in Find in Files output window type: enhancement versions: Python 2.7, Python 3.4, Python 3.5 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21673> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com