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/
& list()
 
  Syntax: list(<list>, <eval>[, <delim>])

  This function is exactly like iter() but serves a specialized 
  purpose: MUX has a buffer limit, and for things like lists of 
  players, iter() can quickly become inadequate, since the output is 
  cut off before the listing is finished. The normal way to handle 
  this is to use a @dolist/@pemit combination, but that takes many 
  queue cycles. list() takes <list>, <eval>, and an optional 
  delimiter, and evaluates them exactly like iter(). The difference 
  is the output: iter() produces a space seperated list, while list() 
  outputs each  list item on a new row of the screen.
 
	Note: This is a side effect function. It does not return anything, 
	instead, it prints its output directly to the screen of the player 
	causing the function to be evaluated. Since it does this, it is not 
	hampered by the buffer limit.
 
  See Also: iter(), @dolist, parse()