Re: [Orgmode] Re: [babel] ledger tutorial on Worg

[Eric Schulte]

Hi Seb,

Sébastien Vauban <address@hidden> writes:

> Hi Eric,
>
> "Eric Schulte" wrote:
>> Sébastien Vauban <address@hidden> writes:
>>> "Eric Schulte" wrote:
>>>> Sébastien Vauban <address@hidden> writes:
[...]
>>>>> 2. When the evaluation produces no output, but had well produced output
>>>>>    before, shouldn't Babel have to delete the previously written results 
>>>>> in
>>>>>    the Org buffer?
>>>>
>>>> This is a good point. Currently Babel just quits if it receives a nil
>>>> result, but I think you're right that we should replace existing results
>>>> when a nil result has been returned. I'll add this as PROPOSED to the babel
>>>> task list.
>>>
>>> I consider this kind of mandatory, for the sake of coherency, and to really
>>> make use of Org-babel every time I want to run some shell commands (and 
>>> change
>>> them, eventually getting no results then).
>>>
>>
>> I've just pushed up a change that implements this behavior.
>
> I've just git pulled, and tested your change.
>
> From my point of view, it does not work yet. Take this example:
>

[...]

>
> With `:cmdline reg unknown', it produced the line with -21.91 EUR. Correct.
>
> Now, if I write `:cmdline "reg" unknown', I expect no output from Ledger, and
> thus the results block to be removed. That's not the case.
>

If ledger throws an exception then the result probably will not be
replaced, however if ledger does return an empty result, then the
existing result will be removed.  If you execute the following code
block

#+begin_src emacs-lisp
  "test"
#+end_src

and then change the body to "" is the previous result removed?

>
> Other peculiarity, if I write `:cmdline reeg unknown', I get an
> exception:
>

Ah, thanks for pointing this out, it seems I introduced an error with my
previous change.  I've just pushed up a fix for this issue.

Thanks -- Eric