Re: export_file_name problem with new exporter

[Alan Schmitt <alan.schmitt@polytechnique.org>]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

>> > 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.

Well, replacing "org-e-beamer-publish-to-latex" by
"org-e-latex-publish-to-latex" results in the same error. I looked at
the code, and my problem was that ":include" expects a list, so I'm able
to make this .

I'll try to see if adding beamer support is difficult.

Alan