| Server IP : 195.201.23.43 / Your IP : 3.22.208.99 Web Server : Apache System : Linux webserver2.vercom.be 5.4.0-192-generic #212-Ubuntu SMP Fri Jul 5 09:47:39 UTC 2024 x86_64 User : kdecoratie ( 1041) PHP Version : 7.1.33-63+ubuntu20.04.1+deb.sury.org+1 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /usr/share/doc/bash-completion/ |
Upload File : |
bash-completion for Debian -------------------------- Completions are kept in /usr/share/bash-completion/completions. If a package installs its completion files under /etc/bash_completion.d/, bash-completion is still able to use them, but bash-completion itself does not install any files under that directory. If you are a package maintainer, you are encouraged to use dh_bash-completion(1), which will take care of installing third-party completions into the appropriate directory. -- David Paleino <dapal@debian.org> Sun, 10 Apr 2011 15:33:19 +0200 -- Gabriel F. T. Gomes <gabriel@inconstante.net.br> Mon, 12 Feb 2018 21:46:42 -0200Private