  The first aspect of the menuing system to grasp are two menuing tactics
  publically known as Command Stacking and Command Linking.  Both of these
  allow multiple commands to be executed from a single key entry, but both
  opperate very differently.

  Command stacking is generally the easiest to use and most popular multi-
  opperational single key system.  This method allows multiple commands to
  be listed in the same string but seperated by the semicolon character (;).
  This process of having several commands listed together in the same string
  makes editing them faster and easier (obviously).  An example of a command
  stack is the following:

       .,@$: "^L;@F;@R"

  Which first clears the screen ("^L"), sends the sysop matrix feedback ("@F")
  and then redisplays the matrix menu ("@R").  Note, if you are using a menu
  command which requires parameters, there are NO spaces entered after the
  menuing command.  Here is how a parameter stacked string works:

       .,@$: "COMMMANDparam;COMMANDparam;COMMANDparam", etc.

  This makes Infusion's menuing system extremely flexible and powerful by
  providing unlimited command execution at your fingertips.

  The other multicommand execution mechanism is Command Linking.  This process
  is not half as complicated, but instead involves creating multiple menuing
  commands with the same user entry key.  So to do the same "^L;@F;@R" in
  a linked commandset would invlove 3 seperate menu commands, all with the
  same entry key, with the first one command "^L", the second one "@F" and
  third "@R".  This process can also be used in conjunction with Command
  Stacking if there is not enough room for you in the entry box in the menu
  editor for the specific command.

  Menus are edited online, in the Infusion Menu Editing System.  Infusion's
  menu editing has been designed with the sysop's ease of use and understanding
  in mind, but with much more configurability than ANY other.
