saffe@lut.fi (Petri Savolainen) (01/17/91)
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? -Saffe-
knikulainen@kontu.utu.fi (01/18/91)
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 -
jms@vanth.UUCP (Jim Shaffer) (01/19/91)
Your problem has nothing to do with using ARP or not, nor does it have anything to do with ARes. Your problem is that you CANNOT use Alias in a Startup-Sequence. Put all your Alias-es in your S:Shell-Startup file. It's the only way. That way the AShell will execute the Alias-es. (Aliases don't get inherited by new shells anyway, so you have to have them in S:Shell-Startup.) -- From the disk of: | jms@vanth.uucp | "Glittering prizes and Jim Shaffer, Jr. | amix.commodore.com!vanth!jms | endless compromises 37 Brook Street | 72750.2335@compuserve.com | shatter the illusion of Montgomery, PA 17752 | (CompuServe as a last resort)| integrity!" (Rush)