From: John Hendy <jw.hendy@gmail.com>
To: Christian Egli <christian.egli@sbs.ch>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Change property drawer syntax
Date: Fri, 31 Oct 2014 11:10:21 -0500 [thread overview]
Message-ID: <CA+M2ft8Dv2iJb3GobsAwHazGoEnfzuyLO-=a5ds4E3dwHw6PsA@mail.gmail.com> (raw)
In-Reply-To: <87tx2k8jwi.fsf@sbs.ch>
On Fri, Oct 31, 2014 at 8:10 AM, Christian Egli <christian.egli@sbs.ch> wrote:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>>
>>> 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.
>
>>> Feedback welcome.
>>
>> If there is no more feedback or objection, I will merge the branch on
>> Tuesday.
>
> I see that it is too late now, but let me still note that the
> taskjuggler exporter is quite liberal in what attribute values it allows
> for exporting. I've never used it and I haven't ever seen anyone using
> it, but in theory you could give a task a note or a journalentry which
> spans multiple lines. This will no longer be possible with this change.
>
> I guess if anyone ever wants to specify notes and journalentries for a
> task and export this to taskjuggler they will have to put it on one
> line.
I use this, or at least things like this. For example:
* task
:PROPERTIES:
:start: 2014-11-03-08:00
:task_id: task_d
:depends: task_a task_b task_c
:duration: 30min
:END:
Not multi-line, but currently I can feed any property that matches a
tj3 attribute (e.g. "task_id") and Org will "do the right thing." I
haven't followed this thread, but wanted to chime in with my usage in
case it affects the discussion/considerations around this.
John
>
> Thanks
> Christian
> --
> Christian Egli
> Swiss Library for the Blind, Visually Impaired and Print Disabled
> Grubenstrasse 12, CH-8045 Zürich, Switzerland
>
>
next prev parent reply other threads:[~2014-10-31 16:10 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
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 [this message]
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='CA+M2ft8Dv2iJb3GobsAwHazGoEnfzuyLO-=a5ds4E3dwHw6PsA@mail.gmail.com' \
--to=jw.hendy@gmail.com \
--cc=christian.egli@sbs.ch \
--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).