Previous: add Up: ../info.html Next: footnotes


 How to Create Menus:

   Any node in the INFO hierarchy may have a MENU - a list of  subnodes.
 The M command searches the current  node's menu for the topic which  it
 reads from the TTY.

   A menu begins with a line starting  with "* Menu:".  The rest of  the
 line is a  comment.  After the  starting line, every  line that  begins
 with a "* " lists a single topic.  The name of the topic - the arg that
 the user must give to the M command to select this topic - comes  right
 after the star and space, and is followed by a colon, spaces and  tabs,
 and the name of  the node which discusses  that topic.  The node  name,
 like node names  following Next,  Previous and Up,  must be  terminated
 with a tab, comma, or  CRLF.  If the node name  and topic name are  the
 same, than  rather than  giving  the name  twice, the  abbreviation  "*
 <name>::" may be  used (and should  be used, whenever  possible, as  it
 reduces the visual clutter in the menu).

   It is considerate to choose the topic names so that they differ  from
 each other very near the beginning - this allows the user to type short
 abbreviations.  In a  long menu, it  is a good  idea to capitalize  the
 beginning  of  each   item  name  which   is  the  minimum   acceptable
 abbreviation for it (a long menu is more than 5 or so entries).

   The node's listed in a node's menu are called its "subnodes", and  it
 is their "father".   They should  each have  an "Up:"  pointing at  the
 father.  It is often useful to arrange all or most of the subnodes in a
 sequence of Next's/Previous's so that someone who wants to see them all
 need not keep revisiting the Menu.

   The INFO Directory is simply the  menu of the node "(DIR)TOP" -  that
 is, node Top in file <INFO>DIR.INFO.   You can put new entries in  that
 menu just like any other menu.  The  INFO Directory is NOT the same  as
 the file directory called INFO.  It  happens that many of INFO's  files
 live on that file directory, but they don't have to; and files on  that
 directory are not automatically listed in the INFO Directory node.

   Also, although the INFO node graph is claimed to be a "Hierarchy", in
 fact it  can be  ANY  directed graph.   Shared structures  and  pointer
 cycles are perfectly possible, and can be used if they are  appropriate
 to the meaning to be expressed.  There is no need for all the nodes  in
 a file  to form  a connected  structure.  In  fact, this  file has  two
 connected components.  You are in one of them, which is under the  node
 Top; the other contains  the node Help which  the "H" command goes  to.
 In fact, since there is no garbage collector, nothing terrible  happens
 if a substructure is  not pointed to, but  such a substructure will  be
 rather useless since nobody will ever find out that it exists.