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

From: cberry@tajo.ucsd.edu
To: emacs-orgmode@gnu.org
Subject: Re: new exporter drops :parameters ?
Date: Wed, 04 Jul 2012 11:19:05 -0700	[thread overview]
Message-ID: <87d34bqtie.fsf@tajo.ucsd.edu> (raw)
In-Reply-To: 878vf1gq73.fsf@gmail.com

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Charles Berry <ccberry@ucsd.edu> writes:
>
>> I am trying to put together a derived backend that makes use of Src Block
>> :parameters attribute.
>>
[deleted]
>>
>> 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):

Thanks! I get it.

It turns out I can piggyback extra info needed on the ':name' element
and use that in lieu of  ':parameters'.

BTW, "#+name: aname" and "#+NAME: aname" are handled differently in e-latex. The
former gets placed in the latex output as "\#+name: aname". Bug?

Chuck

>
>
> --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.
>
[snip]

-- 
Charles C. Berry                            Dept of Family/Preventive Medicine
cberry at ucsd edu			    UC San Diego
http://famprevmed.ucsd.edu/faculty/cberry/  La Jolla, San Diego 92093-0901

next prev parent reply	other threads:[~2012-07-04 18: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
2012-07-04 18:19   ` cberry [this message]
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=87d34bqtie.fsf@tajo.ucsd.edu \
    --to=cberry@tajo.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).