From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nick Dokos <nicholas.dokos@hp.com>
Subject: Re: [BUG?] subtle sequencing error when setting org-bbdb-old in
 org-bbdb.el
Date: Mon, 27 Feb 2012 17:21:59 -0500
Message-ID: <6717.1330381319@alphaville>
References: <8273.1330161610@alphaville> <87r4xgyqdm.wl%dmaus@ictsoc.de>
Reply-To: nicholas.dokos@hp.com
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:40868)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nicholas.dokos@hp.com>) id 1S28xS-0000De-IR
	for emacs-orgmode@gnu.org; Mon, 27 Feb 2012 17:22:15 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nicholas.dokos@hp.com>) id 1S28xH-0007NQ-BX
	for emacs-orgmode@gnu.org; Mon, 27 Feb 2012 17:22:14 -0500
Received: from g5t0008.atlanta.hp.com ([15.192.0.45]:3763)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nicholas.dokos@hp.com>) id 1S28xH-0007M2-7f
	for emacs-orgmode@gnu.org; Mon, 27 Feb 2012 17:22:03 -0500
In-Reply-To: Message from David Maus <dmaus@ictsoc.de>
	of "Mon, 27 Feb 2012 21:26:29 +0100." <87r4xgyqdm.wl%dmaus@ictsoc.de>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: David Maus <dmaus@ictsoc.de>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org

David Maus <dmaus@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.