From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: accessing source block header arguments from exporters Date: Sat, 11 Apr 2015 06:57:18 -0400 Message-ID: References: <55282A05.8040203@roklein.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47097) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ygt6K-0001wv-M4 for emacs-orgmode@gnu.org; Sat, 11 Apr 2015 06:57:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ygt6H-0008MA-DZ for emacs-orgmode@gnu.org; Sat, 11 Apr 2015 06:57:24 -0400 Received: from mail-qk0-x22a.google.com ([2607:f8b0:400d:c09::22a]:35258) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ygt6H-0008LE-9A for emacs-orgmode@gnu.org; Sat, 11 Apr 2015 06:57:21 -0400 Received: by qkhg7 with SMTP id g7so74023493qkh.2 for ; Sat, 11 Apr 2015 03:57:20 -0700 (PDT) In-reply-to: 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: Charles Berry Cc: emacs-orgmode@gnu.org I agree with "Not exactly". In this post http://kitchingroup.cheme.cmu.edu/blog/2014/09/22/Showing-what-data-went-into-a-code-block-on-export/ I did something where I wanted to get information about the variables passed into a block and show that on export. You might get some inspiration from that. The result is at http://kitchingroup.cheme.cmu.edu/media/2014-09-22-Showing-what-data-went-into-a-code-block-on-export/custom-src-table-export-3.html Charles Berry writes: > Robert Klein roklein.de> writes: > >> >> Hi, >> >> is there a way, to read header arguments to source blocks in the >> exporters org--src-block funktions? > > Not directly. org-babel-exp-code has no provision for headers. > They get dropped. > >> >> E.g. is there a way to access :firstline in the example below? >> > > Not exactly, but ... > > If you precede the code block with > > #+attr_firstline: 23 > > then with point in the src block > > (org-element-property :attr_firstline (org-element-context)) > > will return ("23"). And org-*-src-block functions can use it. > > If you really want to use the :firstline idiom, you can add a hook in > `org-export-before-processing-hook' to find :firstline headers and > insert #+attr_firstline lines in the buffer copy that the exporter is using. > >> #+begin_src c++ -n :firstline 23 >> static struct >> { >> char *entity; >> unsigned char equiv; >> } entities[] = >> { >> { "lt", '<' } , >> { "gt", '>' } , >> { "amp", '&' } , >> { "quot", '"' } , >> { "trade", 153 } , /* trade mark */ >> #+end_src >> >> I didn't find it in the `element' structure. >> >> However, if I use >> >> #+begin_src c++ firstline=23 >> // random C++ >> #+end_src >> >> I could access :parameters from `element' and parse the string. >> However I'm not sure if I'd break some babel stuff or not. >> > > C-c C-v C-i on that src block shows that 'firstline=23' is treated as > a switch by babel. So if there is any language that tries to use that > as a switch (or has a regexp that matches it), there could be trouble. > > But in C it looks innocuous. > >> If I'm trying to implement a firstline feature -- source blocks with >> new line numbering (-n) beginning at a given line number -- I'd prefer >> to use :firstline, but I didn't find anything to suggest `:XXX ZZ' >> header arguments to source blocks are available to the exporters. >> > > HTH, > > Chuck -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu