portsnap

[Robert Bonomi]

> From owner-freebsd-questions at freebsd.org  Tue Nov 20 03:17:25 2012
> To: freebsd-questions at freebsd.org
> From: jb <jb.1234abcd at gmail.com>
> Subject: Re: portsnap
> Date: Tue, 20 Nov 2012 09:15:16 +0000 (UTC)
>
> Robert Bonomi <bonomi <at> mail.r-bonomi.com> writes:
>
> > ...
> > > > > > > > You gave portsnap two commands - one succeeded and the 
> > > > > > > > other failed.
> > > > >
> > > > > Nope. I gave ONE command: 'portsnap fetch update'.
> > > >
> > > > FALSE TO FACT.
> > >
> > > No way. UNIX command (on a command line, also called CLI), is 
> > > anything between prompt
> >
> > *NOBODY* said "Unix command".  _You_ falsely imputed that meaning to 
> > the respondants use of the word in a context with a different 
> > applicable meaning.
> >
> > 'command' has many meanings -- *especially* in the Unix environment.
> >
> > [drivelectomy]
> >
> > You persist in repeating your error.
> > ...
>
> Well, yes - CLI applies to many environments (not only OSs), with the 
> same basic format.
>
> http://en.wikipedia.org/wiki/Command-line_interface
> ...
> The general pattern of an OS command line interface is: prompt command 
> param1 param2 param3 ... paramN

No argument -- for _that_ meaning of the word.  That, however, is not
the only valid usage or interpretation of it.

The truth that you refuse to acknowledge is that in *many* cases, one or
more of the 'params' on the command line are commands TO THE APPlICATION
BEING INVOKED.
> A simple CLI will display a prompt, accept a "command line" typed by the 
>  [drivelectomy]
> So, we are discussing here things that are obvious. People who write 
> technical or user manuals should have a clue of what they are writing and 
> talking about (e.g. what is "a command", also called "an entry"). 
> Otherwise they screw up the users and "it's a software error" sysadmins. 

the authors of the portsnap docs (and the _numerous_ other applications
that describe the use of certain keywords used as input to that appication
ARE correct -- despite your boneheaded denial of that fact.

A "command" specifies, to the application to which it is directed, _what_
(or _which_, if you prefer) operation/activity/function is to be performed.
In grammar terms it is a =verb=.

A 'parameter'/'option'/'switch'/etc. instructs the application to which it 
is directed to , _how_ to perform the particular action.  It _modifies_ the
action to be performed.  In grammar terms it is an =adverb=.

This distinction has been known to, understood, and employed by those who
write/read/use technical instructions for well over THREE HUNDRED years.
(early multi-function machinery, such as a crane, could only perform one
action at a time -- e.g. traverse, adjust boom, lift; you moved one set
of controls to command the machine _which_ action to perform, and then
another set of controls to ccntrol how it is done.