Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!agate!stew.ssl.berkeley.edu!johnf
From: johnf@stew.ssl.berkeley.edu (John Flanagan)
Newsgroups: comp.sys.amiga.tech
Subject: SKsh compatibility with unix or AmigaDOS (was:  Re: Using PIP:)
Summary: Unix style, please
Keywords: dupping closing pipes
Message-ID: <1989Dec19.195535.13068@agate.berkeley.edu>
Date: 19 Dec 89 19:55:35 GMT
References: <4689@sugar.hackercorp.com> <1610.AA1610@julie> <1718.AA1718@julie> <4780@sugar.hackercorp.com> <1fdu02pp76f901@amdahl.uts.amdahl.com>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Organization: University of California, Berkeley
Lines: 29

In article <1fdu02pp76f901@amdahl.uts.amdahl.com> kim@uts.amdahl.com (Kim DeVaughn) writes:
>In article <4780@sugar.hackercorp.com>, peter@sugar.hackercorp.com (Peter da Silva) writes:
>> In article <11223@thorin.cs.unc.edu> tell@oscar.cs.unc.edu (Stephen Tell) writes:
>> 
>> > But env: is deficient in that its "global" and therefore you can't have
>> > more than one environment.
>> 
>> I understand this. However you should retain compatibility with the system
>> as it exists. Similarly, your programs should use AmigaDOS keyword argument
>> handling rather than UNIX -option style, and they should work properly under
>> the Workbench and CLI as well as RogueStartup.
>
>If you opt for compatibility as Peter suggests, could you please make it
>settable.  Alot of people prefer -option style specifications.
>
>Similarly with a solution to the env: problem.

Permit me to disagree more strongly than Kim.  The whole point of SKsh,
as I understand it, is to emulate one of the Unix shells (tsh?).  There
are already plenty of shells available which stick to the Amiga Shell
model.  Lets have one for us Unix-heads.  




John Flanagan				Space Sciences Laboratory
johnf@sag4.ssl.berkeley.edu		University of California
(...!ucbvax!sag4.ssl!johnf)		Berkeley, CA 94720
Manners Maketh Man.			(415) 643-6308