From: Nicolas Goaziou <n.goaziou@gmail.com>
To: news1142@Karl-Voit.at
Cc: emacs-orgmode@gnu.org
Subject: Re: bug: "org-export-preprocess-string: Wrong number of arguments" when doing "org-export-as-html"
Date: Fri, 01 Mar 2013 12:12:49 +0100 [thread overview]
Message-ID: <87fw0fnzke.fsf@gmail.com> (raw)
In-Reply-To: <2013-03-01T11-12-10@devnull.Karl-Voit.at> (Karl Voit's message of "Fri, 1 Mar 2013 11:18:08 +0100")
Hello,
Karl Voit <devnull@Karl-Voit.at> writes:
> * Achim Gratz <Stromeko@NexGo.DE> wrote:
>> Karl Voit <devnull <at> Karl-Voit.at> writes:
>>> #+BEGIN_SRC elisp
>>> (org-export-as-html 3 nil nil "htmlized-output" nil nil)
>>> #+END_SRC
>>
>>> Am I doing something wrong or is this a bug?
>>
>> You are trying to use the old exporter and pick up code from an earlier version
>> of Org.
>
> Oh, am I? :-O I was not aware of this. Obviously, I am no insider of
> emacs-lisp nor the exporting mechanism of Org.
>
> What is the equivalent elisp expression for using the new exporter?
`org-html-export-to-html' (output to file) and `org-html-export-as-html'
(output to temporary buffer).
For batch processing, you can also use `org-export-as', in conjunction
with `html' backend, which will output a string.
There's also `org-export-string-as', which will do the same as
`org-export-as' but will work from an input string instead of the
current buffer.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-01 11:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-27 14:17 bug: "org-export-preprocess-string: Wrong number of arguments" when doing "org-export-as-html" Karl Voit
2013-02-28 11:13 ` Achim Gratz
2013-02-28 11:22 ` Neuwirth Erich
2013-03-01 10:10 ` Karl Voit
2013-03-01 10:18 ` Karl Voit
2013-03-01 11:12 ` Nicolas Goaziou [this message]
2013-03-01 16:04 ` org-html-export-to-html instead of old exporter (was: bug: "org-export-preprocess-string: Wrong number of arguments" when doing "org-export-as-html") Karl Voit
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=87fw0fnzke.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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).