taylor@sdcsvax.UUCP (Dave Taylor) (08/28/83)
Contrary to what some people might think (no names mentioned) adding input flags to allow the user to get more verbose output is NOT a valid solution to the interactive problem of UNIX...because the more flags there are, the more intimidating it is for the novice (and indeed the expert) user. How many people KNOW all (ALL) the input flags and combinations to the 'ls' program, for example?? Perhaps if the routines defaulted to a interactive "help" interface, then the flags could turn it off to a varying degree... -- Dave Taylor UCSD Computer Science Dept.
speaker@umcp-cs.UUCP (08/31/83)
I think all programs should respond to a common set of flags.
Examples:
program '--' # Gives you help.
program <bad flag> # Says "Type program '--' for help."
program -<flag> # Subtract attribute like in chmod.
program +<flag> # Add attribute like in chmod.
program - # Force standard input.
Incorrect use of a program generates a "Usage" message, and
program should handle signals in an intelligent way.
Bill-yuns and bill-yuns of flags is okay by me.
I know, I know, you're saying to yourself, "Hey that defeats
the philosophy of Unix with its small simple programs."
Well, maybe. But you can stil have each program operate
in a simple manner when it is used WITHOUT all of the options.
- Speaker
--
Mundane-Name: John T. Nelson
Full-Name: Speaker-To-Animals
UUCP: {seismo,allegra,brl-bmd}!umcp-cs!speaker
CSNet: speaker@umcp-cs
ARPA: speaker.umcp-cs@UDel-Relaysilver@csu-cs.UUCP (09/07/83)
Hey, verbosity by default is not such a bad idea, so long as it's something I can turn on and off (or up and down) ONCE, and have every command behave similarly in response. Like an environment variable called VERBOSE, or somesuch. Of course, asking for this degree of consistency in all (where all = 80%) of the common commands is like asking for standard flags on those commands... Speaking of which, does anyone have an across-the-board options summary? I'd like to see such a thing, just out of curiosity. My fantasy is a sorted list of every single-letter option in, say, the System III brick, with every different meaning shown once followed by a count of number of occurrences (commands which used that meaning). I for one would consult such a list when designing a new command, so as to be more, rather than less, consistent with the established pattern (realizing that it just ain't that simple, all commands are not created equal, etc.). Alan Silverstein, Hewlett-Packard Fort Collins Systems Division, Colorado ucbvax!hplabs!hpfcla!ajs, 303-226-3800 x3053, N 40 31'31" W 105 00'43"