Date: Fri, 22 Apr 94 13:11:30 EDT
From: [EMAIL PROTECTED] (Paul Smith)
Actually, technically this has nothing to do with V19 Emacs; it just so
happens that V19 Emacs ships the newest version of GNUS, which has these
changes, and BBDB is still written to use the older version of GNUS,
which doesn't.
Not true. BBDB can deal with gnus 4.1. I use it all the time.
If you took the new version of GNUS and started using it with Lucid you
would have the same problem there with BBDB.
No. See, that was the whole point of my original message. It works
fine with lemacs, as my original message said. Here's my situation.
I have been using two configurations: FSF-18 with gnus3.1.4 and
Lucid-19.9 with gnus4.1. bbdb and I are both aware of the great gnus
name change. Now, I'm trying to use a new configuration: FSF-19.22 with
gnus4.1. The only thing different between one of my working
configurations my goal is Lucid-19 v. FSF-19. Basically, with Lemacs,
gnus-Article-prepare hook is not bound by starting up GNUS, but with
FSF, that symbol is bound. The result is that when I subsitute FSF
for Lemacs and keep everything else the same, bbdb-insinuate-gnus gets
an error.
I still suspect that something else in my init file is indirectly
causing this problem, but I haven't found it. However, since I want
to abandon FSF-18, I added a form to my gnus-startup-hook:
(makunbound 'gnus-Article-prepare-hook)
Not exactly an elegant solution, but it gets the job done. Now bbdb
and gnus are playing nicely together in FSF-19 and I'm stripping the
remnants of FSF-18 from my init file.
Rick
