emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Myles English <mylesenglish@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: translating event sexps to org for org-caldav
Date: Mon, 21 Nov 2016 23:38:03 +0100	[thread overview]
Message-ID: <8737ikihmc.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87shqn9jky.fsf@gmail.com> (Myles English's message of "Sat, 19 Nov 2016 22:43:41 +0000")

Hello,

Myles English <mylesenglish@gmail.com> writes:

> From the org-caldav github page[fn:2] :
>
> """However, sexp-entries are insanely flexible, and there are limits as
> to what the icalendar exporter will handle. For example, this here
>
> ** Regular event
>    <%%(memq (calendar-day-of-week date) '(1 3 5))>
>
> will not be exported at all."""
>
> However, org-agenda uses these sexps to make entries in the agenda.
>
> Would it be possible to reuse something from org-agenda to write these
> entries as org items into a file that could be uploaded using
> org-caldav?  Maybe org-get-entries-from-diary?  Is there a huge problem
> with this that I haven't noticed?

This is tricky. Agenda has a notion of time span, "ox-icalendar" hasn't.
So you would have to test if sexp matches for every day between some
arbitrary chosen dates.

"ox-icalendar.el" relies on "icalendar.el" library, bundled with Emacs,
for converting diary entries. Alas, it doesn't handle sexp entries
either.

> [fn:1] I think I started using sexps just because org-mode can't do
> e.g. "every Monday, *between these two dates*"

I use `org-class' for that.

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2016-11-21 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-19 22:43 translating event sexps to org for org-caldav Myles English
2016-11-21 22:38 ` Nicolas Goaziou [this message]

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=8737ikihmc.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=mylesenglish@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).