emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: knubee <knubee@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: icalender export: limited number of repeated events
Date: Mon, 16 Jun 2008 17:57:26 +0200	[thread overview]
Message-ID: <E959F4D3-B3A4-4098-9BA9-9A9DAAD3B839@uva.nl> (raw)
In-Reply-To: <loom.20080616T084605-4@post.gmane.org>

Hi,

On Jun 16, 2008, at 11:07 AM, knubee wrote:

> I need to share some of my calendar data with co-workers. One of
> the biggest limitations I encounter with emacs/icalender is that
> it does not seem to support a limited number of repeated events.
>
> As far as I can tell, the way to specify this is with regular
> expressions. Example:
>
> * TODO Something every Sunday, 10:00-12:00, for 2 months
> SCHEDULED: <%%(and (= (calendar-day-of-week date) 7)
>                       (diary-block 1 6 200 31 7 2008)) 10:00-12:00>
>
> I have not been able to figure out how to export these to an .ics
> file.

Since iCal interpreters usually do not have access to Emacs lisp, it is
obviously impossible that the Emacs icalendar exporter could tranlate
sexp diary entries of arbitrary complexity.  We can be happy that it
does handle the most common ones.

However, I did not know that the icalendar format actually supported
something like UNTIL in the RRULE line.  So maybe we could teach the Org
exporter a syntax for this and export it properly.  However, I don't
have a good idea for a syntax, and not much time to implement it now.

One way to hack this yourself would be the following:

- Add some UNTIL:20080610 or smilar cookie to the entry, either
   to the headline or early in the body, so that it will end up
   in the summary field.  Make sure it does end up there, check the raw
   .ics file that Org is producing.

- Use the new org-before-save-iCalendar-file-hook to find these
   in the iCalendar file and turn them into an UNTIL field in
   the RRULE line of the entry.

- When you are done, share this with us!

HTH

- Carsten

>
>
> Google calendar, on the other hand, will export something like
> the following:
>
> BEGIN:VEVENT
> DTSTART:20080601T100000
> DTEND:20080601T120000
> RRULE:FREQ=DAILY;UNTIL=20080731
>
> Has anyone else managed to get a limited number of repeating
> tasks/events to export correctly to .ics format?
>
> thanks.
>
>
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2008-06-16 16:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16  9:07 icalender export: limited number of repeated events knubee
2008-06-16 15:57 ` Carsten Dominik [this message]
2008-06-17  1:35   ` knubee
2008-06-17 10:39     ` Richard G Riley

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=E959F4D3-B3A4-4098-9BA9-9A9DAAD3B839@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=knubee@gmail.com \
    /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).