Re: Org mode for meeting minutes
Hi Timm
Timm Lichte writes:
> Glad you find it interesting. I think both ways of taking notes have
> their merits and use cases. In small productive project meetings, I'd
> rather use more of the org-mode infrastructure. When there is a larger
> event with changing participants and its really important to document
> and keep track of what is going on, simple annotated lists fare better
> in my experience.
I think you are probably right. When taking notes quickly your approach
without having to fidget with Tasks is probably faster. I just did not
want to stray too far off plain org-mode notation.
>> If I understand correctly you are defining some kind of extra list
>> markup (is something a task or a decision, etc) and the you wrote a
>> custom exporter that produces fancy LaTeX for the minutes (well, if I
>> understand correctly it really is a custom exporter that generates
>> org-mode and then LaTeX from there).
>
> Yes, I'm basically extending the syntax for descriptions and
> overlaying it with some convenient font-lock. My custom exporter
> pushes everything in a temporary buffer and replaces the minutes
> notation with LaTeX expressions and then starts the regular
> org-export. This probably looks awkward but gives me full flexibility.
Well, it might look weird, but I think the idea is good. TBH, I'm not
sure if there is another (programatic) way to derive from an existing
exporter.
> The LaTeX document is just a list of sections with nested itemize
> environments. One item would look like this:
>
> \item \ActionTag{Peter}{::} \ActionTagMargin{Peter}Something to do.
>
> I've pushed the TeX file of the example to the repository. Hope this
> makes it clearer.
Ah, yes, this makes it much clearer. I really like this.
> I'm really hesitant to make this a MELPA package right away, if this
> is what you mean. The font-lock and everything is really individual
> and non-generic. But I'll think about it.
I understand. Now that I think of it it might be better to package the
LaTeX commands into a package on CTAN. I looked at the various LaTeX
minutes packages and so far yours seems almost the nicest.
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: Org mode for meeting minutes
Hi Timm Timm Lichte writes: > Just for your amusement: I've developed a very different but effective > way of taking minutes with org-mode that uses just lists and > enumerations. I have been using this solution for more than a year on > a daily basis and I'm really happy with it (and colleagues don't > complain). Speed, simplicity and readability for non-emacsers is > critical in my job, so the solutions you are proposing would be > overkill. This is really interesting! I can see that you are very efficient with this. I think my solution is more using the standard org-mode infrastructure, I don't define any export for example. > You can have a look at the style and code here: > > https://github.com/timmli/org-minutes-dev If I understand correctly you are defining some kind of extra list markup (is something a task or a decision, etc) and the you wrote a custom exporter that produces fancy LaTeX for the minutes (well, if I understand correctly it really is a custom exporter that generates org-mode and then LaTeX from there). I don't quite understand how the LaTeX works. Is this some kind of two column layout or do you keep the action item markers and the assignees in the margin? Can you post the produced LaTeX? > Any feedback is greatly appreciated. But keep in mind that the code is > not polished at all -- this is a hobby project of an elisp dilettante. It would be good to package this. The code would get more usage and you'd get more feedback. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: Org mode for meeting minutes
Hi all I'm picking up this thread again since I think I have solved the issue for myself. I do use org-mode for meeting minutes now. Thanks to the input from this list I managed to solve the outstanding issues such as tabular reports of action items. I wrote a blog post summarizing my findings which you can find here https://egli.dev/posts/using-org-mode-for-meeting-minutes/ Hope that helps Christian "Fraga, Eric" writes: > On Thursday, 31 Oct 2019 at 15:03, Christian Egli wrote: >> His mail is from 2008 and a lot has happened in the mean time. > > Although a lot has happened in the meantime, I've not seen anything pass > by which addresses minutes of meetings and tracking actions. I used to > use org to take minutes but haven't done so in a very long time > (advantage of having somebody else do it for me now ;-)). What you've > done with an active dblock (and TODO states being the names of people!) > looks good and should definitely be put on Worg at the very least. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Org mode for meeting minutes
Hi all I'd like to revisit a very old thread[1] where Adam Spiers asks if there is support in Org mode for 1. Allow *fast* production of meeting agendas and minutes, exportable in a good-looking legible format which non-org readers can digest. 2. Allow minutes to be taken as the meeting progresses, minimising the amount of work required after the meeting. 3. Allow actions to be captured and then automatically extracted into a simple tabulated report which clearly shows actions grouped by owner. 4. Track progress of actions *after* the minutes have been issued. He goes on to say that org mode handles (1) and (2) just fine, but he wasn't sure about (3) and (4). His mail is from 2008 and a lot has happened in the mean time. I would suggest that today (1) and (2) can be handled with normal org export or even pandoc. Inline tasks[2] help a lot to add, well inline tasks. For (3) and (4) he mentions a dynamic block that could collect all action items. I never found that dynamic block he mentions, so I hacked one up (which was suprisingly easy). I haven't packaged it but the gist of it is below: ``` elisp (require 'org) (require 'dash) (defun org-actionitems-extract-entry () (-let* ((entries (org-entry-properties)) (( "ITEM" "TODO" "DEADLINE") entries)) (list ITEM TODO DEADLINE))) (defun org-dblock-write:actionitems (params) (let ((match (or (plist-get params :match) "/+TODO"))) (insert-before-markers "| What | Who | When |\n") (insert-before-markers "|-\n") (let* ((tasks (org-map-entries 'org-actionitems-extract-entry match)) (rows (-map (lambda (task) (->> task (-map (lambda (item) (or item ""))) (apply 'format "| %s | %s | %s |"))) tasks)) (table (string-join rows "\n"))) (insert-before-markers table)) (org-table-align))) ``` The idea is that you use type todos using the people involved at the meeting. Below is an example how this could look: ``` org #+title: Meeting minutes #+TYP_TODO: Fred Sara Lucy Mike | DONE ** Present at meeting - [X] Fred - [X] Sara - [X] Lucy ** Agenda - Reports from the sub teams - Discussion ** Notes *** Reports from the sub teams - The order has arrived *** Fred Check if the order is complete DEADLINE: <2019-11-04 Mo> *** END - The next talk is scheduled *** Mike Organize a speaker DEADLINE: <2019-11-12 Di> *** END * Actions #+BEGIN: actionitems :match "/Fred|Sara|Lucy|Mike" | What | Who | When| |+--+-| | Check if the order is complete | Fred | <2019-11-04 Mo> | | Organize a speaker | Mike | <2019-11-12 Di> | #+END: ``` Before I go on with this I'd like to know 1. Is the worg page[3] the state of the art in taking meeting minutes with org mode? 2. Is it worth packaging this code snippet or should I try to submit it to org mode proper? Any thoughts on this or other ideas very welcome! Thanks, Christian Footnotes: [1] https://lists.gnu.org/archive/html/emacs-orgmode/2008-02/msg00117.html [2] https://code.orgmode.org/bzg/org-mode/src/master/lisp/org-inlinetask.el [3] https://orgmode.org/worg/org-tutorials/org-meeting-tasks.html
Re: [O] taskjuggler subtract scheduled and deadline
Bastien <b...@gnu.org> writes: > @Christian: I don't remember if you are still using and > maintaining ox-taskjuggler.el -- feel free to correct me > if I'm wrong! No I'm barely using it anymore, let alone maintaining it. As for Edgars question > Is there a way to set starting and ending times with a resolution of > hours or minutes to be exported with taskjuggler? AFAIK there isn't. Your patch was good start, but your expressions inside the (or ...) were such that the one that collected the time was never executed. I see three options: 1. Hack the exported taskjuggler file. A hack but gets the job done 2. Try to use the START attribute on the node 3. Improve the source of ox-taskjuggler.el as you've started. Hope that helps Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Editing the taskreport plan width value in taskjuggler taskreport output
Rob Stewart <robstewar...@gmail.com> writes:
> The contents of the exported TaskJuggler .tjp file includes:
>
> # A traditional Gantt chart with a project overview.
> taskreport plan "" {
> headline "Project Plan"
> columns bsi, name, start, end, effort, chart
> loadunit shortauto
> hideresource 1
> }
>
> This renders HTML with a fairly narrow Gannt chart on wide screens.
>
> To widen the rendered Gannt chart, I modify the .tjp file manually
> using { width 1000 }, i.e.:
>
> columns bsi, name, start, end, effort, chart { width 1000 }
>
> Is there a way to set an option at the top of my org file, to
> manipulate the "columns... " line in the taskreport { .. } ?
Have you tried to customize org-taskjuggler-default-global-properties?
That might do what you're after.
HTH
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [bug] ox-taskjuggler
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 default one, the one specified in the attributes (drawer)? What exactly doesn't work? Are there two start entries in the task? One because of the SCHEDULED property and one because of the the start property? Then you might have to remove the start property from org-taskjuggler-valid-task-attributes before adding the other valid attributes i.e. ;; Add other valid attributes. (org-taskjuggler--indent-string (org-taskjuggler--build-attributes task org-taskjuggler-valid-task-attributes)) Might have to become (untested) ;; Add other valid attributes. (org-taskjuggler--indent-string (org-taskjuggler--build-attributes task (remq 'start org-taskjuggler-valid-task-attributes))) HTH Christian The problem by removing the start attribute is that it destroys the backward compatibility. I want ox-taskjuggler to accept both methods, where the start property attribute overrules the scheduled attribute, if this is present. I don't understand. You get the start of a task using org-taskjuggler-get-start. This can be either the start attribute or the SCHEDULED attribute. Then you insert this in the task if it is non-nil. Since you have dealt with this attribute already you don't need to handle it in org-taskjuggler--build-attributes. Hence you remove it (just for this call) from the list of task attributes that need to be handled. HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [bug] ox-taskjuggler
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 two start entries in the task? One because of the SCHEDULED property and one because of the the start property? Then you might have to remove the start property from org-taskjuggler-valid-task-attributes before adding the other valid attributes i.e. ;; Add other valid attributes. (org-taskjuggler--indent-string (org-taskjuggler--build-attributes task org-taskjuggler-valid-task-attributes)) Might have to become (untested) ;; Add other valid attributes. (org-taskjuggler--indent-string (org-taskjuggler--build-attributes task (remq 'start org-taskjuggler-valid-task-attributes))) HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [bug] ox-taskjuggler
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 same is probably true for DEADLINES as well. IIRC there was a patch once for deadlines which I never managed to integrate. Anyway what you would like doesn't seem very hard to implement: Just add another statement to the (let*) of org-taskjuggler--build-task where you get the start time using the org-taskjuggler-get-start function. Then just insert the start time in the (concat) statement maybe right after (and priority (format priority %s\n priority)) Let me know if you need any help Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [BUG] ox-taskjuggler: unable to use depends {gapduration}
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 need to merge maint into master. OK, the fix is pushed to maint and merged to master. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [BUG] ox-taskjuggler: unable to use depends {gapduration}
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 error when trying to
use:
:depends: task {gapduration 1h}
Oddly, the output is as follows (task section):
#+begin_src test.tjp
task test test {
task task1 task1 {
milestone
start 2014-11-05-08:00
}
task task2 task2 {
depends !task1 t :taskjuggl
duration 1h
}
#+end_src
For some reason it's grabbing the taskjuggler tag! I tried with the
example in ox-taskjuggler.el with the same result.
Is this a bug or am I mis-interpreting how this would work?
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 funny t :taskjuggl in the output.
Here's the fix.
diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el
index 807d702..9e977f6 100644
--- a/contrib/lisp/ox-taskjuggler.el
+++ b/contrib/lisp/ox-taskjuggler.el
@@ -600,7 +600,7 @@ doesn't include leading \depends\.
(let ((id (org-element-property :TASK_ID dep)))
(and id
(string-match (concat id +\\({.*?}\\)) dep-str)
- (org-match-string-no-properties 1
+ (org-match-string-no-properties 1 dep-str
path)
;; Compute number of exclamation marks by looking for the
;; common ancestor between TASK and DEP.
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?
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [RFC] Change property drawer syntax
John Hendy jw.he...@gmail.com writes: I use this, or at least things like this. For example: * task :PROPERTIES: :start:2014-11-03-08:00 :task_id: task_d :depends: task_a task_b task_c :duration: 30min :END: Not multi-line, but currently I can feed any property that matches a tj3 attribute (e.g. task_id) and Org will do the right thing. This usage is perfectly fine and will continue to work. There are some very obscure attributes that taskjuggler (and the exporter) support, such as note and journalentry. These can span multiple lines. They can be used to add notes or more structured journal entries. A journalentry has several subparts (headline, summary, etc) but I don't think we need to support this. IMHO the best resolution to this is to simply take the two attributes note and journalentry out of the list of exported attributes. Or maybe better yet, add a note to the docstring. Maybe I'll just do that. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [RFC] Change property drawer syntax
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Hello,
Christian Egli christian.e...@sbs.ch writes:
I see that it is too late now, but let me still note that the
taskjuggler exporter is quite liberal in what attribute values it allows
for exporting. I've never used it and I haven't ever seen anyone using
it, but in theory you could give a task a note or a journalentry which
spans multiple lines. This will no longer be possible with this
change.
I'm not sure to understand what is a note or a journalentry which spans
multiple lines. Could you give an example?
Speaking in taskjuggler syntax it would be as follows:
task alpha Alpha Test {
effort 1w
depends !!software
allocate test, dev2
note Hopefully most bugs will be found and fixed here.
journalentry 2002-03-01 Contract with Peter not yet signed {
author boss
alert red
summary -8-
The paperwork is stuck with HR and I can't hunt it down.
-8-
details -8-
If we don't get the contract closed within the next week,
the start of the testing is at risk.
-8-
}
}
AFAIK the org-mode taskjuggler exporter was previously able to handle
this if given the following headline:
* task
:PROPERTIES:
:Effort: 1w
:depends: software
:allocate: test dev2
:note: Hopefully most bugs will be found and fixed here.
:journalentry: 2002-03-01 Contract with Peter not yet signed {
author boss
alert red
summary -8-
The paperwork is stuck with HR and I can't hunt it down.
-8-
details -8-
If we don't get the contract closed within the next week,
the start of the testing is at risk.
-8-
}
:END:
Oh, and btw: there can be more than one journalentry. So, given this
taskjuggler feature is not very often used and drawer machinery is not
really suited for this use case I suggest we just drop support for it.
Maybe the user can just squeeze the whole entry on one line interspersed
with \ns.
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] What to do with taskjuggler's Plan.html report?
Hi Thorsten Thorsten Jolitz tjol...@gmail.com writes: when I run 'tj3' on a taskjuggler file (.tjp) exported from Org, I get the reports as 'Plan.html' file. I can have a look with my browser, but thats not really what I want - I want to integrate the reports in a LaTeX document (exported from Org). Did anybody try to use TJ3 with Org-mode and has some insights here? I've never tried it but tj3 has the possibility to also generate reports csv or XML. So you might be able to create a report which dumps the list of tasks and their dates into a csv. Given this you could try to create a LaTeX document (maybe even using the pgfgantt[1] package). Thanks Christian Footnotes: [1] http://www.ctan.org/pkg/pgfgantt -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [RFC] Change property drawer syntax
Nicolas Goaziou m...@nicolasgoaziou.fr writes: Nicolas Goaziou m...@nicolasgoaziou.fr writes: As discussed previously, I would like to modify property drawers syntax. The change is simple: they must be located right after a headline and its planning line, if any. Feedback welcome. If there is no more feedback or objection, I will merge the branch on Tuesday. I see that it is too late now, but let me still note that the taskjuggler exporter is quite liberal in what attribute values it allows for exporting. I've never used it and I haven't ever seen anyone using it, but in theory you could give a task a note or a journalentry which spans multiple lines. This will no longer be possible with this change. I guess if anyone ever wants to specify notes and journalentries for a task and export this to taskjuggler they will have to put it on one line. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Proper settings for tj3 report directory/output?
Hi John
John Hendy jw.he...@gmail.com writes:
I just re-set up tj3 on a new work computer and am a bit puzzled by
the report directory structure.
If I use C-e J p instead, I get:
~/working_dir/file.org
~/working_dir/file.tjp
~/working_dir/reports/Overview.html
~/working_dir/reports/taskjuggler/{css,examples,icons,scripts}
I cannot reproduce this behaviour.
I'm a bit confused by both behaviors. The variables I've defined in .emacs
are:
org-taskjuggler-target-version: 3.5
org-taskjuggler-default-reports: include reports.tji (custom report
I've defined)
As far as I know, these are relevant but left as the default that came with
org:
org-taskjuggler-proces-command: tj3 --silent --no-color --output-dir %o %f
org-taskjuggler-reports-directory: reports
Your analysis is correct. The pertinent vars are mostly
org-taskjuggler-reports-directory, org-taskjuggler-proces-command and to
some extent org-taskjuggler-target-version. And as you see the exporter
just delegates to tj3 to put the reports in a specific directory by
using --output-dir. This should work.
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Define resources in ox-taskjuggler
Johan Ekh ekh.jo...@gmail.com writes: Error: crc is not a defined resource I've read some documentation/tutorials and I've searched this list but I did not find an answer. Can anyone of you gurus see emmediately what is wrong or at least point me in the right direction? Isn't this just a question of capitalization? In other words try to define the resource_id lowercase crc. HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] column-mode can not do an estimate effort summation on day/week modifiers
Jon Miller joneb...@gmail.com writes: The problem I'm having is with column-mode and the estimate effort sum. What exactly is the problem? That the sum is not in Xd format? Don't know if you can change that. It appears that the normal effort summation wants purely HH:MM formatted work estimates. I thought it also works with things like 1d. It simply converts these to hh:mm AFAIK. HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] org todos on paper?
Christian Moe m...@christianmoe.com writes: You may want to check out Christian Egli's org2hdpa in the contrib/scripts directory, cf. this thread: http://lists.gnu.org/archive/html/emacs-orgmode/2011-05/msg00577.html This script prints a pocketMod calendar that includes entries from the diary file. However if you also want your todo items you need to extend the script. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] taskjuggler - using gaplength or gapduration
Hi all
frank f...@breengeosci.com writes:
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:
*** 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.
gaplength and gapduration need special treatment of the exporter. They
need to be part of the depends statement. So it woll not work if you
just add them as properties. The dependencies section in the comments of
ox-taskjuggler.el has an example how this can be done:
;; * Training material
;; :PROPERTIES:
;; :task_id: training_material
;; :ORDERED: t
;; :END:
;; ** Markup Guidelines
;;:PROPERTIES:
;;:Effort: 2d
;;:END:
;; ** Workflow Guidelines
;;:PROPERTIES:
;;:Effort: 2d
;;:END:
;; * Presentation
;; :PROPERTIES:
;; :Effort: 2d
;; :BLOCKER: training_material { gapduration 1d } some_other_task
;; :END:
Now, I haven't tested this in a long time and AFAIK this used to work. I
don't know if it survived the port to the new exporter framework. I
would recommend that you try the above mentioned method. From looking at
the source code it seems that Nicolas implemented options on
dependencies.
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [FeatureReq]: Move nodes in column view
Thomas Koch tho...@koch.ro writes: I'm just learning about column view. It might be very useful to work on scrum backlogs with column view and storypoints as a column. Have you looked at https://github.com/ianxm/emacs-scrum? It would be wonderful if I could move nodes up and down in column view to reorder the priority of backlog items represented as org nodes. Is this possible already? AFAIK this is not possible. You can setup your column view so that you'll see the priority and from there you should be able to edit it directly in the column view with S-left and S-right. HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] taskjuggler_report questions
Tom Slee slee@gmail.com writes:
I'd like to include the report spec in my org file as a heading tagged
taskjuggler_report but I am having a few issues getting it to work. I
hope someone can help.
The possibility to create (tj3) report definitions in orgmode is a neat
feature and probably works in very simple cases. However I never was
able to use it for the reasons you mention below (e.g. no support for
multi-line properties)
What I usually do is to either define the report using M-x
customize-variable org-export-taskjuggler-default-reports or I set
org-export-taskjuggler-default-reports to simply include
\reports.tji\ and then define the reports externally (using full tj3
syntax).
How do you get a task id into the report? eg report-id in taskreport
report-id FileName {...
Is it possible to do multi-line properties? I'm looking at rich text
markup using -8-
I think for both of these you might have to define the report in tj3
syntax using either of the methods above.
Can you export macro definitions into the file?
You could try customizing org-taskjuggler-default-global-header.
HTH
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Agenda printing: org-agenda-write doesn't use ps-paper-type
Myles English mylesengl...@gmail.com writes: Thanks for checking it. Yes, I had to change this line in org-agenda.el: - (call-process ps2pdf nil nil nil + (call-process ps2pdf nil nil nil -sPAPERSIZE=a4 I wonder if we need to allow a set of options to be passed to ps2pdf as we do for ps? Where do we pass options for ps? A quick rgrep shows that ps2pdf is used in the agenda and two of the exporters (groff and man) so a better option might be to set the papersize via the environment (GS_OPTIONS). Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Tag der offenen Tuer Die SBS laedt Sie herzlich ein: 29. Juni 2013 von 9 bis 16 Uhr. Mehr Informationen erhalten Sie unter http://www.sbs.ch/offenetuer
Re: [O] Org-mode and Taskjuggler
John Hendy jw.he...@gmail.com writes: I'll try to get some further setup instructions up as well as porting Taskjuggler's tutorial file and default report over to the tj3 page within the next week or so. Man, you're my hero. I thought I'd have to do this myself :-) Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Agenda printing: org-agenda-write doesn't use ps-paper-type
Myles English mylesengl...@gmail.com writes: Trying to print an agenda to pdf always results in the paper size being US letter even though ps-paper-type is set to a4. This is how I try to print it: (org-agenda-write /home/myles/tmp/agenda.pdf nil nil *Org Agenda(a)*) org-agenda-write uses ps-print to do the work so setting ps-paper-type should indeed help. and setting this doesn't fix it either: (eval-after-load ps-print '(setq ps-paper-type 'a4)) Have you tried setting this variable with the custom interface, i.e. M-x customize-variable RET ps-paper-type RET? HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Org-mode and Taskjuggler
Hi Louis Louis Turk l...@dayspringpublisher.com writes: I'm very interested in your work to get Org-mode to export to Taskjuggler version 3 --- very exciting! Being able to export to tj3 from org-mode would be extremely helpful to me. Cool. However, I'm having trouble getting it to work. I suspect that the documentation I've been reading is too old --- for version 2 of Taskjuggler---, and I have version 3 installed. Yes, the documentation should be updated. John Hendy promised to do so a while ago :-) (hint, hint). What are the problems you are encountering? It should work out of the box. Once you have an org file as explained on the worg page you just invoke the exporter with C-c C-e J o for example and you should see the schedule in a browser. Would you please send me: 1 The related code in your .emacs file. There is nothing special in my .emacs file. You need to include contrib to your load path (add-to-list 'load-path ~/src/org-mode/contrib/lisp) and you need to enable the taskjuggler exporter (M-x customize org-export-backends). 2 A sample full-featured org-mode file that compiles successfully to tj3. The one on from the taskjuggler tutorial on the worg page should work. 3 Any up-to-date documentation that is available. The best ATM is the tutorial on worg and the comments in the code. 4 Anything other information needed to get it to work. If there is any other info needed then I'd say it is the official TaskJuggler documentation. Thank you in advance for your help. And thanks for all your work already done on this project. My pleasure. HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Tag der offenen Tuer Die SBS laedt Sie herzlich ein: 29. Juni 2013 von 9 bis 16 Uhr. Mehr Informationen erhalten Sie unter http://www.sbs.ch/offenetuer
Re: [O] [Taskjuggler] Status of exporter
Hi Eric Eric S Fraga e.fr...@ucl.ac.uk writes: I must be doing something really silly (not unheard of ;-) but I just cannot get the new tj3 exporter to work. No, you found a bug in the exporter :-(. Any pointers would be most welcome. The problem is that I added a new feature which inserts the TITLE of the document in the report. As it happens if you don't define a title it is empty and the default report becomes invalid. So you could either - define a document title (#+TITLE: Foo) - define an export title (property 'EXPORT_TITLE') - or git pull. I just pushed a fix that should use the headline of the project if the document title is empty. Sorry for the inconvenience. Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch
Re: [O] [PATCH] Smart inference of task progress when exporting to TJ3
Hi Martin Martin Becker vbmaz...@web.de writes: Thank you for these remarks, next time I know. I attached a clean patch. I like this patch, this is good stuff. Can you tell me how you use this? I.e. does tj3 adapt the length fo a task based on your clock table? A few remarks on the patch from my side: + ;; state=done = complete=100 + (if (eq (org-element-property :todo-type task) 'done) 100.0 +;; else if explicit property = use that +(if complete-explicit (string-to-number complete-explicit) + ;; else guess the completeness from clocksum + (let* ((clocked (org-taskjuggler--clocksum-task task)) + (complete-guess + (and effort (/ (* 100 clocked) + (org-duration-string-to-minutes effort) +(and complete-guess (max (min 99 complete-guess) 0))) + ))) I would write this using cond instead of nested if. Makes it more clear. 2. IIUC you don't need the TINYCHANGE cookie because the changes are made in contrib/ which doesn't require copyright assignment. The taskjuggler exporter used to be in core before it was moved to contrib by Bastien or Nicolas on the bases that there aren't many users (and probably because it wasn't maintained very well). This is OK for now, but eventually I'd like to move it back to core. So we need assignment for this patch. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [Taskjuggler] Status of exporter
Hi Eric Eric S Fraga e.fr...@ucl.ac.uk writes: I get errors, having allocated efforts to all my tasks, that tasks do not fit into the project time frame. How is this time frame defined? This is defined on the project. I think it is some kind of tj3 optimization to limit the space that it has to allocate. Do I need to specify something else in the org file? The project I am defining is several years long with tasks typically a number of months long each. Is there some default? There is a default, see `org-taskjuggler-default-project-duration'. In theory (according to the doc string of `org-taskjuggler--build-project') you should also be able to set an end property on the project, but this hasn't been implemented yet. You can set a deadline and this will be used as an end date, but as I said before I might change this as a DEADLINE maps more to maxend. So your best bet at the moment is to use the default project duration. Hope that helps Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [PATCH] Smart inference of task progress when exporting to TJ3
Hi Martin Martin Becker vbmaz...@web.de writes: My idea was, that clock times are only used when there is no explicit information given, viz., when there is neither a property `complete' nor the task state equals done. Since I am clocking most of my activities, it would be convenient for me to let the exporter/TJ3 infer the task progress instead of explicitly giving the `complete' property. So far for the story. Ah, I get it. You are infering the % complete based on how much effort you have already put into a task. The problem is that this doesn't always relate to each other: You might have put a lot of effort into a task and still be only at 10% complete. I.e. does tj3 adapt the length fo a task based on your clock table? No, TJ3 is not adapting anything here, neither am I. Since you cannot give values 100 (%), my patch limits the maximum inferred progress to 99. We could let the exporter overwrite the effort with the clocksum in those cases, but it doesn't seem right. Yes, since this is another problem with infering the complete information from the planed effort and actual effort: You can end up with complete more than 100% :-), namely if the actual effort is bigger than the planed effort. I found out some more details after reading the documentation of TJ3: - The `complete' property is merely for documentation purposes, it's totally ignored by TJ3 when it comes to scheduling. It just looks nice. Yes, I think there are some other draw backs with the complete information. Check the taskjuggler mailing list archives for a discussion on tracking the progress of a project (https://groups.google.com/d/topic/taskjuggler-users/ZCk_est4GKE/discussion). I for one would like it if were used for scheduling. - But there is another thing we could do: One can add bookings to the tasks, which could be exactly the clock times from org-mode. I tried this manually and it seems to be a mixed blessing: If doing so, TJ3 internally grows the effort when the bookings exceed them and reschedules accordingly (which is nice). This is something that would make sense in the exporter. The clocking information that we have in the org file is really what tj3 wants as a booking. On the other hand sensible clock times are vital then. What I mean is, when there are bookings that are too early w.r.t. a task's earliest possible start (due to dependencies etc.), then TJ3 exits with an error. I am not sure this is wanted behavior. What do you think? Yes, it appears that you will have to have bookings for all the tasks to make this work properly. This is a lot of overhead. I'm also not sure this is wanted. But the benefit would be that you can use projection mode in which tj3 will afaik recalculate the duration of the project based an planed and actual effort. Might be worth exploring. Additionally, the visually attractive completeness is not derived from the bookings or anything. Yes. but eventually I'd like to move it back to core. So we need assignment for this patch. Is it that I need to sign something? Have a look at request-assign-future.txt in the org-mode git repo. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [Taskjuggler] Status of exporter
Christian Egli christian.e...@sbs.ch writes: In theory (according to the doc string of `org-taskjuggler--build-project') you should also be able to set an end property on the project, but this hasn't been implemented yet. I remember now what the problem with this was. The exporter uses the top task both as the task and the container for the project[1]. So an start and an end on this task applies to both the project and the task (which is not always what you want). You might want to assign a start to the top task but probably not an end. The end is supposed to be calculated based on efforts and resource availability. But unless you specify a default duration you will have to specify and end date for the _project_. Maybe we need some fake (in the sense that they are not tj3 attributes) attributes to specify start and end of a project. Thanks Christian Footnotes: [1] Unless you set `org-taskjuggler-keep-project-as-task' to nil -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] [Taskjuggler] Status of exporter
Hi all The Taskjuggler Exporter has seen some major updates. We finally have a nice out-of-the-box experience with tj3, so please give it a spin. What's new? Thanks to Nicolas Goaziou the exporter has been ported to the new export engine. On top of that I added some features that have been requested and there are some pending issues that I'd like to get fixed, see below: Changes ═══ Process and open Previously the exporter just exported a tjp file (at least for tj3). Now there is a new command to process the exported tjp file with tj3 and open the reports in a browser. Dependency resolution against plain IDs ─── There was some discussion on the list about dependency resolution. A good way to express dependencies is to use the org-id module. This is now supported in that it resolves dependencies not only against task_id but also against the ID of a task. Default reports can use document title ── John Hendy proposed to create a possibility to integrate the document title in the default reports. This is now possible by specifying a %title in the default reports. See the doc string of `org-taskjuggler-default-reports'. Use both scheduled and start to determine project start ─── John Hendy again reported an problem that the project start was not using the scheduled info. This is now fixed. Misc bug fixes ── Nicolas Goaziou fixed a number of bugs and typos in the code. Pending ═══ Change mapping of DEADLINE property ─── The DEADLINE property is currently mapped to the end attribute in the tjp export. The end attribute gives tj3 an indication as to when a task should end. Also it has some influence on the scheduling policy (ALAP) which might not be what the user expects. IMHO this is not exactly the semantics of the DEADLINE property. A better fit would be the maxend attribute. For that reason I'd like to propose a backward incompatible change to map the DEADLINE property to the maxend attribute. Patch by Baptiste ─ This patch fixes some problems with milestones. However it depends on above change. Add the text nodes as a note It would make sense to export the text content of a headline as a tj3 note. The new export engine should make this possible. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Item task_id not being used in taskjuggler export tj prefixing
John Hendy jw.he...@gmail.com writes: On Mon, Apr 1, 2013 at 5:01 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: You can already do so. IDs only have to be unique within the task siblings. True, one can name tasks identically as long as they have no identical siblings... but the point was the since one can only specify the lowest level of id (e.g. T1 instead of T.T1), Org doesn't know how to resolve them properly. AFAIK task_ids have to be globally unique if you want to use them for dependencies. Task M1 ends up depending on both M.T1 (represented as !T1) /and/ T.T1. It won't fail since both T.T1 and M.T1 exist, but the user has no way to set a depends option to target the specific T1 they wanted. Setting =:depends: !!T.T1= ignores the :depends: property entirely. The TaskJuggler exporter gives you 3 ways to express a dependency: 1. using ORDERED on the parent task 2. using previous-sibling 3. using a task_id of another task. This has to be a unique id, otherwise you end up depending all the other tasks that have this task_id. You don't have to name parents either. You only need to name tasks that will be used as a dependency. True, which is nice. But we're torn between: - Letting Org name the parent whatever it wants, but then having to figure out the org-generated parent id so we can do =:depends: parent.subtask=, or - Specifically naming the parent to have control over the task_id, but having to change it because we move it later (and then updating all =:depends: parent.task_id= properties accordingly) And in either case, there's still no way to depend on a specific =parent.task_id= combination. I don't understand this. Why do you need to name parents (or assign them a task_id)? As Nicolas says: all you have to do is to give the task you want to depend on a task_id. As an aside I thought you could also use plain ID to express dependencies. But from looking at the code this doesn't seem supported. I think the reason why yet another id (namely task_id) is used, is that this allows for short human readable ids where as the standard ID is generally generated by org mode and is cryptic and much longer. HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Setting taskjuggler project start date (ox-taskjuggler)
John Hendy jw.he...@gmail.com writes: On Wed, Mar 27, 2013 at 9:37 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, John Hendy jw.he...@gmail.com writes: If you have =org-taskjuggler-keep-project-as-task=, it will take the :start: property and use this in the project-as-top-level-task output. Could this be used after =scheduled= and before defaulting to today's date? This would seem to unify the syntax. It strikes me as reasonable to take 1) scheduled, 2) :start: in property drawer and 3) default to today's date (in that order). I just pushed a change that should implement this the way you describe above. Also, since I noticed that my tasks pick up the :start: property and that the get-start (item) function *could* pick up a scheduled date as well... might be good to anticipate the case in which the user specifies both (probably accidentally). Maybe just provide an error that either scheduled/deadline *or* :start: should be used, but not both. Currently the org-taskjuggler-get-start function is only used to determine the start of a project or when checking if a task is a milestone (ie has neither a start nor an end), so the problem above is independent of that. But yes it is a problem: if you schedule a task and add a start attribute you will most likely have two start attributes for that task in your tjp file and the tj3 compilation will fail. Wouldn't this be sufficient? Or if scheduled date conflicts with an duration/dependency relationship as well? What do you mean? This to me sounds like it's the job of tj3. Some of this might be handled by the tj3 command on the resultant .tjp file, though. Yes, my sentiments exactly :-) Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Item task_id not being used in taskjuggler export tj prefixing
Buddy Butterfly buddy.butter...@web.de writes: The problem becomes obvious with your example above. Herr you expect that T8 would be unique across all tasks. If there are some other task paths with a task of T8 then this will not work. True, task_ids have to be unique across tasks. For me this was never a problem as I usually do not have that many dependencies (and hence need only a few task_ids) and org-mode has built in infrastructure to create unique ids. You will always run after tj implementing what they have implemented. Why not write: :depends: !!T.T8 directly? Because IMHO org-mode has more to offer in terms of dependencies. I think that the ORDERED and the BLOCKER stuff gives you a good way to model dependencies that is expressive and covers a lot of use cases nicely. TaskJuggler dependencies is fairly low level I think. I'd like to express my dependencies at a higher level. Hope that helps Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Item task_id not being used in taskjuggler export tj prefixing
John Hendy jw.he...@gmail.com writes: Unique ids could be inserted as depends with some simple key strokes and I would't have to use numbered IDs at all. They'd stay with the tasks no matter where I moved them. For that... I'd actually prefer *not* to have to explicitly name the parent since they could move wherever I put them with no consequence. `org-id-copy' will insert a unique ID into your entry (ie your task) and at the same time store it in your kill ring, so you can then yank it where you have the dependency. Can you try this with a custom key binding? As far as I know the dependency resolution should also work with unique id (aka ID) not just with task_ids. HTH Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] ox-taskjuggler : Correct a small typo and deal with Scheduled and deadline in task
Bastien b...@gnu.org writes: Hi Baptiste and Christian, Christian Egli christian.e...@sbs.ch writes: This looks a bit fishy. Shouldn't this be ((start) (format start %s\n start)) I guess this should be (start (format start %s\n start)) Doh, yes of course. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] ox-taskjuggler : Correct a small typo and deal with Scheduled and deadline in task
Hi Baptiste Thanks for the patch. It fixes a pretty bad oversight that you currently apparently cannot define a start and an end using SCHEDULED and DEADLINE (I thought this worked in the old exporter and was maybe lost in the translation). I would like to use the patch but there are a couple of issues: Baptiste bate...@bat.fr.eu.org writes: (effort (org-element-property :EFFORT task)) + (start (org-taskjuggler-get-start task)) + (end (org-taskjuggler-get-end task)) This is obviously OK. @@ -775,6 +777,14 @@ a unique id will be associated to it. (org-taskjuggler-get-id task info) (org-taskjuggler-get-name task)) ;; Add default attributes. + (and milestone + (cond + ((and start end) (format start %s\n maxend %s\n start end)) Are you saying that if we have a milestone, a start and an end date we should define the start and use the end date as a maxend? This seems like an interesting approach. Unfortunately currently `milestone' is true only if there is not both and start and an end date. We should probably also change the definition of milestone (see http://orgmode.org/cgit.cgi/org-mode.git/tree/contrib/lisp/ox-taskjuggler.el#n757). + ((and start) (format start %s\n start)) This looks a bit fishy. Shouldn't this be ((start) (format start %s\n start)) + ((and end) (format start %s\n end Ditto Also we should probably change the definition of `org-taskjuggler-get-start' to also look for a start attribute but that's another story. Can you fix these issues and resend? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] New exporter and defgroup
Hi all The new exporter engine has changed the defcustom names but seems to have kept the names of the defgroups (at least in the case of taskjuggler). This is good as it allowed me to make some backward-incompatible changes. On the other hand when I do a M-x customize-group RET org-export-taskjuggler I get a list of both the old defcustom vars and the new ones. This is very confusing to the user as you appear to have the same cutomizable var twice in the group. Is this a problem with my setup or is this inherent in the new exporter. If the latter how can we deal with this? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] More generic taskjuggler export proposal
Hi Buddy Buddy Butterfly buddy.butter...@web.de writes: I would like propose the following for taskjuggler export as base for a discussion to change export functionality. Thanks for your detailed proposal. It's been a few years since I wrote the taskjuggler exporter and I don't remember all the design decisions. Your idea with the prefix to the attributes is an interesting one. However, the fundamental problem here is that IMHO there is no one-to-one mapping between all the concepts in taskjuggler and org-mode. Fundamentally taskjuggler is a system to plan and track a multi-resource project. I see org-mode more geared towards planing and tracking a single user. Taskjuggler has the concept of scenarios where you can compare a plan against another plan or an actual execution (based on reported effort). This might be doable in org-mode but is not really a natural thing to do. So in essence what I'm trying to say is that the goal behind the taskjuggler exporter was never to give you a complete taskjuggler development environment. For that you are probably better of just editing the tjp files directly. Instead the goal was to let the user take their normal org-mode files and have them export to taskjuggler with minimal changes (i.e. mark the tasks, efforts and the resources). The same holds for the dependency system. As far as I remember it was an explicit decision not to support the taskjuggler dependency system and use the one provided by org-mod instead. I think taskjuggler's dependency system is very low level. The one provided by org-mode fit my use cases (for the occasional dependency) much better (and have support for higher level concepts such as the ORDERED or previous-sibling attribute). The dependency between tasks is one thing that should be supported by org. I do not know what would be the best solution here. Maybe we could get a completion list for the values when adding :tj_depends: properties. I don't quite understand this part of your message. As I said above I think the support for dependencies in the taskjuggler is IMHO quite nice :-). Here I would suggest that one can place this data inbetween #+BEGIN_TASKJUGGLER #+END_TASKJUGGLER This is something I'd like to add support for. I just never got around to look at how this could be implemented. It has some implications as you could destroy your otherwise valid tjp file. But it might cover some of your use cases above. Do you know how this could be done in the new exporter? I still would like to discuss the organisation with multiple projects. What do you think about it? Are you referring to the problem of handling multiple projects and similar resources? I have never done this. How do you do it in plain taskjuggler? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Best way to generate textile from orgmode ?
Bastien b...@gnu.org writes: Hi Marc-Oliver, Marc-Oliver Ihm m...@ihm.name writes: i would like to convert orgmode to textile (which is used within confluence wiki). What is the best way to do this ? The best way would be to write a textile exporter. I agree that this would be for the benefit of everyone. But you could also just export to md and use pandoc to convert to textile. Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [WORG] How to ediff folded Org files?
Michael Brand michael.ch.br...@gmail.com writes: But instead of the above I use this for ediff generally, it persists in Org mode: #+BEGIN_SRC emacs-lisp (add-hook 'ediff-prepare-buffer-hook 'f-ediff-prepare-buffer-hook-setup) (defun f-ediff-prepare-buffer-hook-setup () ;; specific modes (cond ((eq major-mode 'org-mode) (f-org-vis-mod-maximum)) ;; room for more modes ) ;; all modes (setq truncate-lines nil)) (defun f-org-vis-mod-maximum () Visibility: Show the most possible. (cond ((eq major-mode 'org-mode) (visible-mode 1) ; default 0 (setq truncate-lines nil) ; no `org-startup-truncated' in hook (setq org-hide-leading-stars t)) ; default nil (t (message ERR: not in Org mode) (ding #+END_SRC I condensed this to the following since I don't use truncate-lines and org-hide-leading-stars ;; ediff for org-mode files (add-hook 'ediff-prepare-buffer-hook (lambda () (cond ((eq major-mode 'org-mode) (visible-mode 1) But now the problem now is that the visible-mode persists even when I quit ediff. I tried to find a hook which lets me undo the visible-mode but I couldn't find an obvious one. There is ediff-quit-hook but this is done in the ediff-control-buffer. Maybe after all it might be better to use ediff-select-hook and ediff-unselect-hook. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Creating Gantt charts by Exporting to TaskJuggler 3.3.0
Buddy Butterfly buddy.butter...@web.de writes: I still feel the lack of the support for all tj properties a major drawback. @Christian: Did you work on something like the prefix proposal below? This would be real cool as we could then just use any property we would like. As far as I know Yann's patches improved this situation, but as far as I know most of the tj properties are supported anyway. Can you specify which properties are missing? It should be easy to add them in many cases. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [RFC] Simplify attributes syntax
Nicolas Goaziou n.goaz...@gmail.com writes: The following patch simplifies syntax for attributes. From the developer POV, each non-nil value is now read as a string by `org-export-read-attribute'. I looked at your patch but I'm not sure of the implications. In particular I'm unsure if I need to change anything in ox-taskjuggler.el. Is line 402 in org-taskjuggler--build-attributes maybe suspicious? (intern (upcase (format :%s attribute))) Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Copyright/Distribution questions (Emacs/Orgmode)
The following message is a courtesy copy of an article that has been posted to gmane.emacs.devel as well. Jambunathan K kjambunat...@gmail.com writes: I would like to withdraw my pleasure in having these files distributed as part of Org distribution. These files have been published under the GNU GPL[1] which gives everybody the right to modify and redistribute them as long as they comply with the GNU GPL. In other words the current maintainer has every right to include these files in any further release of orgmode. More specifically, I would like to know how copyright assignment works for files that are not yet part of Emacs. The copyright assignment is solely for the purpose of having one copyright owner. This helps for legal disputes and to change the license. However it is not needed for redistribution purposes, i.e. it gives you no legal recourse to stop redistribution of these files. Once you have published them under GNU GPL (and you have) everybody (including the current maintainer of orgmode) has the four freedoms that come with the GNU GPL[2] namely the freedom to use the software for any purpose, the freedom to change the software to suit your needs, the freedom to share the software with your friends and neighbors, and the freedom to share the changes you make. Again IANAL, but then the GNU GPL is pretty clear about this. Hope this helps Christian Footnotes: [1] on mailing lists and in the git repo of orgmode [2] http://www.gnu.org/licenses/quick-guide-gplv3.html -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch
[O] [PATCH 1/3] Taskjuggler export: Fix a reference to a defcustom
* contrib/lisp/ox-taskjuggler.el (org-taskjuggler--build-task): Fix the reference to the target-version defcustom --- contrib/lisp/ox-taskjuggler.el |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index 8db45e9..88641b8 100644 --- a/contrib/lisp/ox-taskjuggler.el +++ b/contrib/lisp/ox-taskjuggler.el @@ -721,7 +721,7 @@ a unique id will be associated to it. (and allocate (format purge %s\n allocate %s\n ;; Compatibility for previous TaskJuggler versions. - (if (= org-export-taskjuggler-target-version 3.0) allocate + (if (= org-taskjuggler-target-version 3.0) allocate allocations) allocate)) (and complete (format complete %s\n comptete)) -- 1.7.10.4 -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch
[O] [PATCH 2/3] Taskjuggler export: Only create a milestone if node has no children
* contrib/lisp/ox-taskjuggler.el (org-taskjuggler--build-task): Fix the check whether a node has no children A milestone should only (automatically) be inserted if a node has no children and no duration defined. --- contrib/lisp/ox-taskjuggler.el | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index 88641b8..9146dfd 100644 --- a/contrib/lisp/ox-taskjuggler.el +++ b/contrib/lisp/ox-taskjuggler.el @@ -696,14 +696,14 @@ a unique id will be associated to it. (effort (org-element-property :EFFORT task)) (milestone (or (org-element-property :MILESTONE task) - (and (org-element-map (org-element-contents task) 'headline - 'identity info t) ; Has task any child? - (not (or effort -(org-element-property :LENGTH task) -(org-element-property :DURATION task) -(and (org-taskjuggler-get-start task) - (org-taskjuggler-get-end task)) -(org-element-property :PERIOD task)) + (not (or (org-element-map (org-element-contents task) 'headline +'identity info t) ; Has task any child? + effort + (org-element-property :LENGTH task) + (org-element-property :DURATION task) + (and (org-taskjuggler-get-start task) + (org-taskjuggler-get-end task)) + (org-element-property :PERIOD task) (priority (let ((pri (org-element-property :priority task))) (and pri -- 1.7.10.4 -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch
[O] [PATCH 3/3] Taskjuggler export: Target tj3 by default
* contrib/lisp/ox-taskjuggler.el (org-taskjuggler-target-version): The default target is now tj3 Since taskjuggler is not developed anymore and hardly any distributions carry it anymore we ought to target tj3 by default now. --- contrib/lisp/ox-taskjuggler.el |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el index 9146dfd..295fad1 100644 --- a/contrib/lisp/ox-taskjuggler.el +++ b/contrib/lisp/ox-taskjuggler.el @@ -182,7 +182,7 @@ the project. :group 'org-export-taskjuggler :type 'string) -(defcustom org-taskjuggler-target-version 2.4 +(defcustom org-taskjuggler-target-version 3.0 Which version of TaskJuggler the exporter is targeting. :group 'org-export-taskjuggler :type 'number) -- 1.7.10.4 -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch
Re: [O] [ANN] TaskJuggler ported to new export framework
Hi all Bastien b...@altern.org writes: Christian, as the TaskJuggler expert out there, and if you have some free time in the next few weeks, please let us know if it works correctly (for TJ2 and TJ3). Sorry, was down with the flu last week. I'll look at it this week. If the Worg page about TaskJuggler needs some update, please feel free to go ahead or ask some help on the list. It does. I'll see what I can do. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [ANN] TaskJuggler ported to new export framework
Nicolas Goaziou n.goaz...@gmail.com writes: If the Worg page about TaskJuggler needs some update, please feel free to go ahead or ask some help on the list. It does. I'll see what I can do. Does it? Even though the internals have been rewritten, it shouldn't change anything to syntax. Did I miss something? Sorry, this is completely orthogonal to the new exporter. These are changes that should have been on the worg page before. E.g. For a while the exporter supported tj3. This fact was never properly publizized and the worg page still shows screen shots with tj2. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Die neue Online-Bibliothek der SBS: Mit wenigen Klicks zum Buch unter http://online.sbs.ch
Re: [O] org export Taskjuggler
Nicolas Goaziou n.goaz...@gmail.com writes: If nothing has been started once the new export framework is installed and the early bugs are fixed, I will do the port. I don't quite understand why we need to port anything. The taskjuggler exporter is different than the other exporters in that it doesn't really export the content of an org file. Instead it just goes through the headlines (using the mapping API), takes some to be tasks and reads the properties of these headlines to build the taskjuggler file. It pretty much ignores any text that is between the headlines (see also the commentary in org-taskjuggler.el). In essence it treats the org file as a tree of nodes with properties that define the tasks, resources and reports. It doesn't use any of the common (old) exporting infrastructure. So woudn't a ported org-taskjuggler.el look exactly like to one that we have today? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] org-caldav feedback
Torsten Wagner torsten.wag...@gmail.com writes: CC. Since Sogo does not allow a print view. Does someone know how to create a printable weekly calendar which contains org-agenda entries? I barley remember there was a possibility to create a PDF but can't find it anymore There are the cal-tex-* functions which produce tex from diary files. See the info entry on Writing Calendar Files. Also there is a Makefile which uses the cal-tex-* functions to generate hipster style printouts in contrib/scripts/org2hpda. This might serve as an inspiration. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Creating Gantt charts by Exporting to TaskJuggler 3.3.0
Buddy Butterfly buddy.butter...@web.de writes: thanks for info. I will give this a try when I'll find the time. At the moment, because of the scrambled handling of task_ids it is not really usable. What exactly is the problem with the handling of task_ids? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Creating Gantt charts by Exporting to TaskJuggler 3.3.0
Yann Hodique yann.hodi...@gmail.com writes: At the moment I'm kinda contemplating doing a major rewrite of the TJ exporter to use the org-export framework That might be a good idea. The currect tj exporter doesn't use any of the exporting framework. OTOH it is not really a classic exporter in the sense that it exports the content. Instead it uses the headlines as nodes and exports those using some conventions. If this can be handled with the new exporter then sure go for it. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [PATCH v3 00/11] Taskjuggler exporter improvements
Hi Yann Bastien b...@altern.org writes: I have now applied those patches to master. I guess we should update the tutorial on worg (http://orgmode.org/worg/org-tutorials/org-taskjuggler.html). Would you have time to have a stab at this? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [PATCH 07/10] org-taskjuggler: make project umbrella task optional
Yann Hodique yann.hodi...@gmail.com writes: Christian == Christian Egli christian.e...@sbs.ch writes: I'm trying to understand the use case here. If I understand correctly the container headline will no longer unconditionally generate a root task. So you could have multiple root tasks? Does this work in both versions of tj? Yes, basically the use case is the following. [snip] AFAICT it seems to work fine with either tj2 or tj3. OK this clears it up. So basically all the patches are fine from my pov. Thanks again. Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [PATCH 00/10] Takjuggler exporter improvements
Hi Yann Yann Hodique yann.hodi...@gmail.com writes: Here are a couple of patches for org-taskjuggler.el My main goals with these were to: - be able to leverage SCHEDULE/DEADLINE information, so as to be able to leverage org timelines in complement to the reports - be able to #+BIND some of the exporter variables (such as the preamble) - be able to define reports in the org file itself, without having to mess with a custom variable Any feedback is highly welcome. I have looked at your patches. I have not had time to try them but reading the diffs it looks excellent. They implement some features which make the exporter much more flexible. I have one comment to patch make project umbrella task optional which I'll adress separately. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [PATCH 07/10] org-taskjuggler: make project umbrella task optional
Yann Hodique yann.hodi...@gmail.com writes: +(defcustom org-export-taskjuggler-keep-project-as-task t + Whether to keep the project headline as an umbrella task for + all declared tasks. Setting this to nil will allow maintaining + completely separated task buckets, while still sharing the same + resources pool. I'm trying to understand the use case here. If I understand correctly the container headline will no longer unconditionally generate a root task. So you could have multiple root tasks? Does this work in both versions of tj? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Export to multiple HTML files?
Nicolas Goaziou n.goaz...@gmail.com writes: But is there such a function ready to use? I don't think so. Ready to use, no. But since you can specify your own publishing function, it should be doable. Actually if you use the mapping API[1] such a function should be fairly easy to write. Footnotes: [1] http://orgmode.org/manual/Using-the-mapping-API.html#Using-the-mapping-API -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Question: split up files for subprojects using taskjuggler-export (tj3)
Hi m...@dittmaridoo.de writes: I am looking for a solution to split one project into sub-projects, so I can distribute the project into sub-files as suggested here: http://groups.google.com/group/taskjuggler-users/browse_thread/thread/a98489a0e343ddac The export of org-mode to taskjuggler can be taken pretty far and can handle big projects. It is meant for people comfortable with org-mode that like to work within org-mode. However not all concepts in org-mode for example have a corresponding concept in taskjuggler and vice versa. The exporter tries to bridge this mismatch in some cases and ignores others. So, what I'm saying is that if you want the full power of taskjuggler then by all means go for it (i.e. hack your stuff in it directly). If you want the convenience of org-mode then stay with it and try to organize the project within org-mode. IMHO using org-mode lessens the need to structure the projects into sub-files as org-mode is less verbose and inherently more structured. If you still would like to split you project some more I'd try to do something using (tj) include statements, e.g. defining them as your default reports. Hope that helps. Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] taskjuggler (tj3) export issues and proposals
John Hendy jw.he...@gmail.com writes: First off let me say that I'm using the taskjuggler exporter with tj3, so it should work. This statement seems to indicate that org may work out of the box with tj3. Well if you take it out of the box it doesn't work with tj3. You need to adapt the target version and the default reports. I think it might be time to change this since most distros do not have taskjuggler2.4 anymore (except Debian stable is still happily using it) and tj2.4 doesn't even run on Windows or Mac. The exporter just makes the task_id locally unique. That's what tj expects. From your usage I guess that you have a lot of tasks with the same name (probably within different hierarchies). Both methods you outline could be implemented. Which one is more general? Maybe parent_headline_task_headline? But that gets tricking for: * Task Container ** Send product samples to X ** Send product samples to Y ** Send product samples to Z Append a number? My files are not [too] complex; perhaps the exporter should be done while thinking of how org might have worked for the Fedora tj example (http://www.taskjuggler.org/tj3/examples/Fedora-20/f-20.tjp). I had a look at the Fedora tj example. This is using tj to the max. It might not be a good use case for the tj exporter :-). But to understand your use case, could you maybe send me some example org files of yours, so I could look at them (off-list if you like) Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] OT: taskjuggler question
Nick Dokos nicholas.do...@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. 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. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] taskjuggler (tj3) export issues and proposals
with a clever way to do this. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] TaskJuggler 3.1 export (tj3)
Hi Rainer Rainer M Krug r.m.k...@gmail.com writes: I would like to use the export to taskjuggler, but somehow I don't get it working - might be me or the fact that I have taskjuggler 3.1.0. I am trying the example on http://orgmode.org/worg/org-tutorials/org-taskjuggler.html but I somehow don't get it to work. Export to a file which can be consumed by tj3 should work. Opening the exported file with tj2 silently fails if you do not have tj2 installed. What exactly isn't working? My questions are: 1) does the taskjuggler export work with tj3 (version 3.1.0) (John Hendy says it doesn't (taskjuggler (tj3) export issues and proposals), but there are patches which should have made it work (e.g. Christian Egli, small edits to org-taskjuggler.el for tj3). So: what is the actual status? As I said, export to tj3 should work. See also my resonse to John Hendy. 2) does the example (url above) work for tj3? The example file should work. Set org-export-taskjuggler-target-version to 3 and set the org-export-taskjuggler-default-reports to something that tj3 understands. Export to tj3 should be done using C-c C-e j (org-export-taskjuggler), as C-c C-e J silently fails if you don't have TaskJugglerUI (aka tj2.4) installed. On the resulting tjp file run tj3 and open the result in a browser. 3) if no, could somebody provide a simple example org file which works with tj3? The example file works if I follow the steps above. Let me know if you have any problems. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] taskjuggler (tj3) export issues and proposals
Rainer M Krug r.m.k...@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.
Thanks
Christian
#+PROPERTY: Effort_ALL 2d 5d 10d 20d 30d 35d 50d
#+PROPERTY: allocate_ALL dev doc test
#+COLUMNS: %30ITEM(Task) %Effort %allocate %BLOCKER %ORDERED
* Accounting Software
:taskjuggler_project:
** Specification
:PROPERTIES:
:Effort: 20d
:BLOCKER: start
:allocate: dev
:END:
** Software Development
:PROPERTIES:
:ORDERED: t
:BLOCKER: previous-sibling
:priority: 1000
:allocate: dev
:END:
*** Database coupling
:PROPERTIES:
:Effort: 20d
:END:
*** Back-End Functions
:PROPERTIES:
:Effort: 30d
:task_id: back_end
:END:
*** Graphical User Interface
:PROPERTIES:
:Effort: 35d
:allocate: paul, seb
:END:
** Software testing
:PROPERTIES:
:ORDERED: t
:BLOCKER: previous-sibling
:allocate: test
:END:
*** Alpha Test
:PROPERTIES:
:Effort: 5d
:task_id: alpha
:END:
*** Beta Test
:PROPERTIES:
:Effort: 20d
:task_id: beta
:allocate: test, paul
:END:
** Manual
:PROPERTIES:
:Effort: 50d
:task_id: manual
:BLOCKER: start
:allocate: doc
:END:
** Milestones
*** Project start
:PROPERTIES:
:task_id: start
:END:
*** Technology Preview
:PROPERTIES:
:BLOCKER: back_end
:END:
*** Beta version
:PROPERTIES:
:BLOCKER: alpha
:END:
*** Ship Product to Customer
:PROPERTIES:
:BLOCKER: beta manual
:END:
* Resources :taskjuggler_resource:
** Developers
:PROPERTIES:
:resource_id: dev
:END:
*** Paul Smith
:PROPERTIES:
:resource_id: paul
:END:
*** Sébastien Bono
:PROPERTIES:
:resource_id: seb
:END:
*** Klaus Müller
** Others
*** Peter Murphy
:PROPERTIES:
:resource_id: doc
:limits: { dailymax 6.4h }
:END:
*** Dim Sung
:PROPERTIES:
:resource_id: test
:END:
* File Variables
# Local Variables:
# org-export-taskjuggler-target-version: 3.0
# org-export-taskjuggler-default-reports: (include \reports.tji\)
# compile-command: ~/.gem/ruby/1.9.1/bin/tj3 foo.tjp
# End:
textreport report Plan {
formats html
header '== -query attribute=name- =='
center -8-
[#Plan Plan] | [#Status Status] | [#Resource_Allocation Resource Allocation]
=== Plan ===
[report id=plan]
=== Status ===
[report id=status.completed]
[report id=status.ongoing]
[report id=status.future]
=== Resource Allocation ===
[report id=resourceGraph]
-8-
}
# A traditional Gantt chart with a project overview.
taskreport plan {
headline Project Plan
columns bsi, name, start, end, effort, chart
loadunit shortauto
hideresource 1
}
taskreport status {
columns bsi, name { width 150 }, start { width 100 }, end { width 100 },
effort { width 75 }, status { width 75 }, gauge {width 150 }
loadunit shortauto
taskreport completed {
headline Completed tasks
hidetask plan.complete 100.0
sorttasks plan.start.up
}
taskreport ongoing {
headline Ongoing tasks
hidetask ~(isleaf() (plan.start = ${now}) (plan.complete 100.0))
}
taskreport future {
headline Future tasks
hidetask ~(plan.start ${now} (plan.complete 100.0))
}
}
# A graph showing resource allocation. It identifies whether each
# resource is under- or over-allocated for.
resourcereport resourceGraph {
headline Resource Allocation Graph
columns no, name, effort, weekly
loadunit shortauto
hidetask ~(isleaf() isleaf_())
sorttasks plan.start.up
}
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
-
Neu bei der SBS: 9000 Buecher kaufen oder schenken. Mehr dazu finden Sie unter
http://www.sbs.ch/verkauf
Re: [O] taskjuggler (tj3) export issues and proposals
John Hendy jw.he...@gmail.com writes: Exports fine, but I get this error: ./reports.tji:33: Error: Unexpected token 'gauge' found. Expecting one Is gauge in your tweaks or is this a tj 2.x.x specific syntax? Ah, sorry. 'gauge' seems to only work in tj3 3.1.0. By the way, nice report! I was trying to squezze it all into one html file so I can open it easier from Emacs. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Neu bei der SBS: 9000 Buecher kaufen oder schenken. Mehr dazu finden Sie unter http://www.sbs.ch/verkauf
[O] Anyone going to FOSDEM?
Hi all I'm trying to figure out what talks and DevRooms I should go to at FOSDEM and I was wondering if some fellow orgers are going to be there. Maybe we could meet for a chat, for dinner or even some hacking. Unfortunately there doesn't seem to be a GNU devroom this year. Is there any interest for a meetup? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] How to estimate effort by week?
Christoph LANGE ch.la...@jacobs-university.de writes: is there any way of estimating effort by week? Have a look at the doc string of org-effort-durations. Documentation: Conversion factor to minutes for an effort modifier. Each entry has the form (MODIFIER . MINUTES). In an effort string, a number followed by MODIFIER is multiplied by the specified number of MINUTES to obtain an effort in minutes. For example, if the value of this variable is ((hours . 60)), then an effort string 2hours is equivalent to 120 minutes. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] org-taskjuggler export problems
Hi Johnny yggdra...@gmx.co.uk writes: I am trying to export a simple project plan from org to taskjuggler through org-taskjuggler.el. I cannot get the behavour I expect and need do some manual tweaks to get the taskjuggler file working. What am I doing wrong? You're not doing anything wrong. You've hit some bugs in the taskjuggler exporter. 1) The 'end' date specified in the ':taskjuggler_project' base is ignored and the default 280d is used. Because the project duration is long this throws an error. The 'start' date however seems properly picked up. Indeed the end date is not picked up. I remember to have tried to fix this once, but the problem is that the root task serves as both a container for the project attributes and is a task at the same time. So if you define the end, you'll both define the end of the project and the task, which might not be what you want. Can you try to increase the org-export-taskjuggler-default-project-duration instead? 2) The 'task_id' fields are not exported properly. The taskjuggler exporter uses the task_ids you define just for dependency resolution. Other than that it creates automatic ids based on the title of the task. The assumption is that you are not that interested in defining ids. What do you need them for? 3) The 'precedes' property is not exported at all Yes, this is not implemented. Could you use 'depends' instead? And possibly use alap scheduling? Hope that helps Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Asciidoc
Hi Stephen Nelson-Smith sanel...@gmail.com writes: I have a large piece of writing to do, which my publisher wants in asciidoc. I'd prefer to write in orgmode and export as asciidoc. I used to use asciidoc but much prefer orgmode now. Is this feasible? Anyone doing this or done this before? Not directly as far as I know. You have different options: - Export to odt and from there to mediawiki followed by some text munging - Use the generic exporter to generate mediawiki again followed by some text munging - Tweak the generic exporter (don't know how feasible and easy that is) - Write an exporter. For simple ascii exporter that should be doable. There are however different competing starting points. There is an experimental generic exporter by Bastien and there is apparently one by Jambunathan. Can't tell you which one is better. Hope that helps -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Patch for bug in adjusting time ranges in Agenda
Hi Carsten Carsten Dominik carsten.domi...@gmail.com writes: I have just checked in a slightly modified patch. I think there is a problem with this checkin. The variable org-agenda-move-date-from-past-immediately-to-today is not defined. Should this be a defcustom somewhere? Debugger entered--Lisp error: (void-variable org-agenda-move-date-from-past-immediately-to-today) org-agenda-date-later(1) org-agenda-do-date-later(nil) call-interactively(org-agenda-do-date-later nil nil) Thanks -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] The org paper manual - tools used
Nick Dokos nicholas.do...@hp.com writes: Marcelo de Moraes Serpa celose...@gmail.com wrote: How was the process, from org file to tex to paper? I think it'd be nice if whoever did it (Carsten?) documented that on Worg. Org is amazing as a publishing platform (for books and ebooks), but I feel the information is still scattered around. Unfortunately, the org documentation is not an org file: org.texi is the primary file and it has always been a texinfo file. makeinfo is used to turn it into an info file, and texi2pdf is used to turn it into a PDF file (and thence to paper): see the org Makefile. Well, back in the olden days the documentation was simple plain text inside of org.el which I eventually converted into a texinfo file. Texinfo has some very nice features which at the time org-mode did not even dream of having (it did not have an agenda and probably no exporters). -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Time estimates time format?
Johan Ekh ekh.jo...@gmail.com writes: But I'd like to make estimates in days, weeks or even months. You can certainly do that. Have a look at org-effort-durations. You could for example define the effort as '2d', '4w' or '7m'. And have spent time displayed in percentage of the estimate. Is this possible? You might be able to do something along this line. Have a look at the doc string of org-properties-postprocess-alist where it gives you an example on how to calculate the remaining time (clocked vs estimated). HTH -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Time estimates time format?
Johan Ekh ekh.jo...@gmail.com writes:
Thank you,
I've changed to
#+PROPERTY: Effort_ALL 2d 1w 2w 3w 4w 2m
#+COLUMNS: %40ITEM(Task) %17Effort(Estimated Effort){:} %CLOCKSUM
but there is no mapping between days, weeks, months and hours. For example,
'2d' + '1w' is summed as '3:00'. How can I change this?
Ah, according to http://orgmode.org/org.html#Column-attributes the {:}
sums the times and treats the times as HH:MM, plain numbers are hours.
I guess this is a bug? You can define efforts in terms of weeks, etc.
Some parts of org-mode respect it but column view apparently not. Sorry.
Patches or even just proper bug reports are welcome.
Thanks
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
-
Viel Neues fuer Hoerspiel-Fans: Eine aktuelle Uebersicht des Angebots bei der
SBS finden Sie unter http://www.sbs.ch/hoerspiele .
Re: [O] Publishing problem on Worg due to babel intro
Eric Schulte schulte.e...@gmail.com writes: Christian Egli christian.e...@sbs.ch writes: In the mean time I moved the intro to the FIXME directory so that my stuff would be published on worg. Now that the intro exports do you want me to move it back to where it belongs? Yes, that would be great. Thanks -- Eric Done. Thanks -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Viel Neues fuer Hoerspiel-Fans: Eine aktuelle Uebersicht des Angebots bei der SBS finden Sie unter http://www.sbs.ch/hoerspiele .
Re: [O] Publishing problem on Worg due to babel intro
Eric Schulte schulte.e...@gmail.com writes: When writing a code block *all* variables require a default value. I've added default values to all of the variables in this file and it now exports as expected. In the mean time I moved the intro to the FIXME directory so that my stuff would be published on worg. Now that the intro exports do you want me to move it back to where it belongs? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland - Viel Neues fuer Hoerspiel-Fans: Eine aktuelle Uebersicht des Angebots bei der SBS finden Sie unter http://www.sbs.ch/hoerspiele .
[O] Publishing problem on Worg due to babel intro
Hi all I enhanced the taskjuggler tutorial on worg. However the fix is not published as there is a problem with the intro page for Babel[1] (see also the publishing report[2]). The page also fails if I try to publish it locally with the following error message: mapc: Wrong type argument: consp, nil I don't understand where the problem is with this page but I'd appreciate if any of the authors (Eric, Dan, Tom) or anyone else could look into it. Thanks Christian Footnotes: [1] http://orgmode.org/worg/org-contrib/babel/intro.html [2] http://orgmode.org/worg/publishing.txt -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Agenda Bulk Scatter bug
Robert Cunningham ro...@iinet.net.au writes: for a few weeks now, and including the git commit af677f6d0667bacba72defeaee7e76557e68f8c8 that I last tested, the Agenda Bulk Scatter (BS) has had a bug whereby items it reschedules have the DATE lost. Please, please, if you'd like to get your bug fixed, provide a detailed bug report[1] and better yet do a git bisect[2] to track down which change caused the regression. This will greatly increase the chances of the bug actually getting fixed. Thanks Christian Footnotes: [1] http://orgmode.org/org.html#Feedback [2] http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [PATCH] Support for more flexible effort specifications in TaskJuggler exporter
Hi Stuart Stuart Hickinbottom stu...@hickinbottom.com writes: I've been experimenting with tracking medium-sized tasks in org as a work-breakdown and exporting to TaskJuggler to see just how many evenings and weekends I'll have to work to meet my promised deadlines! A recent patch (patch 638, 6th Match 2011) added support for more flexible effort estimate properties such as 4h, 3.5d etc. Unfortunately, at the moment the TaskJuggler exporter is more fussy over this property and only accepts HH:MM or an integer, both of which it translates to a number of days when exporting. The attached patch adds support for passing-through effort specifications when they're in the form REAL UNIT as they are for TJ, supporting the suffixes d, w, m and y in a consistent way to org. Support for HH:MM or bare number of days should still work as before. It also cleans up another couple of things about the export of effort: - HH:MM produces a floating point days duration now (was previously rounded to an integer) - The bare REAL effort regex failed to escape the decimal point (and would match any char) - Regexes now anchor to the string start to avoid matching the end of duff values - Docstring updated for more flexible effort specification Thanks for your patch. I just pushed a patch along the lines of yours which uses the built-in facilities of orgmode. It handles all effort durations that are defined in `org-duration-string-to-minutes'. This brings it in line with the rest of orgmode's effort handling. It also fixes the documentation in org.texi. Can you check and see if this fixes all your issues? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] [Taskjuggler] Backwards incompatible change [was: Support for the new effort durations?]
Christian Egli christian.e...@sbs.ch writes: The Effort property previously had no unit attached. With release 7.5 of orgmode you can now attach units to it such as 4h, 2d or 2m. The taskjuggler exporter however doesn't support this feature yet. It currently assumes that if is simply a number that we are talking about days. If the format is something like 5:30 it assumes that the effort is in hours:minutes. It has no support for other formats (weeks, months which taskjuggler itself would support). Now I suppose the exporter should honor the new effort durations that were introduced in 7.5. This is not that hard to change. However this would mean that existing orgmode files will be exported differently, i.e. the change is not backwards compatible. At the moment I do not know how to deal with this. Should I just move to the new effort durations and ask the user to upgrade their orgmode files or more specifically to upgrade their effort properties to the new effort durations format? I pushed a change now which supports the new effort durations. However this change is NOT BACKWARDS COMPATIBLE. Previously the exporter assumed that effort estimates such as '2' meant 2 days. It now assumes that you are talking about 2 minutes. In order to get the same result when exporting change plain effort estimates such as '2' to '2d'. M-x query-replace-regexp should get you there. The info file is updated. I need to fix the tutorial on worg. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] (French/german) Collecting holidays?
Philipp Haselwarter philipp.haselwar...@gmx.de writes: Would it make sense to share setups for `holiday-local-holidays'? Maybe on worg or emacs-wiki? I'm looking for french and german holidays, if anyone happens to have those set up :) Have you checked http://www.emacswiki.org/emacs/CalendarLocalization#toc12? -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [Patch] For the Manual: using org-crypt
Carsten Dominik carsten.domi...@gmail.com writes: Is anyone working on making this a complete patch? Sorry, no. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] print booklet from orgmode
Matt Lundin m...@imapmail.org writes: Marc Spitzer mspit...@gmail.com writes: http://www.toodledo.com/booklet.php Does org mode have such a feature? Here's an old post with a script to generate something similar. I have no idea whether it still works: http://permalink.gmane.org/gmane.emacs.orgmode/3910 As far as I know it should still work and is included in the contrib/scripts directory under the name of org2hpda (see http://orgmode.org/w/?p=org-mode.git;a=blob;f=contrib/scripts/org2hpda;hb=HEAD). I guess if you also wanted to have the top tasks you need to enhance the script somewhat, i.e. invoke an agenda view in Emacs, export and include it in the booklet. Let me know if you have any problems. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [semi-OT] issue trackers?
Matt Price mopto...@gmail.com writes: I'm collaborating on a project where I'm starting to feel the need for a shared issue tracker. Anyone have any suggestions? We use Redmine[1] here which is very nice and flexible. What I do is that I read the tasks from Redmine into org-mode using org-feed.el[2]. I have not had the time to implement a way to push my changes back to redmine. This should be doable as Redmine has a RESTful interface. John Wiegeley has shown a way to push back data to Bugzilla[3]. Hope that helps Christian Footnotes: [1] http://www.redmine.org/ [2] http://orgmode.org/worg/org-contrib/org-feed.html [3] http://www.mail-archive.com/emacs-orgmode@gnu.org/msg25391.html -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Build error in git HEAD with org-bibtex.el
Hi all When doing a `make update` I get the following compile error: ~/src/org-mode $ make update git pull Already up-to-date. /usr/bin/make clean make[1]: Entering directory `/home/eglic/src/org-mode' [snip] emacs -batch -q -no-site-file -eval (setq load-path (cons (expand-file-name \./lisp/\) (cons \/usr/local/share/emacs/site-lisp\ load-path))) -f batch-byte-compile lisp/org-bibtex.el In toplevel form: lisp/org-bibtex.el:257:8:Error: Byte-compiling a redefinition of `get' will not work - use `labels' instead make[1]: *** [lisp/org-bibtex.elc] Error 1 make[1]: Leaving directory `/home/eglic/src/org-mode' make: *** [update] Error 2 This is using GNU Emacs 23.1.1 (x86_64-pc-linux-gnu, GTK+ Version 2.22.0) of 2011-03-04 on yellow, modified by Debian Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] Formal description of Org files
Carsten Dominik carsten.domi...@gmail.com writes: At FOSDEM, someone asked me if there was a formal description of the structure of Org files, in some language that would be the input for a parser (or parser generator?) so that Org file could be easily parsed. Maybe the person was talking about antlr[1], ANother Tool for Language Recognition, a language tool that provides a framework for constructing recognizers, interpreters, compilers, and translators from grammatical descriptions containing actions in a variety of target languages. It even seems to have preliminary support for generating an elisp parser[2][3] There is also an emacs mode for editing antlr files[4]. Sounds like an interesting project. Thanks Christian Footnotes: [1] http://www.antlr.org/ [2] http://www.antlr.org/wiki/display/ANTLR3/Code+Generation+Targets [3] https://github.com/olabini/antlr-elisp [4] http://antlr-mode.sourceforge.net/ -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: [taskjuggler] small edits to org-taskjuggler.el for tj3
Christian Egli christian.e...@sbs.ch writes:
* in org-taskjuggler-open-project, the duration is never calculated
(default is always used).
Good catch and thanks for your patch. Unfortunately the patch causes
problems with my export. The duration is now correctly calculated,
however the root task now also has an end attribute which causes
problems down the road and TJ2 tells me that End of task foo does not
fit into the project time frame. Try using a later project end date.
But no matter how much I put the end date into the future the issue
remains. If I remove the end attribute from the root task it seems to
work.
The following patch seems to work. If you're OK with it I will commit.
diff --git a/lisp/org-taskjuggler.el b/lisp/org-taskjuggler.el
index f891634..20bd91f 100644
--- a/lisp/org-taskjuggler.el
+++ b/lisp/org-taskjuggler.el
@@ -553,11 +553,11 @@ specified it is calculated
(headline (cdr (assoc headline project)))
(version (cdr (assoc version project)))
(start (cdr (assoc start project)))
- (end (cdr (assoc end project
+ (period (or (cdr (assoc period project))
+ (format %s +%sd start
org-export-taskjuggler-default-project-duration
(insert
- (format project %s \%s\ \%s\ %s +%sd {\n }\n
-unique-id headline version start
-org-export-taskjuggler-default-project-duration
+ (format project %s \%s\ \%s\ %s {\n }\n
+unique-id headline version period
(defun org-taskjuggler-filter-and-join (items)
Filter all nil elements from ITEMS and join the remaining ones
Thanks
Christian
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: Test framework needed
Rainer M Krug r.m.k...@gmail.com writes: http://www.emacswiki.org/emacs/UnitTesting Am I right in assuming, that all of the possible test frameworks would require org files and the expected output (tengle, export to ..., agenda, ...)? In this case, would it make sense to start collecting those, as they can easily be user contributed, consequently representing a cross section of the use cases (even not intended use cases)? Before you go too far with this; Orgmode already contains a unit test suite. Look at the README in the testing directory (http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=testing/README.org;hb=HEAD) -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] [TaskJuggler][Poll] Support for the new effort durations?
The Effort property previously had no unit attached. With release 7.5 of orgmode you can now attach units to it such as 4h, 2d or 2m. The taskjuggler exporter however doesn't support this feature yet. It currently assumes that if is simply a number that we are talking about days. If the format is something like 5:30 it assumes that the effort is in hours:minutes. It has no support for other formats (weeks, months which taskjuggler itself would support). Now I suppose the exporter should honor the new effort durations that were introduced in 7.5. This is not that hard to change. However this would mean that existing orgmode files will be exported differently, i.e. the change is not backwards compatible. At the moment I do not know how to deal with this. Should I just move to the new effort durations and ask the user to upgrade their orgmode files or more specifically to upgrade their effort properties to the new effort durations format? Thoughts? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: [Patch] For the Manual: using org-crypt
the following in your
+@file{.emacs}:
+
+@example
+(require 'org-crypt)
+(org-crypt-use-before-save-magic)
+(setq org-tags-exclude-from-inheritance (quote (crypt)))
+;; GPG key to use for encryption
+;; Either the Key ID or set to nil to use symmetric encryption.
+(setq org-crypt-key nil)
+@end example
+
+If you want to use Public Key Encryption, you will need to generate a
+suitable pubic/private key pair using @command{gnupg}.
+
+Now any text below a headline that has a @samp{:crypt:} tag will be
+automatically be encrypted when the file is saved. If you want to use a
+different tag just customize the @code{org-crypt-tag-matcher} setting.
+
+Preventing tag inheritance stops you having encrypted text inside encrypted
+text.
+
+To decrypt the text just call @kbd{M-x org-decrypt-entry} and the encrypted
+text where the point is will be replaced with the plain text. If you use this
+feature a lot, you will probably want to bind @kbd{M-x org-decrypt-entry} to
+a key.
@node Hacking, MobileOrg, Miscellaneous, Top
@appendix Hacking
--
Christian Egli
Swiss Library for the Blind, Visually Impaired and Print Disabled
Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] [PATCH 3/3] Fix a typo in the commentary.
From: Christian Egli christian.e...@sbszh.ch * org-taskjuggler.el: Fix a typo in the commentary. --- lisp/org-taskjuggler.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-taskjuggler.el b/lisp/org-taskjuggler.el index bcf2c45..f891634 100644 --- a/lisp/org-taskjuggler.el +++ b/lisp/org-taskjuggler.el @@ -144,7 +144,7 @@ ;; - Look at org-file-properties, org-global-properties and ;; org-global-properties-fixed ;; - What about property inheritance and org-property-inherit-p? -;; - Use TYP_TODO as an way to assign resources +;; - Use TYPE_TODO as an way to assign resources ;; - Make sure multiple dependency definitions (i.e. BLOCKER on ;; previous-sibling and on a specific task_id) in multiple ;; attributes are properly exported. -- 1.7.1
[O] [PATCH 1/3] Replace recursive implementation with an iterative one
From: Christian Egli christian.e...@sbszh.ch * org-taskjuggler.el (org-taskjuggler-assign-resource-ids): Replace recursive implementation with an iterative one. That way we can avoid to have ask users to increase `max-lisp-eval-depth'. --- lisp/org-taskjuggler.el | 16 +++- 1 files changed, 7 insertions(+), 9 deletions(-) diff --git a/lisp/org-taskjuggler.el b/lisp/org-taskjuggler.el index 9c88f5d..279f46d 100644 --- a/lisp/org-taskjuggler.el +++ b/lisp/org-taskjuggler.el @@ -418,15 +418,13 @@ deeper), then it's not a leaf. (defun org-taskjuggler-assign-resource-ids (resources) Given a list of resources return the same list, assigning a unique id to each resource. - (cond - ((null resources) nil) - (t -(let* ((resource (car resources)) - (unique-id (org-taskjuggler-get-unique-id resource unique-ids))) - (push (cons unique-id unique-id) resource) - (cons resource - (org-taskjuggler-assign-resource-ids (cdr resources) -(cons unique-id unique-ids))) + (let (unique-ids new-list) +(dolist (resource resources new-list) + (let ((unique-id (org-taskjuggler-get-unique-id resource unique-ids))) + (push (cons unique-id unique-id) resource) + (push unique-id unique-ids) + (push resource new-list))) +(nreverse new-list))) (defun org-taskjuggler-resolve-dependencies (tasks) (let ((previous-level 0) -- 1.7.1
[O] [PATCH 2/3] Fix allocations handling for tj3
From: Christian Egli christian.e...@sbszh.ch * org-taskjuggler.el (org-taskjuggler-open-task): Only emit a purge allocations statement if we are not targeting tj3. --- lisp/org-taskjuggler.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/org-taskjuggler.el b/lisp/org-taskjuggler.el index 279f46d..bcf2c45 100644 --- a/lisp/org-taskjuggler.el +++ b/lisp/org-taskjuggler.el @@ -660,8 +660,8 @@ org-mode priority string. (format depends %s\n previous-sibling) (and depends (format depends %s\n depends))) (and allocate (format purge %s\n allocate %s\n - (or (and (org-taskjuggler-targeting-tj3-p) allocations) - allocate) + (or (and (org-taskjuggler-targeting-tj3-p) allocate) + allocations) allocate)) (and complete (format complete %s\n complete)) (and effort (format effort %s\n effort)) -- 1.7.1
[O] [PATCH 0/3] Small fixes to taskjuggler export
Hi all Here are some more small fixes to taskjuggler export Thanks Christian Egli (3): Replace recursive implementation with an iterative one Fix allocations handling for tj3 Fix a typo in the commentary. lisp/org-taskjuggler.el | 22 ++ 1 files changed, 10 insertions(+), 12 deletions(-)
[O] Re: [PATCH 0/5] Improvements to Taskjuggler export
Bastien b...@altern.org writes: I'm myself using TJ for some reports and I've had to hack things around when we had this compatibility problem. I almost forgot to ask: What where the problems you had to hack around? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: Bug: Column view fails to display ITEM row [7.5 (release_7.5.87.gb227)]
Julien Danjou jul...@danjou.info writes: On Fri, Mar 18 2011, Christian Egli wrote: I ran a git bisect to find the guilty commit and it turns out that there is a problem with commit c84d77a7a035a142bf114c5e6758c32a20f3fd68. I just pushed a fix. Thanks for the report and the bisect! Thanks for the fix. Works like a charm. -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: [PATCH 1/5] Add some minimal infrastructure to handle export to both tj2 and tj3
Bastien b...@altern.org writes: Christian Egli christian.e...@alumni.ethz.ch writes: +(defun org-taskjuggler-targeting-tj3-p () + Return true if we are targeting TaskJuggler III. + ( org-export-taskjuggler-target-version 3.0)) I'm dubious on this one. Shouldn't it be #+begin_src emacs-lisp (defun org-taskjuggler-targeting-tj3-p () Return true if we are targeting TaskJuggler III. ( org-export-taskjuggler-target-version 3.0)) #+end ? Basically org-export-taskjuggler-target-version can be 2.4 or 3.0. So org-taskjuggler-targeting-tj3-p should return true if org-export-taskjuggler-target-version is 3.0 or higher and false otherwise. So, let's see what the *scratch* buffer has to say about this #+begin_src emacs-lisp (setq org-export-taskjuggler-target-version 2.4) 2.4 (defun org-taskjuggler-targeting-tj3-p () Return true if we are targeting TaskJuggler III. ( org-export-taskjuggler-target-version 3.0)) org-taskjuggler-targeting-tj3-p (org-taskjuggler-targeting-tj3-p) nil (setq org-export-taskjuggler-target-version 3.0) 3.0 (org-taskjuggler-targeting-tj3-p) nil (setq org-export-taskjuggler-target-version 3.1) 3.1 (org-taskjuggler-targeting-tj3-p) t #+end Ah, you're right. There is a problem :-\. The correct version should be #+begin_src emacs-lisp (defun org-taskjuggler-targeting-tj3-p () Return true if we are targeting TaskJuggler III. (= org-export-taskjuggler-target-version 3.0)) #+end Let's test this in *scratch* #+begin_src emacs-lisp (setq org-export-taskjuggler-target-version 2.4) 2.4 (defun org-taskjuggler-targeting-tj3-p () Return true if we are targeting TaskJuggler III. (= org-export-taskjuggler-target-version 3.0)) org-taskjuggler-targeting-tj3-p (org-taskjuggler-targeting-tj3-p) nil (setq org-export-taskjuggler-target-version 3.0) 3.0 (org-taskjuggler-targeting-tj3-p) t (setq org-export-taskjuggler-target-version 3.1) 3.1 (org-taskjuggler-targeting-tj3-p) t #+end How do we proceed? Do I resubmit the patch? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: [PATCH 0/5] Improvements to Taskjuggler export
Hi Bastien Bastien b...@altern.org writes: Ps: I had trouble applying your patches: they came in one order on the list, and on a different one on patchwork. Applying them from patchwork didn't always work, so I had to do a few things manually. Not a problem. Is there anything I can do about this? I just commited the changes locally and used git format-patch and git send-email. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: [PATCH 0/5] Improvements to Taskjuggler export
Hi Marc Marc-Oliver Ihm marc-oliver@online.de writes: Does your fork incorporate Anthonys enhancements (e.g. the :TJ:-Drawer) ? It contains some of his enhancements but not all. He has two versions of the code. One for tj2 and one for tj3. I would like to have one version for both. The code as it stands right now can export a project for both tj2 and tj3. However the way the defaults are set for the reports now (in defcustom variables) it will not work for tj3. You'll have to redefine the variables via M-x customize. If you look at his code you'll see that he has some other enhancements. There is support for project specific definitions, for global definitions (such as shifts, etc) and for flags. One really nice idea is that he added support for Drawers that can contain taskjuggler specific code that is tied to a specific node. However I would like to implement this as a src block, which would probably also cover global definitions and file specific reports. My initial idea was to use something like #+BEGIN_TASKJUGGLER and #+END_TASKJUGGLER. But nowadays it seems more kosher to use something along the line of #+BEGIN_SRC taskjuggler. I don't know what that would entail though. I might have to write a Babel backend for Taskjuggler. I basically just want to use these code blocks in my exporter. Is it available at your github (https://github.com/egli/org-mode) ? No, this is stale (I should probably remove it). My most up to date code should be in the orgmode repo. Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] Re: [PATCH 0/5] Improvements to Taskjuggler export
Bastien b...@altern.org writes: Did Anthony advertized his enhancements on this list? AFAIK he did announce them here, but that was a long time ago, probably more than six months. Thanks -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
