David Maus <dm...@ictsoc.de> wrote:
> > The problem was that org-bbdb is part of org-modules by default and that
> > was loading org-bbdb way too early, certainly before bbdb itself was
> > loaded. That would set the value to nil and nothing I would do could
> > change it (short of whacking it with a setq).
>
> I pushed a patch that should fix this problem. I wrapped a
> `eval-after-load' around the `defvar', this should make sure that the
> variable is set after bbdb was loaded.
>
I still have a problem with one configuration (but not with another),
but I haven't drilled down to figure out what the problem is. I was
wondering however if the eval-after-load should be predicated on
bbdb-com rather than bbdb[fn:1]: with this change, both of my tested
configurations work (hardly a definitive test but perhaps better than
nothing).
Nick
Footnotes:
[fn:1] ... the reason being that the fboundp test is on
bbdb-record-get-field-internal, which is defined in bbdb-com.el.
