Path: utzoo!mnetor!uunet!mcvax!enea!ttds!draken!duvan!drs-ano
From: drs-ano@duvan.nada.kth.se (Gunnar Nordmark)
Newsgroups: comp.sys.amiga
Subject: Re: POPCLI 3 doesn't pass path, but POPCLI 2 does
Message-ID: <300@draken.nada.kth.se>
Date: 1 Mar 88 23:15:38 GMT
References: <8802182204.AA18542@decwrl.dec.com>
Sender: usenet@nada.kth.se
Reply-To: nordmark@epsilon.stacken.kth.se (Gunnar Nordmark)
Organization: The Royal Inst. of Techn., Stockholm
Lines: 37
Keywords: NewCLI
Summary: Use a login file

In article <8802182204.AA18542@decwrl.dec.com> rmeyers@tle.dec.com (Randy Meyers 381-2743 ZKO2-3/N30) writes:
>decwrl!ucbvax!husc6!ut-sally!mothra!bryan noticed that the CLI command
>path is not inherited by new CLIs started by POPCLI 3.  This is true,
>and it represents a major defect in POPCLI 3.  POPCLI 2 does not have
>this problem.   I strongly recommend that it be used instead of POPCLI 3.
>(POPCLI 2 is available on Fish disk 40.)
>
>So the best way to have your CLIs created by POPCLI properly set up is
>and to set up the state of your original CLI before RUNning POPCLI 2.
>

I use a 'login' file that sets up the environment I want whenever I pop
up a new CLI. It works great with PopCLI III.

I have this line in my Startup-Sequence:
  PopCLI 300 NewCLI >NIL: "CON:0/0/640/256/AmigaDOS ARP" S:.login

The script file .login is executed when the new CLI pops up and it
initializes the Path and everything else one can imagine. You can add
a call to the DOS command Date to the .login file. Now when you pop up the
new CLI you'll get something like:

New CLI task 2
Tuesday 01-Mar-88 21:52:44
2>

Nice isn't it?

Personally I like the idea of a command that says 'POP!' added to my
.login file :-)

---

SNAIL: Gunnar Nordmark          VOICE: 08 - 755 42 52
       Nora strand 5
       S-182 34 DANDERYD        EMAIL: nordmark@epsilon.stacken.kth.se
       SWEDEN