Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 05 Aug 2012 18:29:50 +0100
From:      Bruce Cran <bruce@cran.org.uk>
To:        Olivier Smedts <olivier@gid0.org>
Cc:        freebsd-hackers@freebsd.org, Mike Meyer <mwm@mired.org>
Subject:   Re: Re: Better error messages for command not found (was Re: Pull in upstream before 9.1 code freeze?)
Message-ID:  <501EAD8E.2000505@cran.org.uk>
In-Reply-To: <CABzXLYMQL45jL0zadC22%2BHAvz7xP8g1G-smg8yku2TQR85V8KA@mail.gmail.com>
References:  <86bojxow6x.fsf@ds4.des.no> <4FF35864.5030109@FreeBSD.org> <CAC8HS2Hx%2BqV1zYSzyM6wYzbyA6BStd3HEwc-VDhv40DHM=qCvw@mail.gmail.com> <CAOjFWZ5ikPz_yDhEQutiXVG354qRHYJTn-M_S4Cx-=YRgFP7eQ@mail.gmail.com> <20120704185104.GA42355@DataIX.net> <4FF4B36A.2040608@FreeBSD.org> <20120704180134.7c649e1b@bhuda.mired.org> <4FF4BEED.10103@FreeBSD.org> <20120704225519.GB19945@DataIX.net> <4FF4CAD1.8080804@FreeBSD.org> <20120704234104.GA392@DataIX.net> <8E9DECBB-3D1E-4129-A958-9DB0DF69ECC3@kientzle.com> <4FF4E105.50502@FreeBSD.org> <20120704203711.2732b645@bhuda.mired.org> <2EA305F0-87D9-47BE-B3E6-366659BF77AF@kientzle.com> <20120704214216.29085927@bhuda.mired.org> <CABzXLYMQL45jL0zadC22%2BHAvz7xP8g1G-smg8yku2TQR85V8KA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?501EAD8E.2000505>