Completion function installation

[Peter Stephenson <pws@xxxxxxx>]

At what point do we need to think of a better mechanism for providing
and installing completion functions?  Things which occur to me include

- people won't mind if the completion function directory is the odd
  megabyte, but won't want it to grow indefinitely with functions they
  never use
- however, very few people will bother to configure which functions get
  installed even if we provide a more sophisticated mechanism (it can
  already be done by editing config.modules)
- it's useful to be able to add newly written functions to existing
  installations easily (of course fpath means this is pretty trivial
  for anyone with any shell knowledge)
- it's useful to be able to find functions for newly installed commands
  which are specialised enough not to have completions supplied with
  the shell.

All that suggests having something like CPAN for completion functions,
but that's a lot of work and I doubt we'll get volunteers.  Adding
completions supplied by users is always going to take real work by real
human beings.  I think we have to live with the current mechanism for
now.

-- 
Peter Stephenson <pws@xxxxxxx>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************