XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX   HIDE  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
 
             A small but comfortable hiding manager for the HP48 G

Many applications produce new files (IOPAR etc) and may bother the user.
Hiding them is possible in any directory. This feature is based on adding to
the directory a nullname or empty name, ''. A hidden (including a mullname)
are known to each commands except VARS. The main advantage of hiding files is
that hiddens are more safe against unintended overwriting or other mistakes. 
----------------------------------------------------------------------
FIRST PUBLIC RELEASE: version 1.03 
----------------------------------------------------------------------
Here the description of the Library options:

Hide  Waits for entry of variables from the current directory into a list for
      hiding these with ENTER. Hide never hides all variables of a directory
      to avoid the creation of empty looking non-empty directories. It creates
      nullnames '' with the default entry CHR_H (character H) which is only a
      dummy, but a smallest possible one. Only nullnames with CHR_H in it are
      purged in an unhiding process. 

HiV   Yields the list of hidden variables of the current directory, nullnamed
      inclusive. This list may look empty but is never empty in HOME since '' 
      then contains the Hidden Directory. If a second nullname is created in
      HOME  by Hide or "STO, only this one is executed, recalled or purged. 

"RCL  Recalls the nullname in the current directory provided there is any; if
      not then "RCL errors, in contrast to the RCL-key which is searching up
      the whole path and will certainly find a nullname in HOME because the 
      builtin Hidden Directory has a nullname as well. If HIDE is used for
      the first time in HOME it may put the Hidden Directory to the stack.

"STO  Stores an stack object in a nullname or overwrites it, in any directory.
      In HOME, a second nullname is created or overwritten (the other one is 
      the Hidden directory's name). Only a user-created nullname is recalled,
      executed or purged and remains safe in a directory even after unhiding.
      One can create own nullnamed hidden directories, but it is not obvious 
      how to manipulate them properly and therefore not recommended. It suits
      better for storing some secrete information in it. Use "STO for storing
      in '', not the STO-key which would hide all files. In case this happens
      unintensionally, use Hide with the empty list for unhiding.  

"EVL  Runs the nullnamed object first found on the path from below. If nothing
      is hidden in HOME, "EVL launches the Hidden Directory. Press VAR to have
      a look at its files and leave it with UPDIR or HOME.

UNH   Unhides all hidden variables (not the Hidden Dir, of course). If " has
      some relevant stuff in it, it is shifted to the directory end.

 "    Puts a nullname on the stack. Do never apply PGDIR to it if you aren't 
      sure that it is not the Hidden Directory - apply "RCL before. 

ALLV  Recalls *all* file names of a dir, including the possibly hidden ones.
---------------------------------------------------------------------------
 Wolfgang Rautenberg - raut@math.fu-berlin.de - www.math.fu-berlin.de/~raut                
----------------------------------------------------------------------------
HINT. A nullname can be stored into itself. Although this is not dangerous, ''
then runs an infinite loop to be stopped only by a warmstart (ON hold F3).