Ronan Waide writes:
> On August 25, [EMAIL PROTECTED] said:
> > And someway the problem gets triggered by the new bbdb versions, as it
> > works fine with bbdb-20000704.
> Aha, you'd a mention of byte-code in between the gnus-mime loading and
> the reinvocation of gnus. That's prolly where it's hitting into bbdb
> territory. Might I suggest running an uncompiled BBDB and regenerating
> the stacktrace?
Done. It doesn't get into bbdb-stuff in there - I get the same
backtrace when using an uncompiled bbdb.
I played around a bit. The following file works perfectly well for me,
when run in an vanilla xemacs:
(setq debug-on-error t)
(require 'bbdb)
(bbdb-initialize 'gnus 'rmail 'vm 'w3)
(setq bbdb-north-american-phone-numbers-p nil)
(setq bbdb-file "~/.bbdb/database")
(setq gnus-select-method (quote (nntp "localhost")))
(gnus)
If, however, I add 'message to the bbdb-initialize, I run into this
infinite loop reported before.
I looked at bbdb-initialize and bbdb-gnus.el, but don�t see anything
that cares about gnus/message interference.
Jochen
--
http://www.Jochen-Kuepper.de
Einigkeit und Recht und Freiheit
Libert�, �galit�, Fraternit�
Sex, drugs and rock-n-roll
_______________________________________________
bbdb-info mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/bbdb-info
