Jack Kamm writes:
> Ihor Radchenko writes:
>
>> Your patch appear to only add more confusion, IMHO.
>>
>> I feel that the description about :results file is confusing from the
>> very beginning:
>
> Well, I guess ":results file" has confusing behavior. So it's
> difficult to write accurate, comp
Ihor Radchenko writes:
We should probably reserve the workaround to Emacs 28 and older and
eventually remove it when Org drops Emacs 28 support.
Ok.
I tested using Emacs 28 and 27 and your patch is passing all the tests.
Thanks.
--
Sébastien Miquel
From 6ea37a3041fb3266e94af0bfce29aa76f6c
Ihor Radchenko writes:
> Ypo writes:
>
>> This is a suggestion: Could Speed commands be applied to lists?
>
> It is just a question of adding an extra hook to
> `org-speed-command-hook'. Let's see what people think about it.
No interest.
So, you can do it yourself in your config instead.
Closed
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 org-columns--su
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
#+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 pr
