From: Nick Dokos <nicholas.dokos@hp.com>
To: Christian Egli <christian.egli@sbs.ch>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: OT: taskjuggler question
Date: Thu, 02 Feb 2012 12:13:00 -0500 [thread overview]
Message-ID: <12524.1328202780@alphaville> (raw)
In-Reply-To: Message from Christian Egli <christian.egli@sbs.ch> of "Thu, 02 Feb 2012 17:24:55 +0100." <87sjitp5ig.fsf@sbs.ch>
Christian Egli <christian.egli@sbs.ch> wrote:
> Nick Dokos <nicholas.dokos@hp.com> writes:
>
> > But I have no TaskJugglerUI executable, which seems to be what the
> > exporter tries to call for export-and-open (C-c C-e J): what am I
> > missing?
>
> The TaskJugglerUI exists only if you have taskjuggler2.4 installed. The
> exporter predates tj3 and naively assumes that there is a TaskJugglerUI
> executable. It should really invoke a browser on the resulting HTML
> report[1] when you call export-and-open, at least when you are targeting
> tj3. The worst part is that it doesn't even tell the user that something
> failed, as it invokes the executable asynchronously using
> start-process-shell-command (info: (elisp) Asynchronous Processes). That
> way you can continue to work with emacs but emacs doesn't know what
> happened to the subprocess. I'll have to do some more research on how to
> start a process in the background and still check if it succeeded.
>
--8<---------------cut here---------------start------------->8---
(setq p (start-process-shell-command "foo" nil "foo"))
#<process foo>
(process-status p)
exit
(process-exit-status p)
127
--8<---------------cut here---------------end--------------->8---
> Thanks
> Christian
>
> Footnotes:
> [1] the tricky bit here is of course to find the resulting HTML, as the
> name of it is defined in a tj3 report definition. I'd rather refrain
> from parsing these report definitions just to find the name of the HTML
> file to open.
>
Yup - a pain. Maybe ask for an option to tj3:
$ tj3 --silent --spit-out-name-of-html-file foo.tjp
Plan.html
or
$ tj3 --silent --symlink-report-to foo.html foo.tjp
and you can go after foo.html - but of course this assumes
that you have symlinks.
Nick
next prev parent reply other threads:[~2012-02-02 17:21 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 [this message]
2012-02-01 18:36 ` taskjuggler (tj3) export issues and proposals Rainer M Krug
2012-02-01 15:07 ` 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=12524.1328202780@alphaville \
--to=nicholas.dokos@hp.com \
--cc=christian.egli@sbs.ch \
--cc=emacs-orgmode@gnu.org \
--subject='Re: OT: taskjuggler question' \
/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
Code repositories for project(s) associated with this 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).