I see that the exact same "bug" was reported at the start of 2016 by
David Bremner. Personally, I feel that fewer people would be confused
by this if the default value was set to "untilnow".
I also realised that the full list of values that I can use for
org-clock-display-default-range is describ
Paul Stansell writes:
> Thanks for that tip, I was totally unaware of that option (it doesn't seem
> to be mentioned in the user documentation, eg, it's not mentioned on
> https://orgmode.org/manual/Clocking-commands.html).
I added a reference to that variable in Org 8.2 manual. Thank you for
th
default should perhaps be changed?
On 1/6/18, Paul Stansell wrote:
> I do wonder why the default range should be set at the current year and not
> simply over the full range of clocked times in a heading.
Hello Nicolas,
Thanks for that tip, I was totally unaware of that option (it doesn't seem
to be mentioned in the user documentation, eg, it's not mentioned on
https://orgmode.org/manual/Clocking-commands.html).
I do wonder why the default range should be set at the current year and not
simply ove
Hello,
Paul Stansell writes:
> The sum of the clock time seems to be summing just times in the current
> year. In the example below typing C-c C-x C-d in the "Example" section
> displays "1:00" instead of "2:00" on the heading line. The clocktable
> computes the sum correctly as "2:00".
See `
Hello,
The sum of the clock time seems to be summing just times in the current
year. In the example below typing C-c C-x C-d in the "Example" section
displays "1:00" instead of "2:00" on the heading line. The clocktable
computes the sum correctly as "2:00".
Thanks
# Start Example -
