Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!rpi!uupsi!sunic!fuug!funic!polaris.utu.fi!kontu.utu.fi!knikulainen
From: knikulainen@kontu.utu.fi
Newsgroups: comp.sys.amiga.programmer
Subject: Re: startup with Ashell
Message-ID: <1991Jan18.003957.37186@kontu.utu.fi>
Date: 18 Jan 91 00:39:57 GMT
References: <1991Jan17.090444.13604@lut.fi>
Lines: 30

In article <1991Jan17.090444.13604@lut.fi>, saffe@lut.fi (Petri Savolainen) writes:
>  I recently got ARP1.3 and tried to make my startup so that would have some
>  commands resident (with FORCE option on) and also some aliases made.
>   s/startup-sequence :
> 
>  Ashell
>  ares blah oh shit FORCE
>  alias sh shit bl blah
>  
>  BUT, it didn't work, even if i put endcli between Ashell and ares.
>  somehow it thought the old CLI was still on and tried to perform ares and
>  alias in it. Not in Ashell as I wanted. 
>  (Is this the same when opening another CLI right from startup- (probably)
>   
> 		 What to do?

Try this:
	s:startup-sequence :

	Ashell from s:ashell.boot

	s:ashell.boot

	Ares blah oh shit FORCE
	Alias sh shit
	Alias bl blah

>  -Saffe-

- Kaitsu -