From: Nick Dokos <nicholas.dokos@hp.com>
To: Philipp Haselwarter <philipp.haselwarter@gmx.de>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org,
bbdb-info@lists.sourceforge.net
Subject: Re: org-bbdb-anniversaries gives error 'bad sexp'
Date: Mon, 13 Jun 2011 00:40:47 -0400 [thread overview]
Message-ID: <24274.1307940047@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Philipp Haselwarter <philipp.haselwarter@gmx.de> of "Mon\, 13 Jun 2011 01\:36\:42 +0200." <87mxhmfwqd.fsf@nzebook.haselwarter.org>
Philipp Haselwarter <philipp.haselwarter@gmx.de> wrote:
> On 2011-05-16 14:08 UT, Matt Lundin <mdl@imapmail.org> wrote:
>
> ML> Leo <sdl.web@gmail.com> writes:
>
> >> On 2011-05-16 00:58 +0800, Matt Lundin wrote:
> >>> I'd be happy to take this on.AFAICT, there are three functions in
> >>> org-bbdb that no longer exist in bbdb v3.
> >>
> >> If you want you can build on top of my version.The anniversaries is
> >> still broken since I don't use BBDB-anniv.el.The rest works well for
> >> the past few weeks.
>
> ML> Thanks Leo!This is very helpful.
>
> ML> I have anniversaries working in my own setup, so between the two
> ML> sets of modifications, I should be able to provide a full set of
> ML> fixes.More soon...
>
> ML> Best, Matt
>
> Hi Matt,
>
> Would you mind sharing the working bits of your setup?
> I just tried %%(org-bbdb-anniversaries) and got a
> Bad sexp at line […]
>
> thanks for the effort!
>
I haven't tried bbdb-3.0 yet - I'm still on "bbdb-2.36 devo",
so I can't help with 3.0 problems. But if you want to debug
it a bit, then the following method should give you some idea
of what's going wrong.
Switch to the *scratch* buffer and evaluate the following:
(setq debug-on-error t)
(setq date '(6 13 2011)) ; you can set the date to different things
; in order to pick up different anniversaries etc.
(org-bbdb-anniversaries)
I hope this gives you a backtrace but it may be that the error is caught
(in order to produce the "Bad diary sexp at ..." message) and I'm not
sure whether a backtrace is produced in this case, but it's still worth
trying I think. In any case, check the *Messages* buffer as well.
HTH,
Nick
next prev parent reply other threads:[~2011-06-13 4:41 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
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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=24274.1307940047@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=bbdb-info@lists.sourceforge.net \
--cc=emacs-orgmode@gnu.org \
--cc=philipp.haselwarter@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).