~/.bash_completion.d/python-argcomplete.sh prevents other completions

I noticed a while ago that when I source the script python-argcomplete.sh I cannot tab to complete environment variables. If I comment the last line in the script:

#complete -o default -D -F _python_argcomplete_global

Then I can do:

macbook-pro:~ jmlopez$ echo $PA<TAB>
macbook-pro:~ jmlopez$ echo $PATH

As soon as I activate the global completer then it doesn’t do the environment variable completion anymore. This behavior does not happen when registering an awesome script, i.e.

eval "$(register-python-argcomplete my-awesome-script.py)"

Not sure if this is happening with others, can someone check if this is bug on argparse? I’m using bash 4.2:

macbook-pro:~ jmlopez$ echo $BASH_VERSION
4.2.45(2)-release

[jmlopez-rod]

I found some bash reference on complete and the -o option got my attention:

-o comp-option

The comp-option controls several aspects of the compspec’s behavior beyond the simple generation of completions. comp-option may be one of:

bashdefault Perform the rest of the default Bash completions if the compspec generates no matches. default Use Readline’s default filename completion if the compspec generates no matches.

It seems that adding the bashdefault option fixes the problem:

complete -o default -o bashdefault -D -F _python_argcomplete_global

Now it completes the environment variables as well.

[jiasli]

Sure. With pleasure!