emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Charles Berry <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: new exporter drops :parameters ?
Date: Tue, 03 Jul 2012 11:16:16 +0200	[thread overview]
Message-ID: <878vf1gq73.fsf@gmail.com> (raw)
In-Reply-To: <loom.20120703T053318-670@post.gmane.org> (Charles Berry's message of "Tue, 3 Jul 2012 03:51:29 +0000 (UTC)")

Hello,

Charles Berry <ccberry@ucsd.edu> writes:

> I am trying to put together a derived backend that makes use of Src Block
> :parameters attribute.
>
> I can see that the header in a begin_src block is picked up by  
>
> org-element-src-block-parser, as it should be when I try it interactively 
>
> But not when I try
>
> M-: (org-export-to-buffer 'my-latex   "*latex out*") RET
>
> I'd really like to have access to the header elements.
>
> AFAICS :parameters is nowhere to be found when using
> org-export-to-buffer.

This is because src blocks are executed before buffer is parsed. You can
try to call `org-export-blocks-preprocess' on the following buffer
(associated to a file):

--8<---------------cut here---------------start------------->8---
  #+name: bblock
  #+BEGIN_SRC R :exports code :et-cetera
  rnorm(2)+1
  #+END_SRC
--8<---------------cut here---------------end--------------->8---

and see what is really parsed: the removal happens on the Babel side.

Depending on your needs, you may want to use ATTR_LATEX keyword instead.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2012-07-03  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03  3:51 new exporter drops :parameters ? Charles Berry
2012-07-03  9:16 ` Nicolas Goaziou [this message]
2012-07-04 18:19   ` cberry
2012-07-05 20:53     ` Nicolas Goaziou
2012-07-07  3:22       ` cberry

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=878vf1gq73.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=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

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).