•  Back 
  •  Menu commands 
  •  Index 
  •  Tree View 
  •  Cross references 
  •  %Hilfe 
  •  Show info about hypertext 
  •  View a new file 
Topic       : Documentation for Thing
Author      : Arno Welzel/Thomas Binder/TransAction
Version     : thing.hyp 1.27E (23/8/1998)
Subject     : Documentation/Shells
Nodes       : 269
Index Size  : 6336
HCP-Version : 4
Compiled on : Atari
@charset    : atarist
@lang       : 
@default    : %I
@help       : %Hilfe
@options    : +g -i -s +y +zz -t4 -d10
@width      : 75
@hostname   : THING   
View Ref-FileExtra - Applications... (Environment)                                 Thing

Some programs evaluate environmental variables on starting. One possibility 
to set such variables is to add additional entries in MAGX.INF (#_ENV), 
MINT.CNF, GEM.CNF (setenv) or one of the environment setters available for 
Single-TOS.

Thing offers the option of adding a 'local' environment for individual 
applications. Using this method the 'global' variables present are 
supplemented by the 'local' entries. One specific example of this would be 
a TOS shell or DVI viewer (specifying the TeX directories etc.).

Every entry must take the form <variable>=<value>
For example: TEX_OUTPUTS=G:\TEX\OUTPUTS\

Thing does not check entries for correct syntax, so it's up to you to 
ensure entries are meaningful!

Obviously, Thing will only use the local environment if 'Use environment' 
is active (crossed). The remaining entries here should need no explanation.


Notes for MagiC users

Unfortunately under MagiC!2 a separate environment can only be used 
for TOS/TTP programs that are executed via the Thing Console window.
For programs running in parallel this is not possible for technical 
reasons, as MagiC!2 does not yet support the required operating system 
call.

In Single mode it is generally not possible to utilise a local environment 
because Thing must be quit before the program is started.


Notes for MultiTOS users

For technical reasons transmission of local environments only seems to 
work with GEM applications. TOS/TTP programs started in parallel from 
MINIWIN.APP always seem to receive the global environment -- this happens 
with both AES 4.0 and AES 4.1.


Incidentally: Under MagiC!>=3 everything works OK -- even if the TOS/TTP 
programs are started via VT52.PRG...

Notes for Single-TOS users

Under Single-TOS a local environment is only available if Thing is not 
unloaded at program starts (remains memory resident), or if TOS/TTP 
programs are not executed via TOSWIN.ACC (under MiNT).


index=254
If a variable defined in a local environment already exists in the global one, it will not be overwritten by Thing but will be present twice. But as Thing saves the local variables at the start of the new environment they will normally take priority -- unless a program searches through its environmental variables from the end to the start, though this is virtually unheard of.