From: Michel Blanc <firstname.lastname@example.org>
To: Bastien <email@example.com>
Subject: Re: Calendar export questions (ical & html)
Date: Tue, 28 Jul 2009 09:28:13 +0200 [thread overview]
Message-ID: <4A6EA88D.firstname.lastname@example.org> (raw)
Bastien a écrit :
> Hi Michel,
> 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.
Well, TODOs exported as VTODOS seems fine to me. And using TODOs in Org
for project management is really very helpful, but it seems that
calendar application out there consider TODOs as laundry lists and never
display them in views.
May be it could be nice to ask Org mode to force exporting VTODOs as
VEVENTs (just like it does for non-TODO DEADLINEd events) to circumvent
those applications limitations ? Don't know if it could be useful to
others though, and this could be done easily with an external script too.
>> Also, the HTML exports for my agenda contains nothing but TODO's,
>> without any date (see example here
>> 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.
Oh well, I probably didn't read the manual deeply enough, sorry about that.
>> Finally, is there a way to customize the agenda name (i.e. X-WR-CALNAME
>> in the ICS file) ?
> Again, sorry to disappoint but the answer is no -- at least not to my
Ok. Thanks Bastien for your answers et bonne continuation.
Michel Blanc - Systèmes/Réseaux Erasme
Twitter : l3u
FA67 4EDA D648 9E50 BFA4 3F29 FDF5 4971 24B3 5C22
next prev parent reply other threads:[~2009-07-28 7:28 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 [this message]
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
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).