Am 28.05.2015 um 19:41 schrieb Michael Biebl: > Hi, > > Am 28.05.2015 um 19:32 schrieb Fabian Greffrath: >> Am Donnerstag, den 28.05.2015, 18:56 +0200 schrieb Michael Biebl:
>>> /usr/share/bash-completion/bash_completion, not the individual completions. >> >> But this script, in turn, does source all the files >> in /usr/share/bash-completion/completions, or not? > > Nope, not afaik. The point of usr/share/bash-completion/completions is, > that those are loaded on demand. That's why they need to be named after > the calling executable. > >> Am Donnerstag, den 28.05.2015, 19:17 +0200 schrieb Michael Biebl: >>> Looking into this more, I'm not convinced bash_completion is the right >>> answer here. After all, it also requires explicit user configuration and >>> doesn't actually work if the symlink is in >>> /usr/share/bash-completion/bash_completion. It feels like misusing >>> bash-completion for something it wasn't designed for. >> >> Now I am puzzled. It worked for me instantly when I copied the file >> to /usr/share/bash-completion/completions and restarted a new >> interactive shell. Also, bash-completion might not be the canonical way >> to source scripts upon shell startup, but e.g. git does the same for its >> branch-aware __git_ps1 prompt. > Just for completeness sake: I created a symlink to vte.sh in /usr/share/bash-completion/completions. Didn't work here, as expected. Maybe you still have a symlink in /etc/bash_completion.d somewhere or sourced it manually in your .bashrc? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
