Re: [O] [new exporter] workaround/replacement for org-export-as-html-batch

2013-02-13 Thread Detlef Steuer 
On Tue, 12 Feb 2013 20:34:55 +0100
Nicolas Goaziou n.goaz...@gmail.com wrote:

 Does `org-html-export-to-html' works as a replacement for
 `org-export-as-html-batch'?

Yes! Thank you so much!

Detlef

[O] [new exporter] workaround/replacement for org-export-as-html-batch

2013-02-12 Thread Detlef Steuer 
Dear all,

I rely on

emacs --batch \
  --eval (add-to-list 'load-path \${HOME}/GIT/org-mode/lisp/\)\
  --load ${HOME}/GIT/org-mode/lisp/org.el \
  --visit file.org \
  --funcall org-export-as-html-batch

somewhere in my HTML generating workflow.

I see org-export-as-html-batch in the FIXME section in the source.

Is there any easy workaround for the moment? Or a guess when it will leave that 
section?

Naively loading the old stuff by adding a
  ---eval (add-to-list 'load-path 
\${HOME}/GIT/org-mode/contrib/oldexp/\)\
line to the call above did not work either.
I then get: 
---
Exporting...
Symbol's value as variable is void: org-export-with-sub-superscripts
---

What worked was de-automating that step and export manually, so it's not an 
emergency.

Obviously my google-fu wasn't up to the task, too.

All that with orgmode from today.

Thanks for any help
Detlef

Re: [O] [new exporter] workaround/replacement for org-export-as-html-batch

2013-02-12 Thread Nicolas Goaziou 
Hello,

Detlef Steuer detlef.ste...@gmx.de writes:

 I rely on

 emacs --batch \
   --eval (add-to-list 'load-path \${HOME}/GIT/org-mode/lisp/\)\
   --load ${HOME}/GIT/org-mode/lisp/org.el \
   --visit file.org \
   --funcall org-export-as-html-batch

 somewhere in my HTML generating workflow.

You may want to set-up a publishing project instead.

Does `org-html-export-to-html' works as a replacement for
`org-export-as-html-batch'?

 I see org-export-as-html-batch in the FIXME section in the source.

The FIXME section ought to be fixed anyway.

 Is there any easy workaround for the moment? Or a guess when it will leave 
 that section?

 Naively loading the old stuff by adding a
   ---eval (add-to-list 'load-path 
 \${HOME}/GIT/org-mode/contrib/oldexp/\)\
 line to the call above did not work either.
 I then get: 
 ---
 Exporting...
 Symbol's value as variable is void: org-export-with-sub-superscripts
 ---

The old export framework is not usable anymore from master branch.


Regards,

-- 
Nicolas Goaziou