From: David Engster <deng@randomsample.de>
To: Sven Bretfeld <sven.bretfeld@gmx.ch>
Cc: Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: Problems with org-caldav (wrong-type-argument stringp 47)
Date: Sat, 02 Feb 2013 16:56:29 +0100 [thread overview]
Message-ID: <87k3qqlnf6.fsf@engster.org> (raw)
In-Reply-To: <877gmxa9nd.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 28 Jan 2013 20:53:34 +1030")
Eric S. Fraga writes:
> David Engster <deng@randomsample.de> writes:
>
>> Sven Bretfeld writes:
>>> Hi David and all
>>>
>>
>>> I've got it. By try and error I found out that entries like these in an
>>> org-file cause the problem:
>>>
>>> %%(diary-anniversary 6 8 1969) Christian is %d years old
>>
>> Ah OK. Thanks for looking into this. Those entries apparently produce
>> events during export but don't seem to get an ID. I'll look into this
>> issue during the next week, when my sinuses have calmed down a bit...
>
> Yes, this is the same problem I was having when I started using
> org-caldav-sync. I currently have all my sexp based diary entries
> commented out so would definitely appreciate getting this working!
OK, I took a shot at dealing with sexp entries. It's a complicated
issue, since s-expressions can be in Org entries or by themselves. I
updated the Readme with a section on how they are handled now. Please
let me know how it works out for you. If you don't want/need sexp-based
entries in your calendar, just set org-icalendar-include-sexps to nil.
-David
next prev parent reply other threads:[~2013-02-02 15:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 14:20 Problems with org-caldav (wrong-type-argument stringp 47) Sven Bretfeld
2013-01-26 17:32 ` David Engster
2013-01-27 2:29 ` Sven Bretfeld
2013-01-27 15:07 ` David Engster
2013-01-27 17:08 ` Sven Bretfeld
2013-01-27 17:47 ` Sven Bretfeld
2013-01-27 20:41 ` David Engster
2013-01-28 10:23 ` Eric S Fraga
2013-02-02 15:56 ` David Engster [this message]
2013-02-03 0:04 ` Eric S Fraga
2013-02-03 12:20 ` David Engster
2013-02-03 22:31 ` Eric S Fraga
2013-01-28 21:14 ` Torsten Wagner
2013-01-30 10:32 ` Bastien
2013-02-01 12:08 ` Torsten Wagner
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=87k3qqlnf6.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-orgmode@gnu.org \
--cc=sven.bretfeld@gmx.ch \
/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).