CompuServe Messages

C Shells

#: 5030 S9/SoftwareDevelopmentForum unknown
    12-Jan-86 21:14:03
Sb: #4712-C Shells
Fm: John Foust 72237,135
To: all

This message turned up in search, but its forum couldn’t be identified from the original transcript, so it may not be linked into its thread.

Thanks for your comments, Gary and Bela. Bela: I use CED pretty heavily, and use SYN most often. I don't remember the context of my '$foo' remark. Anyway, an Amiga shell needs it. I will be posting a better shell, soon, unless someone else has already posted the Usenet MyCli. (haven't DL'd yet. What version of public domain CED do you have? Gary: I agree about the CLI problems, and the screwed up!x:ure of the CLI commands. All different, all obscure. Were you saying the '> prt:' I type is passed to the program in argv[]? ??? I've always been a bit miffed about Lattice changing argv[0] to "c", while we're at it. I remember seeing a shell of some sort that had the CTRL/F you mentioned. I think we could come up with a list of good features for a shell. Any one care to start a list? Another general question – how should we handle environment variables and paths? Should our shell constantly search logged drives with valid paths, and remember any possible programs/commands there? Boy, I hate to kludge up a nice OS like AmigaDOS CLI,but these things have to be done. 🙂 I've had more troubles with CLI / Workbench than anything else. Some documentation would hexxx help. Related question for this thread: How should Workbench level tools accept command lines? How would you implement 'grep' from the Workbench? 'more'? A print spooler? A RAM: disk icon that works? I'd like to get the name of a most recently selected icon, but have trouble with workbenchbase.h, but that;'s another story.