Bug or known issue: org-clock-display

Bug or known issue: org-clock-display

[Ben McGinnes]

[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]

Hi all,
	I've been using org-mode to perform the task of timesheets
with another GNU project and encountered something which has all the
hallmarks of a bug.  I'm just not sure if it's a known issue or
whether to write up a bug report for it.

I use org-clock-in and org-clock-out to track the hours worked and
then at the end of each month use org-clock-display to obtain the
total hours to bill for.

This was going fine all year until January 1st.  At this point I can
no longer see the totals and org-clock-display produces the following
error message:

    Total file time: 0:00 (0 hours and 0 minutes)

If I do a find and replace of 2018 to 2019, however, the correct
calculations occur as expected.  So it appears that org-clock-display
only works for the year you're in.

BTW, the test I performed on just December, the correct total time
message is:

    Total file time: 5d 22:39 (142 hours and 39 minutes)

A bit of a difference.  ;)

So, is this a known issue with possibly some arcane reason for why it
can't easily be fixed or is my next step to go lodge a formal bug
report?


Regards,
Ben


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: Bug or known issue: org-clock-display

[Marco Wahl]

[-- Attachment #1: Type: text/plain, Size: 607 bytes --]

Hi,

> no longer see the totals and org-clock-display produces the following
> error message:
>
>     Total file time: 0:00 (0 hours and 0 minutes)

This is the expected behavior of the org-clock-display function AFAICS.

See

    C-h f org-clock-display

and

    C-h v org-clock-display-default-range

The default value of org-clock-display-default-range is ‘thisyear’ which
means that the result of

    M-x org-clock-display

indeed depends on the current time.

Find also the meanings of prefix arguments for org-clock-display in
the documentation.


HTH,  Marco




[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

Re: Bug or known issue: org-clock-display

[Ben McGinnes]

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

On Mon, Jan 14, 2019 at 07:56:03PM +0100, Marco Wahl wrote:
> Hi,
> 
> > no longer see the totals and org-clock-display produces the following
> > error message:
> >
> >     Total file time: 0:00 (0 hours and 0 minutes)
> 
> This is the expected behavior of the org-clock-display function AFAICS.
> 
> See
> 
>     C-h f org-clock-display
> 
> and
> 
>     C-h v org-clock-display-default-range
> 
> The default value of org-clock-display-default-range is ‘thisyear’ which
> means that the result of
> 
>     M-x org-clock-display
> 
> indeed depends on the current time.
> 
> Find also the meanings of prefix arguments for org-clock-display in
> the documentation.

Ah, cheers, this does indeed make it much more clear and changing
org-clock-display-default-range from "thisyear" to "untilnow" has
resulted in exactly what I wanted (and originally expected).  Though I
can see why it might be preferable for a default setting to run
through to the end of the current year.


Regards,
Ben

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]