| Server IP : 85.214.239.14 / Your IP : 3.144.255.198 Web Server : Apache/2.4.62 (Debian) System : Linux h2886529.stratoserver.net 4.9.0 #1 SMP Tue Jan 9 19:45:01 MSK 2024 x86_64 User : www-data ( 33) PHP Version : 7.4.18 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,pcntl_unshare, MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : OFF Directory : /proc/self/root/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 -0200