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

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.

Yet we are trying to make the new BBDB part of GNU Emacs. So it
would be great if org-mode could be updated to provide (also) an
interface for the new BBDB.

While I'd like to declare soon that BBDB v3 has reached a beta
stage, it was probably good if someone familiar with org-mode's
interface to BBDB could take a look into this so that we could try
to make sure that the new BBDB can work with org-mode as smoothly as
possible. (Various add-ons for BBDB v2 had to go through some pain
to work as intended by advicing BBDB functions and things like that.
With BBDB v3 I tried to clean up and simplify these things; and
various add-ons for BBDB v2 are already incorporated into v3 in one
or the other way. It would probably be good if the needs of org-mode
could be incorporated into the new BBDB before we declare that BBDB
v3 has reached a beta stage.)


Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
BBDB Home Page: http://bbdb.sourceforge.net/

       reply	other threads:[~2011-05-15 16:02 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 ` Roland Winkler [this message]
2011-05-15 16:13   ` org-bbdb-anniversaries gives error 'bad sexp' Roland Winkler
2011-05-15 16:58   ` Matt Lundin
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=19919.63774.257976.613699@gargle.gargle.HOWL \
    --to=winkler@gnu.org \
    --cc=bbdb-info@lists.sourceforge.net \
    --cc=emacs-orgmode@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).