XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX HIDE XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

A small but comfortable hiding manager for the HP49

Many applications produce new files (IOPAR etc) and may bother the user.
Hiding them is possible in any directory. This is based on adding a nullname
or empty name to the directory. Hidden files (including mullnames) are known
to each command except VARS. A main advantage of hiding files is that hiddens
are more safe against unintended overwriting or other mistakes. Hidden files
are known to the Filer and one may also use the hiding tools of the latest
edition of Filer1 or Filer2 (on this site). But the HIDE library is slightly
more comfortable than other hiding tools.
----------------------------------------------------------------------
New in version 9.2002: Command menu reorganized, with a second page. Default
entry in a nullname is now a character. Backward compatibilty is granted if
no single HIDE command had been assigned to a key or is elsewhere integrated.
OT49 has no hiding commands anymore. If such thing occurs in a UsrRPL-program,
edit it and recompile with ENTER. That should make from it a HIDE lib command.

New in version 4.2001: Library number has been changed from 263 to 273.
----------------------------------------------------------------------
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 the dummy CHR_H in a nullname
is purged when unhiding with UNH, see below.

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 unvisible in the filer. If "RCL
is used for the first time in HOME it may recall the Hidden Directory.

"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 better
suits for storing other things. Use "STO for storing in a nullname '',
not the STO-key which hides all files. If this happens unintensionally,
use UNH below for unhiding the files of the directory.
.

"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).