From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Martyn Jago <martyn.jago@btinternet.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] ASCII back-end for new export engine
Date: Sun, 22 Jan 2012 16:45:11 +0100 [thread overview]
Message-ID: <87zkdf3fnc.fsf@gmail.com> (raw)
In-Reply-To: <m2ipk3lrvb.fsf@btinternet.com> (Martyn Jago's message of "Sun, 22 Jan 2012 14:43:52 +0000")
Hello,
Martyn Jago <martyn.jago@btinternet.com> writes:
> I've been playing with (org-export-dispatch) with regard to some simple
> source blocks and have a couple of observations (apologies in advance if
> source blocks are not fully implemented yet).
>
> The test code is:
>
>
> * Test
>
> #+begin_src emacs-lisp # :exports both
> ;; Add two numbers
> (+ 2 3)
> #+end_src
>
> #+results:
> : 5
>
>
> 1) The commented out `# :exports both' appears to be exported as
> uncommented and relevant (actually, this appears to be true of the
> original exporter too).
I cannot reproduce it. Anyway, see my comments below.
> 2) If the source block is executed in buffer with (org-ctrl-c-ctrl-c),
> as shown above, then the exporter appears to export the in-buffer
> results /and/ the export-generated results (where :exports is results
> or both) resulting in two sets of identical results in the export.
It's out of exporter's scope. When you ask to export some buffer, what
is really parsed is a copy of the current buffer with
`org-export-blocks-preprocess' applied to it.
So, simply apply that function in your test buffer, and you will see
what is sent to the parser. That will explain why the results appear
twice.
In other words, tweaking the output of `org-export-blocks-preprocess'
will automatically change the outcome of the export process.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2012-01-22 15:47 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 20:14 [ANN] ASCII back-end for new export engine Nicolas Goaziou
2012-01-21 20:33 ` Samuel Wales
2012-01-21 20:36 ` Samuel Wales
2012-01-21 23:04 ` Nicolas Goaziou
2012-01-22 1:28 ` Samuel Wales
2012-01-22 9:43 ` Nicolas Goaziou
2012-01-22 16:36 ` Samuel Wales
2012-01-28 10:28 ` Samuel Wales
2012-01-28 13:55 ` Nicolas Goaziou
2012-01-28 20:50 ` Samuel Wales
2012-01-28 21:32 ` Nicolas Goaziou
2012-01-28 22:15 ` Samuel Wales
2012-01-28 23:58 ` Nicolas Goaziou
2012-01-22 14:43 ` Martyn Jago
2012-01-22 15:45 ` Nicolas Goaziou [this message]
2012-01-22 16:43 ` Martyn Jago
2012-01-23 20:05 ` Eric Schulte
2012-01-23 20:49 ` Nicolas Goaziou
2012-01-22 16:35 ` Thomas S. Dye
2012-01-22 17:10 ` Nicolas Goaziou
2012-01-23 5:58 ` Thomas S. Dye
2012-01-25 17:41 ` Nicolas Goaziou
2012-01-26 6:49 ` Tweaking the export (was: Re: [ANN] ASCII back-end for new export engine) Christian Wittern
2012-01-27 13:06 ` Tweaking the export Nicolas Goaziou
2012-01-27 13:47 ` Jambunathan K
2012-01-27 14:03 ` Sebastien Vauban
2012-01-28 2:33 ` Christian Wittern
2012-01-28 2:21 ` Christian Wittern
2012-01-28 4:03 ` Eric Abrahamsen
2012-01-29 9:07 ` Nicolas Goaziou
2012-02-04 6:21 ` Christian Wittern
2012-02-17 20:06 ` Nicolas Goaziou
2012-01-26 8:44 ` [ANN] ASCII back-end for new export engine Eric S Fraga
2012-01-26 13:59 ` Thomas S. Dye
2012-01-26 15:28 ` Nicolas Goaziou
2012-01-26 17:32 ` Thomas S. Dye
2012-01-26 18:31 ` Nicolas Goaziou
2012-01-26 19:00 ` Achim Gratz
2012-01-27 12:58 ` Nicolas Goaziou
2012-01-27 13:06 ` Rick Frankel
2012-01-27 13:56 ` Nicolas Goaziou
2012-01-27 16:31 ` Achim Gratz
2012-02-01 6:44 ` Achim Gratz
2012-01-26 20:10 ` Thomas S. Dye
2012-02-01 8:36 ` Jambunathan K
2012-01-27 8:10 ` Jambunathan K
2012-01-27 13:59 ` Nicolas Goaziou
2012-01-27 15:50 ` Bastien
2012-01-27 16:29 ` Thomas S. Dye
2012-01-27 17:04 ` Jambunathan K
2012-01-27 18:13 ` Thomas S. Dye
2012-01-27 18:31 ` Jambunathan K
2012-01-27 19:21 ` Achim Gratz
2012-01-27 19:48 ` Thomas S. Dye
2012-01-27 20:10 ` Nick Dokos
2012-01-27 20:11 ` Thomas S. Dye
2012-01-23 21:33 ` Thomas S. Dye
2012-01-22 19:21 ` Thomas S. Dye
2012-01-22 20:50 ` Nicolas Goaziou
2012-01-23 6:14 ` Thomas S. Dye
2012-01-23 7:03 ` Nicolas Goaziou
2012-01-23 15:53 ` Thomas S. Dye
2012-01-23 18:18 ` Nicolas Goaziou
2012-01-23 21:27 ` Thomas S. Dye
2012-01-23 12:20 ` Andreas Leha
2012-01-27 17:00 ` Thomas S. Dye
2012-02-03 22:57 ` Nicolas Goaziou
2012-02-04 16:42 ` Thomas S. Dye
2012-02-05 2:19 ` Thomas S. Dye
2012-02-05 2:58 ` Thomas S. Dye
2012-02-05 14:09 ` Nicolas Goaziou
2012-02-06 1:34 ` Thomas S. Dye
2012-02-06 14:29 ` Nicolas Goaziou
2012-02-06 16:39 ` Thomas S. Dye
2012-02-06 17:05 ` Nicolas Goaziou
2012-02-06 18:46 ` Thomas S. Dye
2012-02-07 7:27 ` Nicolas Goaziou
2012-02-07 8:57 ` Document date and last updated date Sebastien Vauban
2012-02-07 17:45 ` Nicolas Goaziou
2012-02-07 22:29 ` Sebastien Vauban
2012-02-07 6:22 ` [ANN] ASCII back-end for new export engine Thomas S. Dye
2012-02-07 7:07 ` Nicolas Goaziou
2012-02-07 9:00 ` Sebastien Vauban
2012-02-07 17:49 ` Nicolas Goaziou
2012-02-08 7:11 ` Jambunathan K
2012-02-07 15:45 ` Thomas S. Dye
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=87zkdf3fnc.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=martyn.jago@btinternet.com \
/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).