[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] idempotency and inconsistency for org-babel-remove-inline-result
From: |
Daniele Pizzolli |
Subject: |
Re: [O] idempotency and inconsistency for org-babel-remove-inline-result |
Date: |
Sat, 31 Jan 2015 00:06:41 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
Hello Charles,
"Charles C. Berry" writes:
> On Fri, 30 Jan 2015, Daniele Pizzolli wrote:
>
>> Hello,
>>
>> I really like the new inline results. Thanks for this new cool feature.
>> I have only a few problems with it.
>>
>
> Thanks for your feedback.
Nice to hear.
>> Is there a way to evaluate a buffer an then remove inline results or
>> better, to get the very same buffer after:
[]
>> I see that the function docs says: Extraneous leading whitespace is
>> trimmed. Is this the intended result?
>
> It is intended to remove `extraneous' whitespace. But the way
> `extraneous' is operationalized leaves something to be desired if
> users wish to do as you have done. Maybe preserving whitespace (if any)
> after the result and deleting all that is before it might work.
>
> I'll take a look at changing the defn to deal with your ECM.
Thanks, see later.
>>
>> Also, is there anything that prevents to make
>> org-babel-remove-inline-result interactive as is
>> org-babel-remove-result?
>
> AFAICS, no.
Ok, patch attached.
>> Wwhy not have also
>> org-babel-remove-inline-result-one-or-many and
>> org-babel-remove-all-result-one-or-many to remove all the babel result
>> with one function call?
>
> Easy enough, but is this really needed? What about call block/line
> results?
This is useful for me because I want to easily discard the results to
have the commit with only the changes in the source. I hope others find
this a reasonable facility. It is like a 'make clean' for your org
files.
Patch attached. I am not sure about the default of discarding keyword
Deleting the result line can cause some disorder, but it is the default
in org-babel-remove-result. Also the naming can be confusing.
>> I do no not know lisp a lot, but I can try to submit a patch if you
>> agree that will be useful.
>>
>
> The main issue (IMO) is figuring out what whitespace to delete around
> a `{{{results(...)}}}' macro. I can get to this in a day or so, but
> feel free to send a patch.
This is above my lisp coding abilities, with too many org-related
function to get lost into org-babel-remove-inline-result... I can wait,
but if you have any pointer I will be happy to do some exploration.
Thanks again,
Daniele
0001-ob-core.el-add-interactive-to-org-babel-remove-inlin.patch
Description: Text Data
0002-ob-core.el-Add-org-babel-remove-result-all.patch
Description: Text Data