and...@fedeli.eu writes:
>IR > May you share your changes?
>Sure!
>Here they are: In these slices I take the upper part of the fork (where in
> case, assuming a small-big usage convention ;)) as that is the value that
> surely testify the effort estimation overrun. Being so, at the
IR > May you share your changes?
Sure!
Here they are: In these slices I take the upper part of the fork (where in
case, assuming a small-big usage convention ;)) as that is the value that
surely testify the effort estimation overrun. Being so, at the time of this
writing I just
and...@fedeli.eu writes:
>Howdy!
>I'm back to a previous element partially discussed as I found other org
> places where the duration had to be adapted to be able to deal with ranges:
> org-clock-get-clock-string and
>org-clock-notify-once-if-expired, both in og-clock.el; both get
Howdy!
I'm back to a previous element partially discussed as I found other org
places where the duration had to be adapted to be able to deal with ranges:
org-clock-get-clock-string and
org-clock-notify-once-if-expired, both in og-clock.el; both get into action
if you have a task you
and...@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
Howdy!
Da "Ihor Radchenko" yanta...@posteo.net
A and...@fedeli.eu
Cc emacs-orgmode@gnu.org
Data Fri, 14 Jul 2023 09:02:04 +
Oggetto Re: [BUG] Error in data input and output format for
org-columns--summary-estimate
[ Adding Org ML back to CC. Please use "reply all" to
[ Adding Org ML back to CC. Please use "reply all" to reply on the
mailing list ]
"and...@fedeli.eu" writes:
> I do apologize, I noticed only now the patch content: the output
> format of duration-from-minutes Is controlled by the
> org-duration-format variable, so if the user wants
and...@fedeli.eu writes:
>#+PROPERTY: Effort_ALL 0 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00
>
>#+COLUMNS: %30ITEM(Task) %30Effort(Estimated Effort){est+} %CLOCKSUM
>...
>Originally produces
>image.png
>That shows that days and months are wrongly counted the same
Thanks!
#+PROPERTY: Effort_ALL 0 0:10 0:30 1:00 2:00 3:00 4:00 5:00 6:00 7:00
#+COLUMNS: %30ITEM(Task) %30Effort(Estimated Effort){est+} %CLOCKSUM
* efforts
** task 1
:PROPERTIES:
:Effort: 3d
:END:
** task 2
:PROPERTIES:
:Effort: 3m-4m
:END:
Originally
and...@fedeli.eu writes:
>The matter is related to the fact that org-columns--summary-estimate, from
> org-colview.el, uses function string-to-number to take value on ranges;
> acting this way
>
>the unit is removed making impossible to distinguish between 1y and 1min .
> Similarly, on
Howdy!
This has been tested to happen with org 9.5.5, a few of the
following, and on the HEAD version on git (9.6.7+); it's a source
matter, afflicting org independently of the running platform (GNU/Linux,
Windows, etc.)
The matter is related to the fact that
11 matches
Mail list logo
