[Aptitude-devel] Bug#435829: aptitude-[create|run]-state-bundle commands very annoying
Axel Beckert
abe at debian.org
Tue Jun 7 21:36:04 UTC 2016
Hi,
Manuel A. Fernandez Montecelo wrote:
> >Given aptitude-create-state-bundle/aptitude-run-state-bundle appear to
> >be only for debug purposes, could they be moved to /usr/lib/aptitude or
> >/usr/share/aptitude so that when someone wants to do a debug state save,
> >they just have to type the whole path to the script. Many other
> >packages put rarely needed scripts in such a place to avoid poluting the
> >normal PATH environment.
>
> After almost a decade, things got worse over the years after this report
> (with the binary named aptitude-curses and the now-disabled
> aptitude-gtk, etc). I think that it's too late to address this now.
JFTR: apti<Tab> works for many years without issues:
→ aptitude<cursor-sits-here-after-pressing-Tab>
completing external command
aptitude
completing alias
aptitude-also-via-dependency aptitude-just-recommended
aptitude-review-unmarkauto-libraries aptitude-upgradable-to-experimental
aptitude-dpigs aptitude-newer-than-in-archive
aptitude-upgradable-to-buildd
Not sure what zsh makes differently, but it successfully hid that
problem from me for as long as I can think back. (And I'm the one of
the two current Aptitude maintainers who occassionally uses the
aptitude-*-state-bundle commands.)
Only if I type aptitude-c<Tab>, these commands show up:
→ aptitude-c<cursor-sits-here-after-pressing-Tab>
completing external command
aptitude-create-state-bundle aptitude-curses
> The solution is simple anyway, just adding the extra space, or creating
> aliases if the same mistakes happen too often, etc.
Or switching to zsh. ;-)
SCNR, Axel
--
,''`. | Axel Beckert <abe at debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
More information about the Aptitude-devel
mailing list