From: Charles Berry <ccberry@ucsd.edu>
To: emacs-orgmode@gnu.org
Subject: Re: update on missing :parameters in code blocks
Date: Mon, 22 Sep 2014 02:38:07 +0000 (UTC) [thread overview]
Message-ID: <loom.20140922T042141-683@post.gmane.org> (raw)
In-Reply-To: m261ggvc5t.fsf@andrew.cmu.edu
John Kitchin <jkitchin <at> 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
next prev parent reply other threads:[~2014-09-22 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-21 22:31 update on missing :parameters in code blocks John Kitchin
2014-09-22 2:38 ` Charles Berry [this message]
2014-09-22 16:43 ` John Kitchin
2014-09-22 17:10 ` Nicolas Goaziou
2014-09-22 20:50 ` John Kitchin
2014-09-22 21:24 ` Nicolas Goaziou
2014-09-22 2:39 ` Aaron Ecay
2014-09-22 16:40 ` John Kitchin
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=loom.20140922T042141-683@post.gmane.org \
--to=ccberry@ucsd.edu \
--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).