Daniel Burrows dburr...@debian.org writes:
the bash completion stuff is actually stored in
/etc/bash_completion, which is part of the bash package.
$ apt-file search /etc/bash_completion|wc -l
500
$ apt-file --fixed-string search /etc/bash_completion
bash-completion: /etc/bash_completion
--
On Thu, Jun 04, 2009 at 05:38:43PM +0200, Sven Joachim svenj...@gmx.de was
heard to say:
On 2009-06-04 18:16 +0200, Rodolfo Medina wrote:
I did:
# aptitude purge mplayer
. After that, the bash completion was still working for the `mplayer'
command,
That's because bash reads
I did:
# aptitude purge mplayer
. After that, the bash completion was still working for the `mplayer' command,
and besides the ~/.mplayer directory was still there.
Does this mean that not *all* the configuration stuff was removed, as supposed
`aptitude purge' to do?
Thanks
Rodolfo
--
To
Rodolfo Medina wrote:
I did:
# aptitude purge mplayer
. After that, the bash completion was still working for the `mplayer'
command,
and besides the ~/.mplayer directory was still there.
Does this mean that not *all* the configuration stuff was removed, as supposed
`aptitude purge'
On 2009-06-04 18:16 +0200, Rodolfo Medina wrote:
I did:
# aptitude purge mplayer
. After that, the bash completion was still working for the `mplayer'
command,
That's because bash reads the completion code only once, when it starts
up. Try starting a fresh shell, e.g. with exec bash.
5 matches
Mail list logo
