emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Bug: Inconsistent effort handling in clock totals in maint [9.1.


From: Nicolas Goaziou
Subject: Re: [O] Bug: Inconsistent effort handling in clock totals in maint [9.1.13 (release_9.1.13 @ /home/bernt/git/org-mode/lisp/)]
Date: Mon, 14 May 2018 14:46:25 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux)

Hello,

Bernt Hansen <address@hidden> writes:

> I am fine with plain numbers being interpretted as hours. I don't
> think we need a second interpretation for it (as minutes).

The second interpretation already exists. "org-colview.el" is the sole
place where plain numbers are treated as hours. Everywhere else, plain
numbers are minutes, including in "org-clock.el".

> I don't think changing a bare 15 effort to mean minutes instead of the
> hours is a good idea - in case existing users already have effort data
> with plain numbers -- their estimates will change drastically.

I'm not proposing to change anything. I'm just suggesting a new way to
let users decide what should mean "15" when summing properties in
Columns View mode.

The issue here is you don't want to change Columns View mode, but
everything else. Or, more accurately, you want to add another exception
in plain numbers handling when displaying the mode line. This means
changing how `org-duration-to-minutes' interprets plain numbers, hence
the "everything else" part.

> Ideally I think I just want the mode line total to behave the same as
> the existing column view behaviour as far as plain numbers are concerned
> if this is easy and not causing more problems than it fixes.

We shot ourselves in the foot when we decided that one part of Org
should consider plain numbers as minutes and the other part as hours.
This is clearly sub-optimal.

I see no easy way to fix it painlessly. If we change anything, the
easier route to go is having Column View mode consider plain numbers as
minutes, because it only affects ... Column View mode itself.

We can also change nothing. I have the feeling this issue will bubble up
from time to time, though.

WDYT?

> Otherwise I can live with it -- it's been this way for years I think --
> and I will just change my effort values to always include both HH:MM and
> avoid plain numbers.

That's the most reasonable solution, IMO. Note that you can also use
"3h" instead of the ambiguous "3".

Regards,

-- 
Nicolas Goaziou



reply via email to

[Prev in Thread] Current Thread [Next in Thread]