emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christian Moe <mail@christianmoe.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] using #+call for inline results
Date: Mon, 27 Jun 2011 08:16:33 +0200	[thread overview]
Message-ID: <4E082041.6080709@christianmoe.com> (raw)
In-Reply-To: <87vcvsruzs.fsf@gmail.com>

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


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
>

  reply	other threads:[~2011-06-27  6:14 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 11:07 [babel] using #+call for inline results Eric S Fraga
2011-06-22 16:23 ` Eric Schulte
2011-06-22 18:22   ` Eric S Fraga
2011-06-23  5:32     ` Eric Schulte
2011-06-23  8:10       ` Eric S Fraga
2011-06-23 13:49         ` Nicolas Goaziou
2011-06-23 15:39           ` chris.m.malone
2011-06-23 17:30           ` Eric S Fraga
2011-06-23 19:55             ` Nicolas Goaziou
2011-06-24  8:11               ` Eric S Fraga
2011-06-23  9:25       ` Christian Moe
2011-06-24 22:36         ` Eric Schulte
2011-06-25 19:33           ` Eric S Fraga
2011-06-26 11:56           ` Christian Moe
2011-06-27  0:14             ` Eric Schulte
2011-06-27  6:16               ` Christian Moe [this message]
2011-06-27 17:43                 ` Eric Schulte
2011-06-27 19:01                   ` Christian Moe
2011-06-28  8:04                   ` Sebastien Vauban
2011-06-28 20:31                     ` Eric Schulte
2011-06-29  7:40                       ` Sebastien Vauban
2011-06-29 17:12                         ` Eric Schulte
2011-06-29 17:25                           ` Eric Schulte
2011-06-27 17:09           ` Eric S Fraga
2011-06-27 18:45             ` Eric Schulte
2011-06-29 16:38               ` Eric S Fraga
2011-06-29 17:59                 ` Eric Schulte
2011-06-22 17:53 ` Juan Pechiar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E082041.6080709@christianmoe.com \
    --to=mail@christianmoe.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).