[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [BUG] Error in data input and output format for org-columns--summary
From: |
Ihor Radchenko |
Subject: |
Re: [BUG] Error in data input and output format for org-columns--summary-estimate |
Date: |
Tue, 18 Jul 2023 09:10:33 +0000 |
andrea@fedeli.eu writes:
>> About possibile abuses, org documentation, to date, clearly tells
>> org estimate utilizes times.
>
>> May you please elaborate?
> AF: Sure! Clause 8.5 of current
> (2023.Jul.14) org documentation,
> https://orgmode.org/manual/Effort-Estimates.html, refers to effort
> estimates giving examples that are all appearing to fall in time
> domain.
I see what you mean.
However, est+ column summary does not have to be applied to EFFORT
columns.
One can, for example, use %SCORE{est+} column specification to summarize
values stored in SCORE property. Org has no right to demand SCORE to be
in time units and only time units.
> > Similarly, I'd not spend too much code to check the format; i
> > understand the intent to preserve backward compatibility, bit if
> > that format adaptation mistake slipped forward to these days I
> > doubt that nice feature was used much so far...
>
> Yes, but it is easy to have a fallback, so why not.
> Because this way you persist in allowing a mistaken usage of that
> function. A number is a number but a duration is NOT just a number,
> and having something like (just for example) 10kg-0.5ton be taken
> as 10-0.5 is in my opinion NOT helpful to any user.
We may provide a linter (for M-x org-lint) that will ensure EFFORT
estimates to be in understandable format.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>