emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Tory S. Anderson" <torys.anderson@gmail.com>
Cc: orgmode list <emacs-orgmode@gnu.org>
Subject: Re: Agenda ical export omissions: sexp, hour-in-headline
Date: Thu, 21 Aug 2014 11:17:45 +0200	[thread overview]
Message-ID: <8761hmfbgm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87y4ujcs7d.fsf@gmail.com> (Tory S. Anderson's message of "Wed, 20 Aug 2014 07:32:06 -0400")

Hello,

torys.anderson@gmail.com (Tory S. Anderson) writes:

> I have a shell function that exports my agenda to an ical file and
> uploads it for Google to read; however, there seem to be a couple
> glaring omissions from the ical. Here's the bash line that works over
> my agenda for export:
>
> 	emacs --batch --user $USER --eval "(progn (org-agenda-list nil nil 'year) (org-icalendar-combine-agenda-files))"
>
> It skips the following sort of agenda entries:
>
>    *** 09:05-09:55 CS 7637 Weekly Class @ Klaus 2447
>    <%%(org-class 2014 8 18 2014 12 12 1)> 
>
> and: 
>
>      %%(org-anniversary 2015 03 26) Glory %d Birthday
>
> So, it doesn't seem to ical-ify sexp dates, and it doesn't seem to do
> times (09:05-09:55) in the headers. Is there anything to be done for
> this? I've just discovered the agenda power of these mighty functions
> but will be limited in my use of them if they can't be exported.

Times in the header are not Org syntax, you could use an Org timestamp
instead.

Also, `icalendar' back-end uses `icalendar-export-region' internally,
which doesn't support Sexp-entries (see *icalendar-errors* buffer).


Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2014-08-21  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 11:32 Agenda ical export omissions: sexp, hour-in-headline Tory S. Anderson
2014-08-21  9:17 ` 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=8761hmfbgm.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=torys.anderson@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).