Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!mcsun!unido!fauern!fauern!immd4.informatik.uni-erlangen.de!mlelstv
From: mlelstv@immd4.informatik.uni-erlangen.de (Michael van Elst )
Newsgroups: comp.sys.amiga
Subject: Re: Missing k directive
Message-ID: <585@medusa.informatik.uni-erlangen.de>
Date: 20 Nov 89 13:51:37 GMT
References: <15503@bloom-beacon.MIT.EDU> <1105@forty2.UUCP> <1107@forty2.UUCP>
Organization: IMMD IV, University of Erlangen, W-Germany
Lines: 27

claudio@forty2.UUCP (Claudio Nieder) writes:

>In article <1105@forty2.UUCP> I wrote:
>Thanks to everybody who sent me mail, telling me that I probably have
>a "<" somewherer in my Shell-Startup. After cleaning up my prompt
>which contained that character everything worked well again. 

>Now I'm still wondering, why there is a difference between using the
>Shell-Icon to start it up, and using some other method.

If you use EXECUTE, then parameters are parsed by the command and subsituted
in the script. Actually a second script is generated with those substitutes.

If it is called from NEWSHELL or as a startup-sequence, you just feed
it into the CLIs standard input without ever looking at parameters or
meta-commands (.bra, .dot, .key, etc....)

I use in my startup-sequence:

EXECUTE shell-execute

and my shell-execute file comes up with .BRA { since otherwise any
io-redirections would cause a 'missing K-directive' error.

				Michael van Elst

E-mail: UUCP: ...uunet!unido!fauern!immd4!mlelstv