emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: iCalendar export creates VTODO *and* VEVENT for TODO entries with timestamp [6.36trans (release_6.36.158.g1378)]
Date: Fri, 4 Jun 2010 14:10:36 +0200	[thread overview]
Message-ID: <201006041410.36988.tassilo@member.fsf.org> (raw)
In-Reply-To: <E62FDF7F-F51B-4434-A668-3BC78A86339E@gmail.com>

On Friday 04 June 2010 13:28:02 Carsten Dominik wrote:

Hi Carsten,

> > But there's one thing which might be a bug.  I have this TODO entry:
> >
> > *** TODO Einteilung für Nacht der Informatik machen
> >    <2010-06-08 Tue>
> 
> Hi Tassilo,  before looking deeper:  Why don't you schedule
> the item for this day?

Indeed, that would be more correct.  And after doing that, there're no
duplicate VEVENTs for TODOs.  Here's the VTODO I get:

--8<---------------cut here---------------start------------->8---
BEGIN:VTODO
UID: TODO-148d89b6-7212-4ffc-94c6-48e27dc2af98
DTSTART;VALUE=DATE:20100608
SUMMARY:Einteilung für Nacht der Informatik machen
DESCRIPTION: normal: http://www.[snip]...
CATEGORIES:agebert,uni
SEQUENCE:1
PRIORITY:5
STATUS:NEEDS-ACTION
END:VTODO
--8<---------------cut here---------------end--------------->8---

The scheduled date is set as start time (DTSTART), which is correct as
far as I can tell.  The only problem is that KOrganizer doesn't show it
in its agenda.

It seems org behaves correctly, and there's only an issue with
KOrganizer.  So I'll knock on their doors. ;-)

Bye,
Tassilo

  reply	other threads:[~2010-06-04 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04  6:44 Bug: iCalendar export creates VTODO *and* VEVENT for TODO entries with timestamp [6.36trans (release_6.36.158.g1378)] Tassilo Horn
2010-06-04 11:28 ` Carsten Dominik
2010-06-04 12:10   ` Tassilo Horn [this message]
2010-06-04 12:20     ` Carsten Dominik
2010-06-04 12:29       ` Tassilo Horn

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=201006041410.36988.tassilo@member.fsf.org \
    --to=tassilo@member.fsf.org \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).