Better error messages for command not found (was Re: Pull in upstream before 9.1 code freeze?)

[Bruce Cran]

On 05/07/2012 10:48, Olivier Smedts wrote:
> And it really annoys me too because usually, instead of an immediate
> "command not found", you've got a reply seconds later if on a not so
> fast computer. When working on Ubuntu, after a typo or missing command
> I have the time to realize that something strange is happening, to
> read again what I typed and to hit ^C before any message is displayed.
>

That annoys me too. The openSUSE guys worked on the same problem 
(https://bugzilla.novell.com/show_bug.cgi?id=435160), going from a few 
seconds down to 700ms and got told they'd need to do better :)
In the end they added a COMMAND_NOT_FOUND_AUTO variable, disabled by 
default, to do the slow search, and the standard behaviour became to 
print a message similar to "Command not found. If this isn't a typo, run 
"cnf <command>" to find the package containing it" which is a solution I 
like.

-- 
Bruce Cran