Delay search until keyboard input has stopped

[Earnestly]

When searching for a string within a large body of text using the / command it can cause be significant slow down as the search is triggered immediately on each character input, especially if the first character is something like /e....

Instead the search command could detect a short delay after each input and only consider it complete if it reaches a (configurable?) threshold. With this change I could then type, for example, /expect and only have the search trigger once the word is complete, provided I type it fast enough.