[Bash-completion-devel] Mandriva handling of bash completion
Guillaume Rousse
Guillaume.Rousse at inria.fr
Sat Jan 17 12:28:22 UTC 2009
Guillaume Rousse a écrit :
> See for instance various code currently not part of upstream
> bash-completion package:
>
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/bluez/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/bridge-utils/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/cfengine/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/perl-CPANPLUS/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/dkms/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/minicom/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/msynctool/current/SOURCES
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/munin/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/net-tools/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/qemu/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/quota/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/rdesktop/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/nfs-utils/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/samba/current/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/vncviewer/strace/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/vpnc/strace/SOURCES/
> http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/xen/current/SOURCES/
I didn't had much input of those completions sofar. As Ville seems to
prefer post-commit review, I will introduce them one by one in contrib
directory. I just asked for project membership.
Just a question, tough, as everyone seems to be OK for moving to a
installation-based system for activating completion functions, should we
really keep the have("foo") { } condition in each file ? In such a
scenarion, if a completion file get sourced, it his because it has been
enabled, meaning the command is available. I have no real clue about the
exact cost calling this function, but avoiding useless tests at each new
shell startup seems a good idea for me.
--
Guillaume Rousse
More information about the Bash-completion-devel
mailing list