[Cialug] The Complete CLI Command, According to This Guy

[Jeff Chapin]

> If one were writing
the rules that everyone was going to follow, one might rather say "no bare
arguments where the meaning could in any way be unclear or confusing". And
any time there're two arguments, it *is* unclear and confusing.

mv --origin foo --destination bar

just doesn't seem as user friendly as 'mv foo bar' to me. User friendly is
not just about reading the command, but also *using* the command, and in
unix-land, there is a long history of commands that work in this format, so
this would be a good case of a blanket exception, imo.

On Fri, Oct 12, 2018 at 8:05 AM Todd Walton <tdwalton at gmail.com> wrote:

> On Tue, Oct 9, 2018 at 5:03 PM Adam Shannon <adamkshannon at gmail.com>
> wrote:
>
> > > * flags -- don't use bare arguments
> >
> > So now we're all going to be using  'cat --file secrets.txt' ?
> >
>
> There's probably some useful exceptions one could make. If one were writing
> the rules that everyone was going to follow, one might rather say "no bare
> arguments where the meaning could in any way be unclear or confusing". And
> any time there're two arguments, it *is* unclear and confusing.
>
> Every time I use ln I check the help or man page before I do, just to make
> sure I remember the order correctly. Every time! Is it "destination
> link-name" or "link-name destination"? And ln (inexplicably) does not let
> you flag which is which, so you have to get the order right. I tried to
> rationalize it in a way that would help it stick in my mind, but that
> didn't work. With cp and mv, for example, "copy this to there" makes sense
> to me. But ln does it the reverse of how I think about it.
>
> --
> Todd
> _______________________________________________
> Cialug mailing list
> Cialug at cialug.org
> http://cialug.org/mailman/listinfo/cialug
>


-- 
Jeff Chapin
President, CedarLug, retired
President, UNIPC, "I'll get around to it"
President, UNI Scuba Club
Senator, NISG, retired