btmux-0.6-rc4/doc/
btmux-0.6-rc4/event/
btmux-0.6-rc4/game/
btmux-0.6-rc4/game/maps/
btmux-0.6-rc4/game/mechs/
btmux-0.6-rc4/game/text/help/
btmux-0.6-rc4/game/text/help/cat_faction/
btmux-0.6-rc4/game/text/help/cat_inform/
btmux-0.6-rc4/game/text/help/cat_misc/
btmux-0.6-rc4/game/text/help/cat_mux/
btmux-0.6-rc4/game/text/help/cat_mux/cat_commands/
btmux-0.6-rc4/game/text/help/cat_mux/cat_functions/
btmux-0.6-rc4/game/text/help/cat_templates/
btmux-0.6-rc4/game/text/wizhelp/
btmux-0.6-rc4/include/
btmux-0.6-rc4/misc/
btmux-0.6-rc4/python/
btmux-0.6-rc4/src/hcode/btech/
btmux-0.6-rc4/tree/
& @pemit
 
  Syntax: @pemit[/switches] <what>=<message>
 
  Emits <message> only to <what>, or to <what>'s contents of the
  /contents switch is given.  <what> must be either in the same 
  location as you or be something you own.  You can also @pemit to 
  distant players if pagelocks allow you to page them, and this 
  costs as much as a page <This feature is not present in all 
  MUXes>.  You cannot @pemit to the contents of something you don't 
  own.
 
  The following switches are available:
    /contents - Send the message to the contents of the named object.
    /object   - Send the message to the named object.
    /list     - Send the message to a list of objects.
 
  You may specify any combination of these switches.
  
  See also: page, @remit, @emit, @oemit, SPOOFING