From: Marc-Oliver Ihm <marc-oliver.ihm@online.de>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: Andreas Leha <andreas.leha@med.uni-goettingen.de>, emacs-orgmode@gnu.org
Subject: Re: [babel] #+call-line removes hlines and headings ?
Date: Tue, 31 Jan 2012 19:45:25 +0100 [thread overview]
Message-ID: <4F2836C5.7060209@online.de> (raw)
In-Reply-To: <87zkd5yxv7.fsf@gmx.com>
Hi Eric,
thanx ! That explains very clearly what I have seen, when trying to debug this phaenomenon.
So this behaviour is by design and I can work around :-)
kind regards, Marc
Am 30.01.2012 17:10, schrieb Eric Schulte:
> Marc-Oliver Ihm<marc-oliver.ihm@online.de> writes:
>
>> Am 29.01.2012 11:42, schrieb Andreas Leha:
>>> :colnames yes
>> Hi Andreas,
>>
>> Thanx, that is definitely a solution !
>>
>> And I agree with you, that its a bit puzzling, that both cases behave differently;
>> the #+call-line should just have the same result as the #+begin_src-line, to which after all
>> it just refers. Beeing able to change the behaviour of the #+call-line
>> with header arguments is
>> of course a good thing, but it should not be necessary here in the first place.
>>
>> However, this would require a patch to the babel-code, which I am
>> currently not able to produce, because I already
>> got lost in debugging this problem :-) And of course I am not sure
>> what would be the side effects of changing this
>> behaviour ...
>>
>> So, thanx again for pointing out this very easy workaround !
>>
>>
>> with kind regards, Marc-Oliver Ihm
>>
>
> To explain the cause (if not rationale) for the current behavior; when
> executing a call line, an ephemeral code block is created at the point
> of the call line. The result of the called function is passed into this
> ephemeral block, and the output of the block is inserted into the
> buffer.
>
> This is why call lines have *two* possible sets of header arguments, one
> to pass to the original called code block, and one for local effect in
> the ephemeral block.
>
> The reason the colnames header argument is required for the call line
> and not the code block, is because hlines are only stripped when data
> passes *into* a code block as a variable. In this case the 'hlines are
> stripped when the table passes into the ephemeral code blocks.
>
> Hope the above is more illuminating that confusing,
>
prev parent reply other threads:[~2012-01-31 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 8:08 [babel] #+call-line removes hlines and headings ? Marc-Oliver Ihm
2012-01-29 10:42 ` Andreas Leha
2012-01-29 14:21 ` Marc-Oliver Ihm
2012-01-30 16:10 ` Eric Schulte
2012-01-31 18:45 ` Marc-Oliver Ihm [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F2836C5.7060209@online.de \
--to=marc-oliver.ihm@online.de \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.