| commit | 1de29a0059e300da5e0245a209f66275c4eb3ec8 | |
| author | Niels Giesen <niels.giesen@gmail.com> | |
| Fri, 10 Jun 2011 09:32:42 +0000 (10 11:32 +0200) | ||
| committer | Carsten Dominik <carsten.dominik@gmail.com> | |
| Fri, 10 Jun 2011 11:56:02 +0000 (10 13:56 +0200) | ||
| tree | 419c25681a82bcec19c52d8959c3c126338f18d4 | treesnapshot (tar.gz zip) |
| parent | 374b70a3832366ccc4fadafd916394ac9e9affd4 | commitdiff |
Fix reported file time for clock reports
Fix the format specification for clock tables.
Niels writes:
Bernt was right in that there were more arguments to format than the
format string specified. I guess I must not have noticed that there was
a call to format (all the other times properties columns are 'maybe
inserted' go directly to `insert-before-markers'), and I must have
forgotten to test the multifile case (I never used multifile clock
reports myself).
However, to keep the layout of the table consistent the *File time*
cells should be in the Headline column. Attached patch fixes this by
putting the (empty) properties cells *before* the *File time* cell.
Fix the format specification for clock tables.
Niels writes:
Bernt was right in that there were more arguments to format than the
format string specified. I guess I must not have noticed that there was
a call to format (all the other times properties columns are 'maybe
inserted' go directly to `insert-before-markers'), and I must have
forgotten to test the multifile case (I never used multifile clock
reports myself).
However, to keep the layout of the table consistent the *File time*
cells should be in the Headline column. Attached patch fixes this by
putting the (empty) properties cells *before* the *File time* cell.
| lisp/org-clock.el | diffblobblamehistory |