Compatibility fix: rename --shell option for compatibility with the console in Symfony Framework

User interface BC break from 0.4.0: The --shell option introduced yesterday in 0.4.0 has been removed in favour of an argument to the existing --generate-hook option. This was required as the default console application in Symfony Framework has a global --shell option which conflicts with the one in this command, causing a logic exception. Forcing a shell type is now done as follows:

$ myprogram _completion --generate-hook zsh

ZSH support

This release adds a hook for using the module under ZSH, and makes it easy to add hooks for other shells. The appropriate hook is determined automatically at runtime, so no user profile changes should be needed for existing setups in most cases (see second note below).

Notes

• The recommended way of parsing the completion hook in a shell has changed, though the old method will continue working for existing installations:

  # New method (works under BASH and ZSH)
  myprogram _completion --generate-hook | source /dev/stdin
  
  # Old method (only works under BASH)
  eval $(myprogram _completion --generate-hook)

• In order to generate a script that will work in the current shell, the SHELL environment variable is parsed. Since this is a setting rather than a representation of current state, the --shell option may need to be specified in some circumstances.

0.3.0

This release primarily adds support for colon characters in completions.

BC break: public methods on CompletionHandler that allowed reading of command-line contents have been moved to CompletionContext. A completion handler's context is accessible through CompletionHandler::getContext().