Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Jul 2012 15:16:07 -0700
From:      David Brodbeck <brodbd@uw.edu>
To:        freebsd-hackers@freebsd.org
Subject:   Re: Pull in upstream before 9.1 code freeze?
Message-ID:  <CAHHaOuYoN_1Thb8JXKyicQSXpwNsikWBY04a9TwiPvQvzNZo-g@mail.gmail.com>
In-Reply-To: <50048A96.5060803@jetcafe.org>
References:  <CA%2BQLa9B-Dm-=hQCrbEgyfO4sKZ5aG72_PEFF9nLhyoy4GRCGrA@mail.gmail.com> <4FF4BEED.10103@FreeBSD.org> <62039A45-92E4-4588-988D-6DF39D7B01E5@bsdimp.com> <201207050922.25815.j.mckeown@ru.ac.za> <20120705082857.GB37083@server.rulingia.com> <4FF55864.8040807@FreeBSD.org> <50048A96.5060803@jetcafe.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jul 16, 2012 at 2:41 PM, Dave Hayes <dave@jetcafe.org> wrote:
> Why not create a command wtf(1)?
>
> When you type it, it detects the shell you are using, looks at the last
> command you typed, and provides all sorts of arbitrarily verbose and usable
> documentation and suggestions as to what that command might have done, what
> the verbatim command will do, and where you can find more information.

I suspect you meant this as a sarcastic suggestion, but I actually
like it.  It reminds me of AmigaDOS's "why" command, which would give
a detailed explanation of why the previous command failed.

-- 
David Brodbeck
System Administrator, Linguistics
University of Washington



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