From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Brand Subject: Re: [RFC] Change property drawer syntax Date: Tue, 14 Oct 2014 18:25:13 +0200 Message-ID: References: <87oatek909.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47999) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xe4uU-00079P-QQ for emacs-orgmode@gnu.org; Tue, 14 Oct 2014 12:25:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xe4uQ-0001oQ-PW for emacs-orgmode@gnu.org; Tue, 14 Oct 2014 12:25:18 -0400 Received: from mail-qa0-x22f.google.com ([2607:f8b0:400d:c00::22f]:56862) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xe4uQ-0001oE-M9 for emacs-orgmode@gnu.org; Tue, 14 Oct 2014 12:25:14 -0400 Received: by mail-qa0-f47.google.com with SMTP id cm18so6128676qab.34 for ; Tue, 14 Oct 2014 09:25:13 -0700 (PDT) In-Reply-To: <87oatek909.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode List Hi Nicolas On Tue, Oct 14, 2014 at 4:42 PM, Nicolas Goaziou wrote: > As discussed previously, I would like to modify property drawers syntax. > The change is simple: they must be located right after a headline and > its planning line, if any. Therefore the following cases are valid > > * Headline > :PROPERTIES: > :KEY: value > :END: > > * Headline > SCHEDULED: <2014-10-14 mar.> > :PROPERTIES: > :KEY: value > :END: 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: * 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: Will they also become invalid as I tend to understand? 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> * Yearly task [It seems it can not be only reordered.] 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> ? Michael