Søren Mikkelsen so...@aamikkelsen.dk writes:
On 2015-01-23 09:59, Christian Egli wrote:
Søren Mikkelsen so...@aamikkelsen.dk writes:
It works, but only for tasks that aren't having a start
attribute. It is possible to give a warning if the start
attribute already exists and make the
Søren Mikkelsen so...@aamikkelsen.dk writes:
It works, but only for tasks that aren't having a start attribute. It
is possible to give a warning if the start attribute already exists
and make the default one, the one specified in the attributes (drawer)?
What exactly doesn't work? Are there
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-01-23 09:59, Christian Egli wrote:
Søren Mikkelsen so...@aamikkelsen.dk writes:
It works, but only for tasks that aren't having a start
attribute. It is possible to give a warning if the start
attribute already exists and make the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-01-22 11:21, Christian Egli wrote:
Søren Mikkelsen so...@aamikkelsen.dk writes:
It would, however, make sense to be able to scheduled tasks
where interpreted as the start time, if the org-file is used for
more than just generating the
Søren Mikkelsen so...@aamikkelsen.dk writes:
It would, however, make sense to be able to scheduled tasks where
interpreted as the start time, if the org-file is used for more than
just generating the report.
I agree that it would make sense to use the scheduled date as the start
time. The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015-01-21 14:31, John Hendy wrote:
On Jan 21, 2015 7:09 AM, Søren Mikkelsen so...@aamikkelsen.dk
mailto:so...@aamikkelsen.dk wrote:
On 2015-01-20 22:00, Nicolas Goaziou wrote:
Hello,
Søren Mikkelsen s...@iha.dk mailto:s...@iha.dk
On 2015-01-20 22:00, Nicolas Goaziou wrote:
Hello,
Søren Mikkelsen s...@iha.dk writes:
I'm trying to use the taskjuggler exporter for getting an overview of my
project, and it seems to be straight forward if you know a bit about
Taskjuggler.
However, tasks that are scheduled org-mode
On Jan 21, 2015 7:09 AM, Søren Mikkelsen so...@aamikkelsen.dk wrote:
On 2015-01-20 22:00, Nicolas Goaziou wrote:
Hello,
Søren Mikkelsen s...@iha.dk writes:
I'm trying to use the taskjuggler exporter for getting an overview of
my
project, and it seems to be straight forward if you
I'm trying to use the taskjuggler exporter for getting an overview of my
project, and it seems to be straight forward if you know a bit about
Taskjuggler.
However, tasks that are scheduled org-mode like, i.e.,
*** TODO My task
SCHEDULED: 2015-01-27 Tue
don't appear in the report. But, if I
Hello,
Søren Mikkelsen s...@iha.dk writes:
I'm trying to use the taskjuggler exporter for getting an overview of my
project, and it seems to be straight forward if you know a bit about
Taskjuggler.
However, tasks that are scheduled org-mode like, i.e.,
*** TODO My task
SCHEDULED:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Nicolas, I can push this myself but I haven't pushed to the repo in
years. What is the current way? Do I just push to master?
I think you should push to maint, so that users of org+contrib package
can benefit from your fix soon enough. You then
Christian Egli christian.e...@sbs.ch writes:
OK, the fix is pushed to maint and merged to master.
Thank you.
As a side note, two spaces after sentences are required in commit
messages.
Regards,
John Hendy jw.he...@gmail.com writes:
I ran into an odd issue with a taskjuggler task tree I'm working on
when trying to apply a gapduration attribute to a task dependency.
Typically, I can just pass any valid taskjuggler attribute through
using properties, but my export was producing an
Hello,
Christian Egli christian.e...@sbs.ch writes:
No it is indeed a bug. At first I thought this was simply no longer
working in the new exporter but I was wrong. Nicolas of course
implemented it and way more. But there is a subtle bug. I actually found
it because I wondered about the
On Wed, Nov 5, 2014 at 2:21 AM, Christian Egli christian.e...@sbs.ch wrote:
John Hendy jw.he...@gmail.com writes:
I ran into an odd issue with a taskjuggler task tree I'm working on
when trying to apply a gapduration attribute to a task dependency.
Typically, I can just pass any valid
I ran into an odd issue with a taskjuggler task tree I'm working on
when trying to apply a gapduration attribute to a task dependency.
Typically, I can just pass any valid taskjuggler attribute through
using properties, but my export was producing an error when trying to
use:
:depends: task
On Sun, Nov 2, 2014 at 5:25 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
John Hendy jw.he...@gmail.com writes:
Thanks for the explanation. I pretty much only use duration, which has
never had an issue. As a fluke I used effort and noticed the big
difference. Thanks for illuminating the
I ran into an error with a 30min task which used the :effort: property
to set this duration. Upon compilation, I noted the warning:
```
file.tjp:10: Warning: 400.0d of effort of task one does not fit into
the project time frame.
Warning: 1 tasks could not be scheduled
```
I looked at the .tjp
Hello,
John Hendy jw.he...@gmail.com writes:
I ran into an error with a 30min task which used the :effort: property
to set this duration. Upon compilation, I noted the warning:
```
file.tjp:10: Warning: 400.0d of effort of task one does not fit into
the project time frame.
Warning: 1 tasks
On Sun, Nov 2, 2014 at 4:47 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
Hello,
John Hendy jw.he...@gmail.com writes:
I ran into an error with a 30min task which used the :effort: property
to set this duration. Upon compilation, I noted the warning:
```
file.tjp:10: Warning: 400.0d of
John Hendy jw.he...@gmail.com writes:
That mostly makes sense. Org's not case-sensitive, correct?
Correct.
I was looking at the [granted, outdated] taskjuggler documentation and
it features estimates in days (i.e. 10d): -
http://orgmode.org/worg/org-tutorials/org-taskjuggler.html
Is this
On Sun, Nov 2, 2014 at 5:01 PM, Nicolas Goaziou m...@nicolasgoaziou.fr wrote:
John Hendy jw.he...@gmail.com writes:
That mostly makes sense. Org's not case-sensitive, correct?
Correct.
I was looking at the [granted, outdated] taskjuggler documentation and
it features estimates in days
John Hendy jw.he...@gmail.com writes:
Thanks for the explanation. I pretty much only use duration, which has
never had an issue. As a fluke I used effort and noticed the big
difference. Thanks for illuminating the situation!
Actually, I was slightly wrong. According to
When exporting the attached file to task juggler, the SCHEDULED
attribute is not included in the generated file as a start attribute.
The export process is invoked with the key sequence C-c C-e J j
* Project A :taskjuggler_project:
:PROPERTIES:
24 matches
Mail list logo
