Done Parameter to ignore [Escape] for FFIND /T"XXX" in a file

Nov 14, 2011
15
0
Escape interrupts FFIND

Example: first line not using ESC during FFIND and second line ESC is pressed and no ffind matches !!!

[0][i:\wrk]ffind /K /M /U /F /T"_MSC_VER=1700" E:\Sls.vs2012.404\bin\CInst.exe & echo %_ffind_matches
1

[0][i:\wrk]ffind /K /M /U /F /T"_MSC_VER=1700" E:\Sls.vs2012.404\bin\CInst.exe & echo %_ffind_matches
0
 
May 20, 2008
10,680
83
Syracuse, NY, USA
I can reproduce something like that. During the first FFIND below, I pressed Esc several times; during the second, I didn't.

Code:
v:\> ffind /s /k /m /u /f /t"if" d:\*.exe & echo %_ffind_matches
57

v:\> ffind /s /k /m /u /f /t"if" d:\*.exe & echo %_ffind_matches
70

It's difficult to reproduce again because after doing it once, data is cached and subsequent searches happen too quickly.
 

rconn

Administrator
Staff member
May 14, 2008
11,955
133
I went back through the FFIND history - the "abort on escape" was added 10 years ago as a (multiple) user request.

So the question is why do you want to press ESC and *not* abort, and why is it a good idea to change existing behavior & make the users who originally requested it unhappy?