# bash completion for the Mercurial distributed SCM -*- sh -*-

​

# Docs:

#

# If you source this file from your .bashrc, bash should be able to

# complete a command line that uses hg with all the available commands

# and options and sometimes even arguments.

#

# Mercurial allows you to define additional commands through extensions.

# Bash should be able to automatically figure out the name of these new

# commands and their options.  See below for how to define _hg_opt_foo

# and _hg_cmd_foo functions to fine-tune the completion for option and

# non-option arguments, respectively.

#

#

# Notes about completion for specific commands:

#

# - the completion function for the email command from the patchbomb

#   extension will try to call _hg_emails to get a list of e-mail

#   addresses.  It's up to the user to define this function.  For

#   example, put the addresses of the lists that you usually patchbomb

#   in ~/.patchbomb-to and the addresses that you usually use to send

#   the patchbombs in ~/.patchbomb-from and use something like this:

#

#      _hg_emails()

#      {

#          if [ -r ~/.patchbomb-$1 ]; then

#              cat ~/.patchbomb-$1

#          fi

#      }

#

#

# Writing completion functions for additional commands:

#

# If it exists, the function _hg_cmd_foo will be called without

# arguments to generate the completion candidates for the hg command

# "foo".  If the command receives some arguments that aren't options

# even though they start with a "-", you can define a function called

# _hg_opt_foo to generate the completion candidates.  If _hg_opt_foo

# doesn't return 0, regular completion for options is attempted.

#

# In addition to the regular completion variables provided by bash,

# the following variables are also set: