emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: frank <fab@breengeosci.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: taskjuggler - using gaplength or gapduration
Date: Wed, 12 Feb 2014 15:31:13 -0600	[thread overview]
Message-ID: <CA+M2ft8CkMk0-RAOMJzg=3y5hnc5OM=9z8UOkYKNxWcK-063fw@mail.gmail.com> (raw)
In-Reply-To: <52FBD572.7040604@breengeosci.com>

On Wed, Feb 12, 2014 at 2:11 PM, frank <fab@breengeosci.com> wrote:
>
> One issue that I am having is regarding gaplength and gapduration for tasks.  Under the TJ3 syntax, the command would be
> " depends !!PHII {gapduration 7w} ".
>
> I added gaplength and gapduration under ' Org Taskjuggler Valid Task Attributes ' and added the following in my org-mode file:
>

Ah, my apologies. Now I understand. I think you'll need Nicholas' or
someone else's help with this regarding the tj3 exporter. The typical
mapping is simply:

- Org

:property: value

- tj3

task {
property value
}

I just re-read how gaplength and gapduration work, and you'll need new
mapping of the :property: value to the output format so it ends up in
curly braces. I didn't catch that initially. The gapduration and
gaplength docs don't really make that clear, but the depends page
does:
- http://www.taskjuggler.org/tj3/manual/depends.html

So, no, you didn't do anything wrong, I just don't think the exporter
is setup to handle this sort of mapping.


John


> *** PSF
>     :PROPERTIES:
>     :Task_id: PSF
>     :depends: PHII
>     :gaplength: 7w
>     :duration: 10d
>     :END:
>
> The resulting export comes out:
>     depends !!PHII
>     duration 10d
>     gaplength 7w
>
> which is incorrect.  What am I doing wrong.
>
> Frank
>

  parent reply	other threads:[~2014-02-12 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 20:11 taskjuggler - using gaplength or gapduration frank
2014-02-12 21:22 ` John Hendy
2014-02-12 21:31 ` John Hendy [this message]
2014-02-12 22:44 ` Nicolas Goaziou
2014-02-13 10:54 ` Christian Egli

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+M2ft8CkMk0-RAOMJzg=3y5hnc5OM=9z8UOkYKNxWcK-063fw@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=fab@breengeosci.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).