From: Carsten Dominik <email@example.com>
To: Richard Riley <firstname.lastname@example.org>
Cc: Bastien <email@example.com>, firstname.lastname@example.org
Subject: Re: Calendar export questions (ical & html)
Date: Mon, 3 Aug 2009 15:48:55 +0200 [thread overview]
Message-ID: <DFAA405B-06B3-479C-BD90-076656EB45EF@gmail.com> (raw)
maybe someone could turn this information into a tutorial
or a FAQ entry? I think it would be useful to write it up
and have it somewhere accessible.
On Jul 28, 2009, at 9:30 AM, Richard Riley wrote:
> Bastien <email@example.com> writes:
>> Hi Michel,
>> Michel Blanc <firstname.lastname@example.org> writes:
>>> First, I discovered that all the calendar applications I tried do
>>> show TODO entries (Google Agenda, PHP-iCalndar, Thunderbird, ...)
>>> *inside* the day/week/... view, but in sidebars or so (when the do).
>>> However, I am required to publish my agenda on GoogleAgenda (using
>>> by URL"). Is there any way to export TODO entries as VEVENT
>>> instead of
>>> VTODO in ical exports, so they get showed in external apps ?
>> A todo like this
>> * TODO Do this
>> <2009-07-28 mar>
>> will be exported both as a VTODO and as a VEVENT.
>> Note that this is not the case for DEADLINE and SCHEDULED, maybe the
>> code need to be more consistent about this.
>>> Also, the HTML exports for my agenda contains nothing but TODO's,
>>> without any date (see example here
>>> http://leucos.lstilde.org/workcal.html). There are many
>>> SCHEDULED/DEADLINE enabled entries, but nothing is shown besides
>>> hierarchy. I suspect I'm off the mark in some way here...
>> There are several types of agenda views: the tags and tags-todo types
>> don't display the dates, but the agenda type does.
>> Usually, when I need to display the dates in a tags-todo type view, I
>> just switch on the column view. But for now there is no way to store
>> the dates in the HTML output of the tags-todo agenda view, the way to
>> go is to define an agenda-type view.
>>> Finally, is there a way to customize the agenda name (i.e. X-WR-
>>> in the ICS file) ? I export 2 different ics files (the classic
>>> personal/work duo) and I would like to set relevant names for them.
>> Again, sorry to disappoint but the answer is no -- at least not to my
> FYI and still half asleep here, I think you can do the name. here is
> ical cust section:
> org-combined-agenda-icalendar-file "~/webs/richardriley/sync/
> org-icalendar-include-todo t
> org-icalendar-combined-name (quote "Richard Riley ORG")
> org-icalendar-use-scheduled '(todo-due event-if-todo event-if-
> org-icalendar-use-deadline '(todo-due event-if-todo event-if-
> org-icalendar-timezone "Europe/Berlin"
> org-icalendar-include-bbdb-anniversaries t
> ; org-icalendar-timezone nil
> org-icalendar-store-UID t
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
prev parent reply other threads:[~2009-08-03 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 12:04 Calendar export questions (ical & html) Michel Blanc
2009-07-28 0:15 ` Bastien
2009-07-28 0:25 ` Bastien
2009-07-28 7:28 ` Michel Blanc
2009-07-28 7:30 ` Richard Riley
2009-07-28 10:16 ` Michel Blanc
2009-07-28 10:56 ` Bastien
2009-07-28 11:34 ` Michel Blanc
2009-07-28 10:41 ` Bastien
2009-08-03 13:48 ` Carsten Dominik [this message]
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).