From: Daniel Martins <email@example.com>
To: Sven Bretfeld <firstname.lastname@example.org>
Cc: Dan Griswold <email@example.com>, firstname.lastname@example.org
Subject: Re: Re: iCal export and complex diary sexps
Date: Fri, 23 Jul 2010 18:05:48 -0300 [thread overview]
Message-ID: <AANLkTikMe-+UmQ=a4uQ_dHGktgV0W4XPj5081AHDvTGZ@mail.gmail.com> (raw)
Exporting org-diary-class even ignoring the weeke off (last arguments)
for me it would be a fantastic start. It would be like converting
org-diary-class to a simple diary sexp.
I know it is dumb but in my case I would be glad to slit one
org-diary-class in several org-diary-class (before and after weeks
off) on order to have my appts exposted to ical.
2010/7/23 Sven Bretfeld <email@example.com>:
> Hi Dan
> Dan Griswold <firstname.lastname@example.org> writes:
>> On 15 Jul 2010, email@example.com wrote:
>>> There was a thread about this some weeks ago. The iCal export does not
>>> support org-diary-class entries or other complex diary sexps.
>> I missed that thread, but it's an issue I looked into some time ago,
>> with regard to sexps. The basic issue is that org-export-icalendar-*
>> calls icalendar.el, which currently does not support the export of
>> complex sexps.
>> In other words, it doesn't do much good for us to say that Org ought to
>> export these things to ical, because the feature is missing not from org
>> but from a completely different package.
> But it's strange that diary-sexps can explicitly switched on and of for
> iCalendar export in customize. Why is that?
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
next prev parent reply other threads:[~2010-07-23 21:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 7:07 iCal export and complex diary sexps Sven Bretfeld
2010-07-15 19:31 ` Dan Griswold
2010-07-23 10:00 ` Sven Bretfeld
2010-07-23 21:05 ` Daniel Martins [this message]
2010-08-07 6:55 ` Carsten Dominik
2010-08-08 14:35 ` Daniel Martins
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 \
* 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).