Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU (Carl J Lydick)
Newsgroups: comp.os.vms
Subject: Re: TPU
Message-ID: <880604090034.16a@CitHex.Caltech.Edu>
Date: 4 Jun 88 16:09:03 GMT
References: <1801*stokes@cmc.cdn>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 18


 > Is there a way to pass parameters to TPU (as in P1 and P2 etc..) when
 > it is invoked something like:
 > 
 >  $ edit/tpu/display/section=evesecini/command=domything.tpu banana.txt 123
 > 
 > I want the command file domything.tpu to accept a line number (123) from the
 > command line (instead of TPU prompting for it) and do whatever to it.

No.  The command-line parser won't allow two arguments; it accepts only one, of
type $INPUT_FILE (or something like that).  You COULD get around that problem
by putting a set of quotes around ALL your arguments. i.e.,
  $ edit/tpu/display/section=evesecini/command=domything.tpu "banana.txt 123"
but then the startup procedure in the section file would try to read in
the file "banana.txt 123", and, of course, fail.

What you could do is to write a procedure that overrides the default startup
procedure, compile it, save the result in your own section file, then use:
  $ edit/tpu/display/section=my_evesecini "banana.txt 123"