On Thursday December 30 2010, Patrick Shanahan wrote:
* Patrick Shanahan <paka@opensuse.org> [12-30-10 08:23]:
a possible solution, removal of the script, /etc/bash_completion.d/patool.sh
Indeed, removal of the file, /etc/bash_completion.d/patool.sh *solves* the problem of the delay and error msg "bash: have: command not found"
Of course, but only at the expense of the completions for patool that .../patool.sh would have established.
AND, I guess, a report to bugzilla?? But I still don't understand why I have the problem and others do not??
nor which package, bash-completion or patool, is causing the problem.
The peculiar thing is that in the execution trace (from the -x option to bash) shows the pattern of setting and unsetting the _value_ "have" (unset -v have ... have="yes") and finally the unsetting of the function defintion have() (unset -f have). It is following this last unset that the patools script is sourced and that is why the diagnostic occurs (and, of course, the code that is predicated on the exit / return status of have() does not run and the patools completions are not established). The other possible clue is that the amount of trace between the many iterations of the { unset -v have ... have="yes" } cycle is much smaller (on the order of 10) than that between the { unset -f have } and the diagnostic for "have: command not found" (nearly 300), suggesting that the patools completion set-up script is being executed in the wrong place.
But I will make a bug report to bugzilla.novell.com against bash-completion and cite patool package
Bug #661851 submitted.
-- Patrick Shanahan
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org