From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarmo Hurri Subject: Re: Babel: the disappearing hline Date: Fri, 15 Nov 2013 08:50:11 +0200 Message-ID: <8738myduqk.fsf@syk.fi> References: <877gcfhuq0.fsf@syk.fi> <8738n3t2ez.fsf@gmail.com> <87fvr3nfcm.fsf@syk.fi> <87wqkfrm3v.fsf@gmail.com> <87y54uhpw8.fsf@gmail.com> <87y54urgs4.fsf@syk.fi> <87ppq6hlye.fsf@gmail.com> <87r4amb0vc.fsf@syk.fi> <87ob5pmwkf.fsf@syk.fi> <87y54ssu1r.fsf@syk.fi> <8738n0b0ot.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47879) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VhDEf-0000K5-RW for emacs-orgmode@gnu.org; Fri, 15 Nov 2013 01:50:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VhDEV-0002FF-Ob for emacs-orgmode@gnu.org; Fri, 15 Nov 2013 01:50:33 -0500 Received: from plane.gmane.org ([80.91.229.3]:51804) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VhDEV-0002FA-Ia for emacs-orgmode@gnu.org; Fri, 15 Nov 2013 01:50:23 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VhDEU-00038f-FF for emacs-orgmode@gnu.org; Fri, 15 Nov 2013 07:50:22 +0100 Received: from host-137-163-18-130.edu.hel.fi ([137.163.18.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Nov 2013 07:50:22 +0100 Received: from jarmo.hurri by host-137-163-18-130.edu.hel.fi with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 15 Nov 2013 07:50:22 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Greetings Eric. Eric Schulte 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