From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jarmo Hurri Subject: Re: Babel: the disappearing hline Date: Tue, 12 Nov 2013 08:16:55 +0200 Message-ID: <87r4amb0vc.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34497) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vg7Hn-0007aj-Kf for emacs-orgmode@gnu.org; Tue, 12 Nov 2013 01:17:22 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vg7Hg-0003Qq-A4 for emacs-orgmode@gnu.org; Tue, 12 Nov 2013 01:17:15 -0500 Received: from plane.gmane.org ([80.91.229.3]:44547) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vg7Hg-0003Qm-3Q for emacs-orgmode@gnu.org; Tue, 12 Nov 2013 01:17:08 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Vg7He-0005u2-Cp for emacs-orgmode@gnu.org; Tue, 12 Nov 2013 07:17:06 +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 ; Tue, 12 Nov 2013 07:17:06 +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 ; Tue, 12 Nov 2013 07:17:06 +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 Eric Schulte writes: Greetings Eric. > There are two paces to specify header arguments in a call line, the > arguments in the [] are applied to the input-table function, *not* to > the call line, so they change the inputs. The trailing header > arguments are applied to the call line. So there is an implicit post-processing function that takes the result of the called block as input, and hline pruning is applied in this function? I put on the table a suggestion that the default behaviour of #+CALL w.r.t. the handling of hlines is changed from removing hlines in output to not removing them. I am suggesting this partly because I don't understand why the default behaviour is as it is now, and secondly because the current behavious differs from the way hlines are handled in other block evaluations: # --------------------------------------------------------------------- * hline pruning in output # case 1: hlines are retained by default when a source code block is # defined and evaluated #+NAME: func #+BEGIN_SRC emacs-lisp (list '(a) '(b) 'hline '(c)) #+END_SRC #+RESULTS: func | a | | b | |---| | c | # case 2: hlines are retained by default when source code is called # by post #+BEGIN_SRC emacs-lisp :post func() #+END_SRC #+RESULTS: | a | | b | |---| | c | # case 3: but hlines are removed by default when source code is # called by #+CALL #+CALL: func() #+RESULTS: | a | | b | | c | # --------------------------------------------------------------------- All the best, Jarmo