From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Change property drawer syntax
Date: Tue, 14 Oct 2014 21:38:38 +0200 [thread overview]
Message-ID: <874mv65tmp.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CALn3zojArx-0_wsXUEAM-KNihqS7FzF3gAa1d24P6q2On_D_3A@mail.gmail.com> (Michael Brand's message of "Tue, 14 Oct 2014 18:25:13 +0200")
Hello,
Michael Brand <michael.ch.brand@gmail.com> writes:
> What about legacy multi line plain timestamp and planning info:
>
> * Yearly meeting
> <2013-09-22 Sun>
> <2014-10-19 Sun>
> SCHEDULED: <2015-01-01 Thu> Add next plain timestamp.
> :PROPERTIES:
> :KEY: value
> :END:
This is invalid, and has been so for a long time. Quoting first footnote
in (info "(org) Inserting deadline/schedule"):
The ‘SCHEDULED’ and ‘DEADLINE’ dates are inserted on the line right
below the headline. Don’t put any text between this line and the
headline.
This footnote was inserted in c431fef47a7cbcc6ea79e3a945bc22cca4b4be96,
which is dating back from march 2011.
> * Yearly task
> DEADLINE: <2013-09-22 Sun -2d>
> DEADLINE: <2014-10-19 Sun -2d>
> SCHEDULED: <2015-01-01 Thu> Add next deadline.
> :PROPERTIES:
> :KEY: value
> :END:
This is also invalid, per the footnote above. Also, you cannot have some
text on the planning line.
> Will they also become invalid as I tend to understand?
They are already. My proposal doesn't change anything about it.
> Can they be reordered as
>
> * Yearly meeting
> SCHEDULED: <2015-01-01 Thu> Add next plain timestamp.
> :PROPERTIES:
> :KEY: value
> :END:
> <2014-10-19 Sun>
> <2013-09-22 Sun>
If you remove "Add next plain timestamp.", this is perfectly valid.
* Yearly meeting
SCHEDULED: <2015-01-01 Thu>
:PROPERTIES:
:KEY: value
:END:
<2014-10-19 Sun>
<2013-09-22 Sun>
> or will they have to be transformed into sub-headings like
>
> * Yearly meeting
> :PROPERTIES:
> :KEY: value
> :END:
> ** Yearly meeting - 2013
> <2013-09-22 Sun>
> ** Yearly meeting - 2014
> <2014-10-19 Sun>
> ** Yearly meeting - Add next plain timestamp
> SCHEDULED: <2015-01-01 Thu>
>
> * Yearly task
> :PROPERTIES:
> :KEY: value
> :END:
> ** Yearly task - 2013
> DEADLINE: <2013-09-22 Sun -2d>
> ** Yearly task - 2014
> DEADLINE: <2014-10-19 Sun -2d>
> ** Yearly task - Add next deadline
> SCHEDULED: <2015-01-01 Thu>
I don't understand this.
Again, there is one possible planning info line per entry. If there is
one, the property drawer has to be inserted right below it. Otherwise,
it needs to be right after the headline itself.
This has nothing to do with plain timestamps, i.e., <2014-10-19 Sun> and
<2013-09-22 Sun> in your example.
I hope this is clearer now.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2014-10-14 19:38 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 14:42 [RFC] Change property drawer syntax Nicolas Goaziou
2014-10-14 14:55 ` Andreas Leha
2014-10-14 15:55 ` Nicolas Goaziou
2014-10-14 16:18 ` Eric Abrahamsen
2014-10-14 19:26 ` Nicolas Goaziou
2014-10-14 16:25 ` Michael Brand
2014-10-14 19:38 ` Nicolas Goaziou [this message]
2014-10-15 17:25 ` Michael Brand
2014-10-15 20:52 ` Nicolas Goaziou
2014-10-15 2:58 ` Eric Abrahamsen
2014-10-15 10:11 ` Nicolas Goaziou
2014-10-15 11:22 ` Eric Abrahamsen
2014-10-15 7:38 ` Rainer M Krug
2014-10-15 10:14 ` Nicolas Goaziou
2014-10-15 11:27 ` Rainer M Krug
2014-10-20 22:35 ` Rasmus
2014-10-26 15:24 ` Nicolas Goaziou
2014-10-28 13:27 ` Nicolas Goaziou
2014-11-06 10:21 ` Sebastien Vauban
2014-11-08 13:46 ` Nicolas Goaziou
2014-11-10 10:19 ` Sebastien Vauban
2014-11-10 10:41 ` Nicolas Goaziou
2014-11-10 11:04 ` Sebastien Vauban
2014-11-10 11:51 ` Nicolas Goaziou
2014-11-10 12:55 ` Sebastien Vauban
2014-11-12 10:40 ` Sebastien Vauban
2014-11-13 19:58 ` Nicolas Goaziou
[not found] ` <87sihmq3dd.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2014-11-26 14:09 ` Sebastien Vauban
2014-10-31 13:10 ` Christian Egli
2014-10-31 16:10 ` John Hendy
2014-11-03 8:27 ` Christian Egli
2014-11-03 8:33 ` Nicolas Goaziou
2014-11-01 10:57 ` Nicolas Goaziou
2014-11-03 8:38 ` Christian Egli
2014-11-03 20:14 ` Nicolas Goaziou
2014-11-12 11:01 ` Sebastien Vauban
2014-11-12 11:11 ` Sebastien Vauban
2014-11-26 14:18 ` Sebastien Vauban
2014-11-26 23:37 ` Nicolas Goaziou
2014-11-27 9:24 ` Sebastien Vauban
2014-11-28 22:16 ` Nicolas Goaziou
2014-12-05 14:33 ` Puneeth Chaganti
2014-12-05 23:31 ` Nicolas Goaziou
2014-12-06 6:42 ` Puneeth Chaganti
2014-12-06 20:36 ` Nicolas Goaziou
2014-11-14 8:36 ` Nicolas Goaziou
[not found] ` <87ppcqnpq7.fsf-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org>
2014-11-14 13:58 ` Sebastien Vauban
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=874mv65tmp.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@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).