Summary: | problem at disabling a module in bash-completion | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | fctk86 |
Component: | Current packages | Assignee: | Mike Kelly (RETIRED) <pioto> |
Status: | RESOLVED CANTFIX | ||
Severity: | trivial | CC: | ka0ttic, shell-tools |
Priority: | Lowest | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://forums.gentoo.org/viewtopic-t-463580.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
fctk86
2006-05-19 04:02:50 UTC
This is due to the way that completion functions and file sourcing are handled in bash. I really can't think of any way around this. Sorry :\. Only thing I can tell you is to run: unset _scriptname where scriptname is the script you just removed with eselect bashcomp. But, that isn't how all the completion functions are named, so there isn't really a 100% reliable way to do this, so it can't be automated in, say, eselect bashcomp. |