chas@gtss.gatech.edu (Charles Cleveland) (03/19/89)
In article <45@xenlink.UUCP> deraadt@xenlink.UUCP (Theo A. DeRaadt) writes:
)So, every day. Unix. Amiga. Unix. Amiga. You don't get used to how
)bad the Amiga commands are.
) <tdr.
What a wimp.
Every day. Unix. AmigaDOS. VMS. NOS. NOS/VE. CTSS. Sun
keyboard. VT240 keyboard. Amiga 1000 keyboard. IBM-PC keyboard (or
almost equivalently, IRIS keyboard). Editing using FSE, EDIF, vi, emacs,
EDT, and several little custom numbers the irrepressible-reinventers-of-the-
wheel at MFECC churned out. With a little experience, working in multiple
environments becomes second nature. The only real problem I have is using the
IBM-PC keyboard -- whoever designed that zonker should be strung up at COMDEX
and allowed to twist in the wind.
Unix is not the only other OS on the planet besides AmigaDOS. If Unix and
AmigaDOS wildcard conventions converged, I would hardly notice. The Amiga
commands are fine.
The biggest problem is changing machines (or OS's) without changing
'terminals'. Please, Commodore, make it OBVIOUS whether the user is using
UNIX or AmigaDOS. It would really help us make the context switch.
The suggestion:
The wildcard.library proposed in this group (seems like a nice project,
doesn't it?) could be made to work with an environment variable which indicates
which wildcard.library (standard AmigaDOS, the default. UNIX. whatever.)
the user wants to use. The application checks the env. variable and tries to
open the appropriate library. We would just have to agree what the functions
in such a library should be called and what they should return. Is it as
simple as one external routine called ParseWildCard() that accepts one
char *argv[] as input, and for output an char **argv2[] and a char *string to
hold the parsed input line (and I guess we better also input the maximum
number of parsed arguments and the maximum number of characters in the parsed
input line)? Other suggestions or ideas?
Of course, it would have to be supported by Commodore, since their commands
would have to check the environment variable too. But people using both
AmigaDOS and UNIX on the same machine might regard this as a real feature.
--
"Our vision is to speed up time, eventually eliminating it." -- Alex Schure
Charles Cleveland Georgia Tech School of Physics Atlanta, GA 30332-0430
UUCP: ...!gatech!gtss!chas INTERNET: chas@gtss.gatech.edujbwaters@bsu-cs.UUCP (J. Brian Waters) (03/20/89)
In article <396@gtss.gatech.edu>, chas@gtss.gatech.edu (Charles Cleveland) writes: > The suggestion: > The wildcard.library proposed in this group (seems like a nice project, > doesn't it?) could be made to work with an environment variable which indicates > which wildcard.library (standard AmigaDOS, the default. UNIX. whatever.) Since I have seen numorous references to a wildcard.library and no one mention arp.library, I thought I would do so. The arp.library contains wilcard routines. And they do read an environmental to turn on and off the '*' as a wildcard. If you want your commands to support this you use the Arp commands. If you are happy with the AmigaDOS wildcards and just want to add them to your programs you use the library calls. Note that you CAN use the library even if you do not want to use the commands... and the release of the 1.3 version of Arp seems eminent. -- Brian Waters <backbone>!{iuvax|pur-ee}!bsu-cs!jbwaters
deraadt@xenlink.UUCP (Theo A. DeRaadt) (03/20/89)
In article <396@gtss.gatech.edu|, chas@gtss.gatech.edu (Charles Cleveland) writes: | In article <45@xenlink.UUCP| deraadt@xenlink.UUCP (Theo A. DeRaadt) writes: | )So, every day. Unix. Amiga. Unix. Amiga. You don't get used to how | )bad the Amiga commands are. | ) <tdr. | | What a wimp. | | Every day. Unix. AmigaDOS. VMS. NOS. NOS/VE. CTSS. Sun | keyboard. VT240 keyboard. Amiga 1000 keyboard. IBM-PC keyboard (or | almost equivalently, IRIS keyboard). They all have the keyboard coming out the front, and the spacebar is always in the same place. I also hate unix terminals that don't have an ESC key in the proper place. A friend who uses Dvorak, finds himself switching to Qwerty and back whenever he hits one of those keys which are the same. Wimpy? | Editing using FSE, EDIF, vi, emacs, | EDT, and several little custom numbers the irrepressible-reinventers-of-the- | wheel at MFECC churned out. With a little experience, working in multiple | environments becomes second nature. The only real problem I have is using the | IBM-PC keyboard -- whoever designed that zonker should be strung up at COMDEX ^^^^^^^^^^^^^^^ - Amiga wildcards | and allowed to twist in the wind. I have an emacs on every machine I use too. Does that make me a wimp too? | Unix is not the only other OS on the planet besides AmigaDOS. If Unix and | AmigaDOS wildcard conventions converged, I would hardly notice. The Amiga | commands are fine. I want wildcards that are easy to type; and all the commands should understand them. Unix wildcards are consistant, powerful, and easy. Darn it, make it simple, don't make me type all sorts of silly punctuation marks in hard to reach places, if there is an easier way. The only real reason I have heard yet for keeping things the same is that "*" is the console. <tdr.