On 06.04.20 18:13, Nicolas Goaziou wrote:
Heiko Schmidt 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 introducin
On 06.04.20 12:13, Nicolas Goaziou wrote:
Effort property accepts a specific, and well defined type of value:
a duration. Such values cannot be negative, as explained in the error
message.
You may, however, use a different property for your use-case, and apply
column view on it.
Regards,
This
Hi everybody.
When planning projects I estimate the amount of time for tasks by
filling the property EFFORT with an amount of time.
#+begin_src org
,*** Projekt
:PROPERTIES:
:COLUMNS: %30ITEM %8EFFORT{:}
:END:
, effort planned/estimated
On 18.03.20 16:50, Eric S Fraga wrote:
Indeed hackish. But it does beg the question: why does ob-calc pop the
stack? I cannot see any use case given that the stack is essentially
infinite and can be safely ignored (in most if not all cases).
Could the solution be to simply remove the
Hi Marco,
On 18.03.20 15:47, Marco Wahl wrote:
Okay. I take here the "any advice is appreciated" part.
AFAICS at the org babel calc evaluation the last value of the calc stack
gets dropped.
So your workaround is okay, I think. You can just write any dummy
element at the bottom of each block
rote:
On Sunday, 15 Mar 2020 at 11:46, Heiko Schmidt wrote:
- I want to use ob-calc to do some "literate calculation" with the
purpose to document what I thought at the time I wrote it.
I have never managed to get ob-calc to do what I want either so I cannot
help you directly wi
Hi there,
the following org snippet is describing my issue.
Thanks in advance,
Heiko
* TODO post problem report about ob-calc duplicate stack-element issue
:LOGBOOK:
- State "TODO" from [2020-03-15 Sun 09:19]
:END:
- I want to use ob-calc to do some "literate
