[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Babel: the disappearing hline

From: Jarmo Hurri
Subject: Re: [O] Babel: the disappearing hline
Date: Fri, 15 Nov 2013 08:50:11 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux)

Greetings Eric.

Eric Schulte <address@hidden> writes:

> I understand that this particular use case is confusing, however there
> are competing use cases and the case described here is not the most
> common.
> Take for example the following.
>     #+name: data
>     | header |
>     |--------|
>     | one    |
>     | two    |
>     |--------|
>     | three  |
>     #+BEGIN_SRC sh :var in=data
>       echo "$in"
>     #+END_SRC
>     #+RESULTS:
>     | header |
>     | one    |
>     | two    |
>     | three  |
> In fact, hlines are *not* preserved by default with regular code blocks.
> And in practice only emacs-lisp code blocks tend to create hlines
> themselves.  

I do realize this, and you are the expert, but the suggestion was that
hlines would not be stripped from the _output_ of a #+CALL, if they are
generated by the call, just like hlines are not stripped from the
_output_ of an evaluated block, or the _output_ of a post(), as
demonstrated in my earlier examples.

In your example hlines are stripped directly from the _input_.  The
manual also leads one to think that stripping is applied to the
_input_. Maybe this is too simplistic for expert taste, but that is what
it looks like to a casual user.

To put things in context while discussing this minor detail: thank you
for this very impressive system!

All the best,


reply via email to

[Prev in Thread] Current Thread [Next in Thread]