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 21:01:02 +0200 [thread overview]
Message-ID: <4E08D36E.9030302@christianmoe.com> (raw)
In-Reply-To: <87y60n5fvx.fsf@counsyl.com>
Hi,
Yes, these all checked out (assuming you meant the second one /should/
be exported -- as quoted code -- but not evaluated).
This is a nice addition, and rather cleaner and more intuitive than
the workarounds I've been playing with. (Faking an inline call to
block A with an inline src block B that takes a variable from calling
A in the header args, and shortening it with a macro that expands to B...)
Yours,
Christian
On 6/27/11 7:43 PM, Eric Schulte wrote:
> 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---
next prev parent reply other threads:[~2011-06-27 18:59 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
2011-06-27 17:43 ` Eric Schulte
2011-06-27 19:01 ` Christian Moe [this message]
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=4E08D36E.9030302@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).