From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Kitchin Subject: Re: update on missing :parameters in code blocks Date: Mon, 22 Sep 2014 12:43:53 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57955) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XW6ic-0005IC-4J for emacs-orgmode@gnu.org; Mon, 22 Sep 2014 12:44:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XW6iX-000309-Ci for emacs-orgmode@gnu.org; Mon, 22 Sep 2014 12:44:06 -0400 Received: from mail-qg0-x236.google.com ([2607:f8b0:400d:c04::236]:39039) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XW6iX-0002zG-9F for emacs-orgmode@gnu.org; Mon, 22 Sep 2014 12:44:01 -0400 Received: by mail-qg0-f54.google.com with SMTP id a108so3157608qge.41 for ; Mon, 22 Sep 2014 09:43:55 -0700 (PDT) In-Reply-To: (Charles Berry's message of "Mon, 22 Sep 2014 02:38:07 +0000 (UTC)") 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 Charles Berry writes: Thanks for the tips. I did not see a way to do the advice here. For what I need, we need to save parameters for each code block. But it appears they are all affected by one function org-babel-exp-process-buffer, and advising this kind of function is tantamount to rewriting the function! my solution is here: http://kitchingroup.cheme.cmu.edu/blog/2014/09/22/Showing-what-data-went-into-a-code-block-on-export/ I agree it would be nice if that was unnecessary, but it is not too terrible for now. > John Kitchin andrew.cmu.edu> writes: > >> >> I did some more digging on the missing :parameters during export, and it >> seems that the src block itself is different during export than in the >> buffer. Below illustrates what I mean. In the buffer, if I look at the >> contents of the code block using output from org-element-at-point, it >> looks as I expect, with the complete header. But, using the same method >> in the export, it is clear that the header args are not there. >> >> I have not figured out where they disappear yet. >> > [snip] > > Instrument org-export-as. Then step thru it. > > Before this line: > > (org-export-execute-babel-code) > > the buffer copy ( my-buffer<2>, say ) will show the parameters/headers. > > After that line is executed, they are gone. > > You can work around this by `advicing' various babel functions and inserting > things you want to save as attributes, but it would be nice not to need > to do that. > > HTH, > > Chuck > > > > > -- ----------------------------------- John Kitchin Professor Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 http://kitchingroup.cheme.cmu.edu