From: arne@vajhoej.dk   
      
   On 9/20/2025 12:02 PM, Arne Vajhøj wrote:   
   > On 9/20/2025 9:15 AM, David Meyer wrote:   
   >> Digging into EVE and DECTPU I've found that you can use the EVE @   
   >> command to run a sequence of EVE commands stored in an .EVE file, and   
   >> the TPU command to run a TPU procedure defined in a .TPU file. You can   
   >> use DEFINE KEY to invoke a "@ ..." or "TPU ..." command with a   
   >> keystroke.   
   >>   
   >> Is there a way to define a custom EVE command that can be invoked   
   >> directly from the DO prompt without prefixing "@" or "TPU"?   
   >   
   > You can define EVE commands in your TPU$COMMAND file.   
   >   
   > Example:   
   >   
   > procedure eve_foo_bar   
   >      message("Hi from eve_foo_bar!");   
   > endprocedure;   
   > !   
   > procedure eve_count(n)   
   >      local   
   >          msg, i;   
   >      msg := "Counting:";   
   >      i := 1;   
   >      loop   
   >          exitif i > int(n);   
   >          msg := msg + " " + str(i);   
   >          i := i + 1;   
   >      endloop;   
   >      message(msg);   
   > endprocedure;   
   >   
   > DO + foo bar   
   >   
   > DO + count 3   
   >   
   > (the examples only output a message, but they can obviously do anything)   
   >   
   > Disclaimer: they seem to work, but I am a bit rusty in TPU - I have done   
   > very little TPU in this century.   
      
   A few more explanations.   
      
   procedure eve_xxx_yyy_zzz(a1, a2, a3)   
      
   becomes the command:   
      
   xxx yyy zzz a1 a2 a3   
      
   The TPU$COMMAND file (known as TPUINI file by 4.x people) are   
   specified as:   
      
   1) $ EDIT/TPU/COMMAND=file ...   
   2) $ DEFINE/NOLOG TPU$COMMAND file   
   3) TPU$COMMAND.TPU in current directory   
      
   Arne   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)