Re: negative values for EFFORT result in error when switching to column view

[Nicolas Goaziou]

Heiko Schmidt <address@hidden> writes:

> This is exactly the reason why I'd love to have negative values for
> the durations. It would open the possibility of doing something like
> "accounting" of time.

I think you can do accounting of time without introducing negative
duration. Basic accounting implies having two categories. You expect
them to be "positive" and "negative", but it could also be "positive in
property A" and "positive in property B".

> I'm working with self defined duration units and it would be of great
> value to be able to calculate the balance for planned and done work
> time. I don't use clocking.
>
> What'd be wrong about having -0:30 h, -30 min, -2.5 h, -3 d or -3 m?
> It'd be an addition no change so there would hoefully be no
> incompatibilities.
>
> Maybe even 3m -3d be or -3m 3d could be of use.

No incompatibility doesn't mean no cost. It adds code complexity. You
also have to maintain the feature later on, make sure it doesn't break
future code, etc.

Moreover, I'm not convinced about the general need for such a feature.
Of course, it is possible that I may be missing the point. Org folks may
want to chime in and correct me if I do.

> As I see there is org-duration.el - Have the changes to be made only
> there?

I think so. But I suggest to check if you cannot do otherwise (again,
I'm sure you can).