Shell commands like to OS/2 shell (or MS PowerShell)
bdwheele at indiana.edu
Wed Apr 21 00:18:02 UTC 2010
On Tue, 2010-04-20 at 10:00 +0300, Slava Zanko wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Frank Murphy wrote:
> > Bookmark this: http://ss64.com/bash/
> I know about :) This idea just try for standartization of command
> names... I know about posix and LSB, but these standards don't make
> logic in the names of commands. Okay, as I see, this idea don't have
> interest for most...
> To All: in any case, thanks for attention.
Honestly it doesn't effect me since my brain has long since been molded
into the unix way, but what about this as an alternative idea:
In addition to dumping out options when --help is specified, perhaps an
option like --helpxml could be added (maybe even generated from the gnu
getopts data) to dump out information about how the program is used as
well as the options. Then a gui tool or other front end could parse
that XML and generate an interface for the end users. AIX (I think)
used to have that for some of the more esoteric sysadmin tools, but they
were one-off wrappers. It might make it easier for some people to build
complex command lines that use lots of piping...say for parsing logs or
gunzip -fc /www/logs/access* | grep "GET /status" | cut -f 1 -d\ | sort
| uniq -c | sort -n
Or, even as a worst case, perhaps man pages could be parsed, but that is
probably a road to madness.
> - --
> WBR, Slavaz.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> -----END PGP SIGNATURE-----
More information about the devel