When searching with ?pattern or /pattern in a file not containing the pattern, ed incorrectly printed two '?' prompts and did not capture the expected 'no match' error
The code after edParse() returns is not supposed to do anything in this case since edParse() already does the 'no match' error (seen when repeating the search with H mode enabled)
Reintroduce old behaviour by adding a nop action in cmdtab (now edParse() can signal for no subsequent work to be done without a 'bad command' error being raised)
While here, reduce code by folding edSetCurrentLine() into cmdtab
edSetCurrentLine() is the default action if a search matches
The structure of performing a search within CalculateLine() is confusing; this could be improved later