Re: export_file_name problem with new exporter

[Suvayu Ali <fatkasuvayu+linux@gmail.com>]

On Fri, Dec 07, 2012 at 05:12:46PM +0100, Alan Schmitt wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > Since the new exporter is not documented yet, information is absent from
> > the info manual.  You can find relevant docs in the source files.  I am
> > slowly working towards a tutorial type docs for org-e-beamer.  When it
> > is in shape, I'll push to Worg.
> 
> Great.
> 
> > That said, publishing is fully supported by the new exporter, just
> > change the publishing function names to the functions provided by the
> > new exporter.
> >
> > Here is an improperly tested example from one of my tests:
> >
> > (setq org-e-publish-project-alist
> >       '(("thesis" :components ("thesis-tex" "thesis-html"))
> > 	("thesis-tex" :base-directory "/path/PhD-thesis"
> > 	 :publishing-directory "/path/PhD-thesis/latex"
> > 	 :publishing-function org-e-publish-org-to-latex
> > 	 )))
> >
> > Hope this helps.
> 
> It does, but for some reason I can't make it work. It seems that it has
> issues getting the base file. Here is my setup:
> 
> (setq org-e-publish-project-alist
>       '(("jsseccloud"
>          :base-directory "~/Documents/Org"
>          :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org"
>          :publishing-directory "~/tmp"
>          :publishing-function org-e-beamer-publish-to-latex
>          )))
> 
> and with this I get an error:
> 

I believe that is because org-e-beamer does not support publishing yet.
Nicolas can confirm.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.