From: Simon Thum <simon.thum@gmx.de>
To: Yann Hodique <yann.hodique@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH 07/10] org-taskjuggler: make project umbrella task optional
Date: Sun, 12 Aug 2012 23:36:03 +0200 [thread overview]
Message-ID: <502821C3.3060608@gmx.de> (raw)
In-Reply-To: <m2boigwn8v.fsf@jarvis.hodique.info>
On 08/12/2012 10:03 AM, Yann Hodique wrote:
>>>>>> "Christian" == Christian Egli<christian.egli@sbs.ch> writes:
...
> while the new (non-default) one would generate
> --8<---------------cut here---------------start------------->8---
> project main Main {}
> task task1 "Task1" {}
> task task2 "Task2" {}
> --8<---------------cut here---------------end--------------->8---
>
> leading to a report like
> --8<---------------cut here---------------start------------->8---
> 1 Task1
> 2 Task2
> --8<---------------cut here---------------end--------------->8---
>
> I must confess this is mostly a way to avoid questions from people
> looking at the report, asking why my task numbers are all 1.x :)
Yeah that sucks. If there would be a way to make the numbers
configurable in org that'd be even better. I am responsible for parts of
a project, so there is an externally defined numbering in some cases.
Bit I might go at this myself if your patches land, which look excellent
BTW.
Cheers,
Simon
>
> AFAICT it seems to work fine with either tj2 or tj3. I'm using tj3 only
> myself, but the UI of tj2 doesn't complain at all about those multiple
> root tasks.
>
> Thanks,
>
> Yann
>
next prev parent reply other threads:[~2012-08-12 21:36 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 10:53 [PATCH 00/10] Takjuggler exporter improvements Yann Hodique
2012-08-05 10:53 ` [PATCH 01/10] org-taskjuggler: make task and resource properties customizable Yann Hodique
2012-08-05 10:53 ` [PATCH 02/10] org-taskjuggler: properly install local variables at export time Yann Hodique
2012-08-05 10:53 ` [PATCH 03/10] org-taskjuggler: make use of org properties Yann Hodique
2012-08-05 10:53 ` [PATCH 04/10] org-taskjuggler: task with end-only is also a milestone (deadline) Yann Hodique
2012-08-05 10:53 ` [PATCH 05/10] org-taskjuggler: introduce a global header, for early macros Yann Hodique
2012-08-05 10:54 ` [PATCH 06/10] org-taskjuggler: use project end date, if specified Yann Hodique
2012-08-05 10:54 ` [PATCH 07/10] org-taskjuggler: make project umbrella task optional Yann Hodique
2012-08-10 5:30 ` Christian Egli
2012-08-12 8:03 ` Yann Hodique
2012-08-12 21:36 ` Simon Thum [this message]
2012-08-12 21:56 ` Bastien
2012-08-14 2:39 ` Christian Egli
2012-08-14 7:43 ` Bastien
2012-08-05 10:54 ` [PATCH 08/10] org-taskjuggler: disambiguate "headline", as it's also a valid taskjuggler property Yann Hodique
2012-08-05 10:54 ` [PATCH 09/10] org-taskjuggler: allow reports definition from within the org file Yann Hodique
2012-08-05 10:54 ` [PATCH 10/10] org-taskjuggler: update doc to reflect latest changes Yann Hodique
2012-08-05 17:29 ` [PATCH 00/10] Takjuggler exporter improvements Bastien
2012-08-05 20:02 ` Yann Hodique
2012-08-06 8:15 ` Bastien
2012-08-10 5:25 ` Christian Egli
2012-08-15 19:11 ` [PATCH v2 00/11] " Yann Hodique
2012-08-15 19:11 ` [PATCH 04/10] org-taskjuggler: task with end-only is also a milestone (deadline) Yann Hodique
2012-08-16 7:48 ` [PATCH v2 00/11] Takjuggler exporter improvements Bastien
2012-08-16 18:37 ` Yann Hodique
2012-08-19 7:27 ` Bastien
2012-08-16 19:01 ` [PATCH v3 00/11] Taskjuggler " Yann Hodique
2012-08-16 19:01 ` [PATCH v3 01/11] org-taskjuggler.el: Make task and resource properties customizable Yann Hodique
2012-08-16 19:02 ` [PATCH v3 02/11] org-taskjuggler.el: Properly install local variables at export time Yann Hodique
2012-08-16 19:02 ` [PATCH v3 03/11] org-taskjuggler.el: Make use of org properties Yann Hodique
2012-08-16 19:02 ` [PATCH v3 04/11] org-taskjuggler.el: Fix milestone definition Yann Hodique
2012-08-16 19:02 ` [PATCH v3 05/11] org-taskjuggler.el: Introduce a global header, for early macros Yann Hodique
2012-08-16 19:02 ` [PATCH v3 06/11] org-taskjuggler.el: Use project end date, if specified Yann Hodique
2012-08-16 19:02 ` [PATCH v3 07/11] org-taskjuggler.el: Make project umbrella task optional Yann Hodique
2012-08-16 19:02 ` [PATCH v3 08/11] org-taskjuggler.el: Disambiguate "headline", as it's a valid attribute Yann Hodique
2012-08-16 19:02 ` [PATCH v3 09/11] org-taskjuggler.el: Allow reports definition from within the org file Yann Hodique
2012-08-16 19:02 ` [PATCH v3 10/11] org-taskjuggler.el: Update doc to reflect latest changes Yann Hodique
2012-08-16 19:02 ` [PATCH v3 11/11] org-taskjuggler.el: Make taskjuggler compatible with org-publish Yann Hodique
2012-08-26 7:55 ` [PATCH v3 00/11] Taskjuggler exporter improvements Bastien
2012-09-25 13:53 ` Christian Egli
2012-08-15 19:11 ` [PATCH v2 01/11] org-taskjuggler: make task and resource properties customizable Yann Hodique
2012-08-15 19:11 ` [PATCH v2 02/11] org-taskjuggler: properly install local variables at export time Yann Hodique
2012-08-15 19:11 ` [PATCH v2 03/11] org-taskjuggler: make use of org properties Yann Hodique
2012-08-15 19:11 ` [PATCH v2 04/11] org-taskjuggler: fix milestone definition Yann Hodique
2012-08-15 19:11 ` [PATCH v2 05/11] org-taskjuggler: introduce a global header, for early macros Yann Hodique
2012-08-15 19:11 ` [PATCH v2 06/11] org-taskjuggler: use project end date, if specified Yann Hodique
2012-08-15 19:11 ` [PATCH v2 07/11] org-taskjuggler: make project umbrella task optional Yann Hodique
2012-08-15 19:11 ` [PATCH v2 08/11] org-taskjuggler: disambiguate "headline", as it's also a valid property Yann Hodique
2012-08-15 19:11 ` [PATCH v2 09/11] org-taskjuggler: allow reports definition from within the org file Yann Hodique
2012-08-15 19:11 ` [PATCH v2 10/11] org-taskjuggler: update doc to reflect latest changes Yann Hodique
2012-08-15 19:11 ` [PATCH v2 11/11] org-taskjuggler: make taskjuggler compatible with org-publish Yann Hodique
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=502821C3.3060608@gmx.de \
--to=simon.thum@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=yann.hodique@gmail.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).