Re: Very slow incremental search (/). (VS2010 Beta 3)
I am editing a 2000 line file, and it take about 5 - 10 seconds before the character I type on the keyboard appears on the command line when the text you are searching for does not exist.
Now unfortunately when you are trying to be quick sometimes a typo can happen and if that happens you might as well go get a cup of coffee so you can wait for your keystrokes to catch up because you can't do anything until then.
I suggest that as you type if the search string becomes not found then you stop trying to search because as you keep typing something is not all of a sudden going to match.
So if I have a file with the following text:
It was all that could be done in the time before the ancients.
And I perform this search:
It should scan the file (which will take a second in a large file) and discover it does not exist.
So when I continue to type the following characters into the search:
It will not even bother scanning the file for zl or zll because it already knows there is nothing with a z in it.
That way I can quickly realize my mistake, hit esc, and try again.