Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!harpo!floyd!vax135!ariel!hou5f!hou5e!hou5d!hogpc!drux3!ihnp4!inuxc!pur-ee!uiucdcs!parsec!ctvax!uokvax!andree
From: andree@uokvax.UUCP
Newsgroups: net.cog-eng
Subject: Re: expert-friendly: are long names a wa - (nf)
Message-ID: <4427@uiucdcs.UUCP>
Date: Sat, 10-Dec-83 20:49:07 EST
Article-I.D.: uiucdcs.4427
Posted: Sat Dec 10 20:49:07 1983
Date-Received: Tue, 13-Dec-83 03:09:56 EST
Lines: 25

#R:umcp-cs:-417100:uokvax:1800011:000:895
uokvax!andree    Dec  9 12:42:00 1983

/***** uokvax:net.cog-eng / sdcsvax!davidson /  8:46 am  Dec  5, 1983 */
If a user knows a command, they will want to enter it in as
abbreviated fashion as possible, and aside from the question of
how they learned it, they will be better off with short names.

-Greg
/* ---------- */

Greg, speak for yourself. I don't want to enter commands in the
most abbreviated fashion as possible. For example, on VMS I always
use the `type' command, even though `t' is a perfectly valid
abbreviation.  The reason is that the time to mentally translate
`type' to `t' is longer than the time it takes me to type
`type'.

The other case in which abbreviations are undesirable is in a
command script. I invariable use the full form of the VMS commands,
parameters and qualifiers in scripts, as this makes it MUCH clearer
what is going on. The other systems I use don't have this option,
unfortunately.

	<mike