Package: bash
Version: 3.0-17

Normally, bash can complete shell variables when appropriate; for
example, "foo=1" followed by "echo $f<TAB>" will complete to "echo
$foo".  However, programmable completion interferes with this; for
example, "svn ls $f<TAB>", "cvs $f<TAB>", and "ssh $f<TAB>" all fail to
complete $foo.  Shell variables should always be a valid completion when
they are syntactically valid, since they could always contain a string
appropriate for the current command.

(By "when they are syntactically valid", I mean that the shell already
knows not to complete "echo \$f<TAB>" into "echo \$foo", and that
shouldn't change.)

- Josh Triplett

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to