From: Ihor Radchenko <yantar92@posteo.net>
To: andrea@fedeli.eu
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Error in data input and output format for org-columns--summary-estimate
Date: Tue, 18 Jul 2023 09:10:33 +0000 [thread overview]
Message-ID: <871qh5wpo6.fsf@localhost> (raw)
In-Reply-To: <RXSB26$31CC50B784CF89D0AFACC55F32997B41@fedeli.eu>
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>
next prev parent reply other threads:[~2023-07-18 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-09 12:46 [BUG] Error in data input and output format for org-columns--summary-estimate andrea
2023-07-09 14:17 ` Ihor Radchenko
2023-07-09 14:33 ` andrea
2023-07-10 8:57 ` Ihor Radchenko
[not found] ` <RXR2XJ$F3602788F3665C159BAF986799B1995C@fedeli.eu>
2023-07-14 9:02 ` Ihor Radchenko
2023-07-14 11:39 ` andrea
2023-07-18 9:10 ` Ihor Radchenko [this message]
2023-08-15 15:53 ` andrea
2023-08-16 10:15 ` Ihor Radchenko
2023-08-18 6:20 ` andrea
2023-08-18 9:29 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871qh5wpo6.fsf@localhost \
--to=yantar92@posteo.net \
--cc=andrea@fedeli.eu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).