From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <df49a7370711090645u5e6c1ac6h82ab046d2068ba8c@mail.gmail.com>
Date: Fri,  9 Nov 2007 14:45:34 +0000
From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] cpu(1) design...
In-Reply-To: <509071940711090640y7dd8f2d7u1605033984cacde3@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <691e7ca02963cc4348bfb160ec4357de@quintile.net>
	<509071940711090640y7dd8f2d7u1605033984cacde3@mail.gmail.com>
Topicbox-Message-UUID: f040ec70-ead2-11e9-9d60-3106f5b1d025

On Nov 9, 2007 2:40 PM, Anthony Sorace <anothy@gmail.com> wrote:
> On 11/9/07, Steve Simon <steve@quintile.net> wrote:
> // why does cpu not have a default argument?
>
> I'm not sure I follow what you're asking for here. $cpu *is* the
> default; if you want something else, you can give it.

i think what steve's getting at is: why doesn't cpu take
any non-flagged command-line arguments?

i have to say i've been caught out in the past by doing:

    cpu netstat

rather than:

    cpu -c netstat

but you live and learn.