From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Detlef Steuer <detlef.steuer@gmx.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-caldav problem; used to work
Date: Mon, 17 Nov 2014 00:12:29 +0100 [thread overview]
Message-ID: <871tp2spsy.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20141116235825.420fe95a@linux-w3xx> (Detlef Steuer's message of "Sun, 16 Nov 2014 23:58:25 +0100")
Hello,
Detlef Steuer <detlef.steuer@gmx.de> writes:
> But there was a new Problem: A new set of UIDs got created when I edited
> my test data. (removed the SCHEDLULED key-word)
>
> --- Before (result of first test export)
>
> * APPT Test1
> SCHEDULED: <2014-11-12 Mi 19:00-20:00>
> :PROPERTIES:
> :ID: dc432cb8-ab29-4bf0-8ea0-e40ca8e8850d
> :END:
[...]
> removed SCHEDULED
A properties drawer needs to be the second element in the entry,
planning info being the first, or the first one if there is no planning
info.
If you remove "SCHEDULED:", you also remove planning info only to leave
a plain timestamp (in a paragraph, but that doesn't matter here). The
properties drawer is no longer correctly located in your entry: it
becomes a regular drawer named "PROPERTIES".
As a consequence, ox-icalendar can no longer recognize entry's ID and
creates a new one, correctly located this time, before next export:
> --- After
>
> * APPT Test1
> :PROPERTIES:
> :ID: 867c4f4e-9c7f-4d39-9404-f9dadb25edd9
> :END:
> <2014-11-12 Mi 19:00-20:00>
> :PROPERTIES:
> :ID: dc432cb8-ab29-4bf0-8ea0-e40ca8e8850d
> :END:
Long story short: if you remove "SCHEDULED:", also move the timestamp
/after/ the drawer.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2014-11-16 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 14:41 org-caldav problem; used to work Detlef Steuer
2014-11-16 21:53 ` David Engster
2014-11-16 22:15 ` Detlef Steuer
2014-11-16 22:24 ` Rasmus
2014-11-16 23:00 ` Detlef Steuer
2014-11-16 22:37 ` David Engster
2014-11-16 22:58 ` Detlef Steuer
2014-11-16 23:12 ` 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=871tp2spsy.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=detlef.steuer@gmx.de \
--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).