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: Thu, 23 Jun 2011 11:25:10 +0200	[thread overview]
Message-ID: <4E030676.3070504@christianmoe.com> (raw)
In-Reply-To: <87sjr1i040.fsf@gmail.com>

+1 for inline calls. No hurry, though.

Yours,
Christian

On 6/23/11 7:32 AM, Eric Schulte wrote:
> Eric S Fraga<e.fraga@ucl.ac.uk>  writes:
>
>> Eric Schulte<schulte.eric@gmail.com>  writes:
>>
>>> Hi Eric,
>>
>> Hi Eric!  ;-)
>>
>>> So the problem is that the results are inserted as a separate block,
>>> when you want them to be inserted inline?  If so perhaps using an
>>> "inline" block http://orgmode.org/manual/Structure-of-code-blocks.html
>>> would result in the desired behavior.
>>>
>>> Please let me know if I've misunderstood the question.
>>
>> Yes and no.  I *do* want the effect that is achieved by using an inline
>> block but I do *not* want to write the whole block inline
>
> I find the following pattern
>
>    #+source: big-block
>    #+begin_src emacs-lisp :exports none
>      "something complex"
>    #+end_src
>
>    Here is some text with src_emacs-lisp[:var it=big-block]{it} in the
>    middle.
>
> to be helpful in these situations.
>
>> as that can be difficult to do or, at the very best, hard to read even
>> if possible... I would like to invoke/evaluate, inline, a particular
>> source code block with a specific value of an argument.
>>
>>  From the documentation, I don't see how to "call" a src block inline.
>> That's why I thought of using =#+call=.  Am I missing something?
>>
>
> nope, there is no way to issue an in-line call, although maybe this
> wouldn't be the worst idea if only for the added brevity over an inline
> code block.
>
> I'll put it on my long-term low-priority stack. :)
>
> Cheers -- Eric
>
>>
>> Thanks,
>> eric
>

  parent reply	other threads:[~2011-06-23  9:24 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 [this message]
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
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=4E030676.3070504@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).