_E_n_v_i_r_o_n_m_e_n_t_ _v_a_r_i_a_b_l_e_s_ _u_s_e_d_ _b_y_ _M_i_r_a_n_d_a
 (This section may be of particular interest to  installers  and  system
administrators)

The behaviour of the `mira' program is  sensitive  to  the  settings  of
certain environment variables.

An alternative location for the miralib directory may  be  specified  by
setting  the  environment variable "MIRALIB".  An explicit -lib flag, if
present, overrides this.

The  first time it is called (i.e. if no .mirarc file is present, either
in the home directory or in miralib) the miranda  system  picks  up  the
name  of  the  resident editor from the environment variable EDITOR - if
this is not set it assumes `vi'.

If the environment variable RECHECKMIRA is set (to any non-empty string)
the  Miranda  system  rechecks  to see if any relevant source files have
been updated, and performs any  necessary  recompilation,  before  every
interaction  with the user - this is the appropriate behaviour if an (eg
emacs) editor window is being kept open permanently during  the  Miranda
session.   If  this  environment  variable  is  not  set,  the  check is
performed only after `/e' commands and `!' escapes.

To decide  what  shell  to  use  in  `!'  escapes,  mira  looks  in  the
environment  variable  SHELL (this will normally contain the name of the
user's login shell).  If no SHELL is entered in the environment, /bin/sh
is assumed.

For displaying pages of the manual mira uses the program entered in  the
environment  as  VIEWER  -  if  this  variable is not set it uses either
`/usr/ucb/more -d' (Berkeley UNIX) or `/usr/bin/pg -e' (system 5).

The manual reading system is also sensitive to the settings of two other
environment  variables,  MENUVIEWER and RETURNTOMENU.  If you set VIEWER
to something else, you may also need to  set  the  environment  variable
RETURNTOMENU.  More information about this may be obtained by typing
	???
to the "next selection" prompt of the manual system.

The manual system clears the user's screen before displaying a  contents
page  and before each invocation of VIEWER - it finds out how to do this
by looking in  the  termcap  (Berkeley  UNIX)  or  terminfo  (system  5)
database.   If  there  is  no  appropriate TERMCAP/TERMINFO entry in the
environment a warning message is printed each time you enter the  manual
system.

_H_o_w_ _t_o_ _s_e_t_ _a_n_ _e_n_v_i_r_o_n_m_e_n_t_ _v_a_r_i_a_b_l_e_ _i_n_ _y_o_u_r_ _U_N_I_X_ _s_h_e_l_l_:
 (Reminder/tutorial information)

Example, setting the environment variable VIEWER to /usr/local/view

 (i) if you use the Bourne shell (usual on system 5)
      say at the UNIX command level (i.e. before calling Miranda)

      VIEWER=/usr/local/view; export VIEWER

      to make it permanent add this line to your .profile

 (ii) if you use the C shell (usual on Berkeley UNIX)
      say at the UNIX command level (i.e. before calling Miranda)

      setenv VIEWER /usr/local/view

      to undo the above say `unsetenv VIEWER',
      to make it permanent add the setenv line to your .login

