emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Roland Winkler <winkler@gnu.org>
Cc: emacs-orgmode@gnu.org, bbdb-info@lists.sourceforge.net,
	Johnny <yggdrasil@gmx.co.uk>
Subject: Re: org-bbdb-anniversaries gives error 'bad sexp'
Date: Sun, 15 May 2011 12:58:36 -0400	[thread overview]
Message-ID: <87k4drew8z.fsf@fastmail.fm> (raw)
In-Reply-To: <19919.63774.257976.613699@gargle.gargle.HOWL> (Roland Winkler's message of "Sun, 15 May 2011 11:02:38 -0500")

"Roland Winkler" <winkler@gnu.org> writes:

> On Sat May 14 2011 Johnny wrote:
>> I have set up an org-agenda that includes anniversaries in the agenda
>> view from the bbdb database, but this breaks with bbdb 3.02 giving the
>> error 'bad sexp'.
>> I set up the agenda file using (from org-mode 6.33x info section 10.3.1):
>> * Anniversaries
>> :CATEGORY: Anniv
>> :END
>> %%(org-bbdb-anniversaries)
>> Any ideas?
> I need to say that I do not know how org-mode interfaces with BBDB.
> I am CC'ing this email also to emacs-orgmode@gnu.org.
> If org-mode is set up to work with BBDB v2.x, (most likely) this
> does not work with BBDB v3. Defining aliases for the old BBDB
> functions in terms of the new ones would work only in a few cases.
> Of course, this depends first of all on how org-mode is supposed to
> work with BBDB.

I'd be happy to take this on. AFAICT, there are three functions in
org-bbdb that no longer exist in bbdb v3.


The first two can easily be defaliased to bbdb-search-organization and
bbdb-search-name. (For a while, we should probably support bbdb v2 and
v3 simultaneously.)

What is the new name of bbdb-record-getprop (the function that retrieves
the value of a given label in a record)? My best guess is
bbdb-record-note, but I want to confirm this.

The other major change that breaks compatibility is the order of the
parameters in bbdb-split. It has been reversed in the new bbdb: i.e.,
one used to call (bbdb-split string separator), whereas now one must
call (bbdb-split separator string). Is there a compelling reason to
change this order in the new bbdb?


  parent reply	other threads:[~2011-05-15 16:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87wrht82iw.fsf@gmx.co.uk>
2011-05-15 16:02 ` org-bbdb-anniversaries gives error 'bad sexp' Roland Winkler
2011-05-15 16:13   ` Roland Winkler
2011-05-15 16:58   ` Matt Lundin [this message]
2011-05-15 17:35     ` Roland Winkler
2011-05-16 14:03       ` Matt Lundin
2011-05-15 18:18     ` Leo
2011-05-16 14:08       ` Matt Lundin
2011-06-12 23:36         ` Philipp Haselwarter
2011-06-13  4:40           ` Nick Dokos
2011-06-13 12:27           ` Matt Lundin
2011-06-13 16:15             ` Philipp Haselwarter
2011-06-15 14:32               ` Carsten Dominik
2011-06-15 19:13                 ` [bug] Problem with insert anniversary agenda function (was Re: org-bbdb-anniversaries gives error 'bad sexp') Eric S Fraga
2011-06-16  8:04                   ` [patch] " Eric S Fraga
2011-06-16 12:41                     ` Carsten Dominik
2011-06-20  7:41                       ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k4drew8z.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=bbdb-info@lists.sourceforge.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=winkler@gnu.org \
    --cc=yggdrasil@gmx.co.uk \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).