Pat Tressel wrote:
> I'm curious why this was switched to qbzr. I'm not using qbzr -- I'm
> using the command line -- and I did not use any of the q* commands.
> Commands involved were:
Because the traceback clearly shows that the error is raised from within
a hook function registered by qbzr. This doesn't guarantee that qbzr is
the cause, but it's currently the primary suspect.
You could try those commands again with --no-plugins; that may
work around the problem for you.
Pat Tressel wrote:
> I'm curious why this was switched to qbzr. I'm not using qbzr -- I'm
> using the command line -- and I did not use any of the q* commands.
> Commands involved were:
Because the traceback clearly shows that the error is raised from within
a hook function registered by qbzr. This doesn't guarantee that qbzr is
the cause, but it's currently the primary suspect.
You could try those commands again with --no-plugins; that may
work around the problem for you.