[Bash-completion-devel] Question on subversion completion
Guillaume Rousse
Guillaume.Rousse at inria.fr
Sun May 17 19:48:28 UTC 2009
David Paleino a écrit :
> On Mon, 11 May 2009 15:44:49 +0200, Niels Thykier wrote:
>
>> Hi Bash-completion team + subversion maintainer
>
> Hello,
>
>> [..]
>> Namely why is debian shipping with two different bash_completions for
>> subversion? I have one from bash_completion v1:1.0-2 and one from
>> subversion v1.5.6dfsg-1(determined via apt-file):
>
> Because we had a subversion completion, but didn't check whether it was
> complete or not. Thus we renamed it as _subversion.
The upstream completion from subversion has different behaviour than
other completions from bash-completion project. For instance, it filters
completion on short version of options when the long one has already
been given (-v --v<TAB> won't complete on verbose, for instance), and on
mutually exclusive options too (--recursive vs --non-recursive).
I forked it in bash-completion project many times ago to have a more
standard behaviour and implementation. Indeed, it may lacks recently
added options.
As we'll run into this problem for other packages too (gvfs, openoffice
for instance also provide their own completions functions), I guess we
may consider the practice of shipping our own versions in _package files
a consistent answer.
--
BOFH excuse #299:
The data on your hard drive is out of balance.
More information about the Bash-completion-devel
mailing list