[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [O] [babel] using #+call for inline results
From: |
Eric Schulte |
Subject: |
Re: [O] [babel] using #+call for inline results |
Date: |
Mon, 27 Jun 2011 10:43:46 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
Christian Moe <address@hidden> writes:
> Fixed, thanks. I should have guessed that might be it.
>
> Evaluating inline calls now works, but there are some ramifications
> for output and export that I hadn't thought about when I seconded the
> request.
>
>
> * Export
>
> The call itself should not be exported, but I'm seeing:
>
> : <p>
> : Here is a call<sub>square</sub>(it=4) <code>16</code> stuck in the
> middle of some prose.
> : </p>
>
>
> * Output
>
> To get rid of the literal equals-signs, I try:
>
> : Here is a call_square(it=4)[:results raw] stuck in the middle of
> some prose.
>
> I expect to get the result inline, but instead it comes as a normal
> call results block (aligned with the call):
>
> : #+results: square(it=4)
> : 16
>
Hi Christian,
Thanks for sharing these issues, it appears I messed some functionality
up with some of my recent changes. I believe that I have fixed these
issues. The following examples should now all export as described.
--8<---------------cut here---------------start------------->8---
The following exports as a normal call line
#+call: double(it=1)
Now here is an inline call call_double(it=1) stuck in the middle of
some prose.
This one should not be exported =call_double(it=2)= because it is
quoted.
Finally this next one should export, even though it starts a line
call_double(it=3) because sometimes inline blocks fold with a
paragraph.
And, a call with raw results call_double(4)[:results raw] should not
have quoted results.
--8<---------------cut here---------------end--------------->8---
Please let me know if you experience any more problems, and thanks for
helping to get this sorted before the impending release!
Cheers -- Eric
>
>
> Yours,
> Christian
>
> On 6/27/11 2:14 AM, Eric Schulte wrote:
>>>
>>> But I seem to have a problem (running your example):
>>>
>>> Debugger entered--Lisp error: (invalid-function (nonempty (a b) (let
>>> ((it (match-string a))) (if (= (length it) 0) (match-string b) it))))
>>> (nonempty (a b) (let (...) (if ... ... it)))()
>>> org-babel-lob-get-info()
>>> org-babel-lob-execute-maybe()
>>> org-babel-execute-maybe()
>>> org-babel-execute-safely-maybe()
>>> run-hook-with-args-until-success(org-babel-execute-safely-maybe)
>>> org-ctrl-c-ctrl-c(nil)
>>> call-interactively(org-ctrl-c-ctrl-c nil nil)
>>>
>>
>> I believe this is due to my forgetting to require 'cl at compile time.
>> I've just pushed up a fix, please let me know if the problem persists.
>>
>> Thanks -- Eric
>>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
- Re: [O] [babel] using #+call for inline results, (continued)
- Re: [O] [babel] using #+call for inline results, Christian Moe, 2011/06/23
- Re: [O] [babel] using #+call for inline results, Eric Schulte, 2011/06/24
- Re: [O] [babel] using #+call for inline results, Eric S Fraga, 2011/06/25
- Re: [O] [babel] using #+call for inline results, Christian Moe, 2011/06/26
- Re: [O] [babel] using #+call for inline results, Eric Schulte, 2011/06/26
- Re: [O] [babel] using #+call for inline results, Christian Moe, 2011/06/27
- Re: [O] [babel] using #+call for inline results,
Eric Schulte <=
- Re: [O] [babel] using #+call for inline results, Christian Moe, 2011/06/27
- Re: [O] [babel] using #+call for inline results, Sebastien Vauban, 2011/06/28
- Re: [O] [babel] using #+call for inline results, Eric Schulte, 2011/06/28
- Re: [O] [babel] using #+call for inline results, Sebastien Vauban, 2011/06/29
- Re: [O] [babel] using #+call for inline results, Eric Schulte, 2011/06/29
- Re: [O] [babel] using #+call for inline results, Eric Schulte, 2011/06/29
- Re: [O] [babel] using #+call for inline results, Eric S Fraga, 2011/06/27
- Re: [O] [babel] using #+call for inline results, Eric Schulte, 2011/06/27
- Re: [O] [babel] using #+call for inline results, Eric S Fraga, 2011/06/29
- Re: [O] [babel] using #+call for inline results, Eric Schulte, 2011/06/29