From: Rainer M Krug <r.m.krug@gmail.com>
To: Christian Egli <christian.egli@sbs.ch>
Cc: emacs-orgmode@gnu.org
Subject: Re: taskjuggler (tj3) export issues and proposals
Date: Wed, 01 Feb 2012 19:36:06 +0100 [thread overview]
Message-ID: <4F298616.3050405@gmail.com> (raw)
In-Reply-To: <87pqdyr1lz.fsf@sbs.ch>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/02/12 16:54, Christian Egli wrote:
> Rainer M Krug <r.m.krug@gmail.com> writes:
>
>> But I am not clear about
>>
>> 1) how your .org file looks 2) your reports.tji looks 3) what I
>> have to set in emacs / org variables to use tj3.
>>
>> Would it be possible to post a small basic example so that one
>> has something to start working with? I still feel lost.
>
> I attached a sample org file (basically the one from the worg page)
> that also sets (as file variables) the two variables that you need
> to set. Also I attached the reports.tji that I'm using. This should
> answer your question 1 and 2. As for question 3: If you take the
> attached org files all the relevant variables are set for you. If
> you do it manually you'll have to set
> org-export-taskjuggler-target-version and
> org-export-taskjuggler-default-reports.
>
> Let me know if the attached files work for you out of the box. I
> have some small local changes to the taskjuggler exporter but AFAIK
> they should not influence this.
Works like a charm. Now I have to figure out why my org file is not
working - but I'll look at that tomorrow.
Thanks a lot,
Rainer
>
> Thanks Christian
>
>
>
>
>
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation
Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk8phhYACgkQoYgNqgF2egrA/ACfXvMPY4NQZxN0NTmOn/3r9NZl
udMAn3fiA+FvaIAn0upH1RhEryqD6Leu
=1MMj
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-02-01 18:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 4:59 taskjuggler (tj3) export issues and proposals John Hendy
2012-02-01 14:09 ` Christian Egli
2012-02-01 14:18 ` Rainer M Krug
2012-02-01 15:20 ` John Hendy
2012-02-01 15:54 ` Christian Egli
2012-02-01 17:47 ` John Hendy
2012-02-02 7:10 ` Christian Egli
2012-02-02 15:49 ` John Hendy
2012-02-02 16:08 ` OT: taskjuggler question [was: Re: taskjuggler (tj3) export issues and proposals] Nick Dokos
2012-02-02 16:22 ` John Hendy
2012-02-02 16:24 ` OT: taskjuggler question Christian Egli
2012-02-02 17:13 ` Nick Dokos
2012-02-01 18:36 ` Rainer M Krug [this message]
2012-02-01 15:07 ` taskjuggler (tj3) export issues and proposals John Hendy
2012-02-02 8:23 ` Christian Egli
2012-05-07 4:26 ` Eric S Fraga
2012-05-08 8:16 ` Bastien
2012-05-08 9:14 ` Eric Fraga
2012-05-08 14:36 ` John Hendy
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=4F298616.3050405@gmail.com \
--to=r.m.krug@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).