[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#799545:



On Fri, Jun 9, 2017 at 8:55 PM, Julian Andres Klode <jak@debian.org> wrote:
> On Fri, Jun 09, 2017 at 10:50:43AM +0400, Ville Skyttä wrote:
>> The main apt completion seems to be shipped with the apt package, and
>> apt-get and apt-cache with bash-completion.
>
> We really only shipped the apt completion, because nobody at the
> bash-completion side was merging it.

That's not really too much of a surprise, as our general preference is
to encourage projects to ship their completions themselves, and to
take advantage of general purpose features, functions etc from
bash-completion. And besides, it's been a while since there has been a
Debian/Ubuntu user active in bash-completion upstream
development/maintenance. Nowadays it's basically just me, and I'm a
Fedora user, not a Debian/Ubuntu one, and I don't have that much time
for bash-completion in the first place.

> I don't particularly like merging bash completions, or any completions
> for that matter. How many shells will we end up with?

I'd say max two, bash and zsh. And I gather zsh can use bash
completions so I think you can get away with one.

Conversely, in bash-completion we don't have any active apt* users,
and we have no knowledge what options the tools actually support, and
should preferably support whatever version of apt* is installed on the
end user system. Whereas if the completions where shipped by you in
apt, you know exactly what the options available are and what they do.
I'm fairly certain that the hardcoded option and command lists we have
in bash-completions' apt* completion files are outdated or inaccurate.


Reply to: