From: Jarmo Hurri <jarmo.hurri@syk.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Babel: the disappearing hline
Date: Fri, 15 Nov 2013 08:50:11 +0200 [thread overview]
Message-ID: <8738myduqk.fsf@syk.fi> (raw)
In-Reply-To: 8738n0b0ot.fsf@gmail.com
Greetings Eric.
Eric Schulte <schulte.eric@gmail.com> 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,
Jarmo
prev parent reply other threads:[~2013-11-15 6:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 14:35 Babel: the disappearing hline Jarmo Hurri
2013-11-11 14:53 ` Thorsten Jolitz
2013-11-11 15:11 ` Jarmo Hurri
2013-11-11 15:31 ` Thorsten Jolitz
2013-11-11 16:19 ` Eric Schulte
2013-11-11 17:26 ` Jarmo Hurri
2013-11-11 17:44 ` Eric Schulte
2013-11-12 6:16 ` Jarmo Hurri
2013-11-12 15:45 ` Rick Frankel
2013-11-12 16:09 ` Jarmo Hurri
2013-11-12 19:22 ` Rick Frankel
2013-11-13 6:19 ` Jarmo Hurri
2013-11-13 14:17 ` Eric Schulte
2013-11-13 18:52 ` Rick Frankel
2013-11-13 23:27 ` Eric Schulte
2013-11-15 6:50 ` Jarmo Hurri [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
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=8738myduqk.fsf@syk.fi \
--to=jarmo.hurri@syk.fi \
--cc=emacs-orgmode@gnu.org \
/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).