🚀 go-pugleaf

  
   About LVRC variable problems with various shells.... 
  
  
   When I ported Levee to the ST (late 1985...), I didn't have access to any 
other shells or anything, and there wasn't any getenv() available for the 
machine or for alcyon C.  So I wrote one, using the prototype environment in 
the bios listing as the form to make the environment like.  The prototype 
environment is 'VAR='{null}'VALUE'{null}....  And certain shells/libraries 
(dlibs, JSH, MWC-shell, and apparently the BDT shell) produce an environment 
of the form 'VAR=VALUE'{null}.  So, Levee will just laugh at those 
environment variables. 
  
   But that is likely to change, because I've found some situations where 
my old environment readers will fail. (running nested teeny-shells under 
STadel while a copy of Turbodos is sitting in the background makes my 
environment reader very unhappy, for example.  And let's not talk about 
Amulti and my environment reader, shall we?)  So, in the grand tradition of 
all shareware programmers, I'm gonna STEAL* a getenv()/putenv() from dlibs 
and stuff it into the Levee and the teeny-shell and all that.  (and maybe 
I'll even put in a workaround for the GEM console-input-overrun bug while I'm 
at it - MUMBLE!) 
  
    But for right now... Well, (shrug), I guess you'll haveta suffer; or use 
the teeny-shell. 
  
                                       -orc 
                                       -david parsons 
                                       -orc@pell.UUCP 
                                       -orc@pell (6123779239) 
                                       -etc.