emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: export_file_name problem with new exporter
Date: Fri, 7 Dec 2012 16:21:00 +0100	[thread overview]
Message-ID: <20121207152100.GN4294@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <m2fw3iark7.fsf@top.irisa.fr>

On Fri, Dec 07, 2012 at 03:02:32PM +0100, Alan Schmitt wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > You could try the publishing facilities in Org.
> >
> > (info "(org)Publishing")
> 
> I did not know about that, it's a very nice suggestion. I have one
> question that I did not see addressed in the documentation, though: is
> it possible to use it with the new exporter?
> 

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.

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.

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2012-12-07 15:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07 10:27 export_file_name problem with new exporter Alan Schmitt
2012-12-07 12:29 ` Suvayu Ali
2012-12-07 12:38   ` Alan Schmitt
2012-12-07 12:50     ` Suvayu Ali
2012-12-07 14:02       ` Alan Schmitt
2012-12-07 15:21         ` Suvayu Ali [this message]
2012-12-07 16:12           ` Alan Schmitt
2012-12-07 19:09             ` Suvayu Ali
2012-12-08 10:50               ` Alan Schmitt
2012-12-08 11:13                 ` Alan Schmitt
2012-12-08 11:54                   ` Suvayu Ali
2012-12-08 12:03                   ` Achim Gratz
2012-12-09 10:12                     ` Alan Schmitt
2012-12-09 11:04                       ` Achim Gratz
2012-12-09 13:36                         ` Suvayu Ali
2012-12-09 14:03                           ` Jambunathan K
2012-12-09 16:33                           ` Achim Gratz
2012-12-13 13:09 ` Nicolas Goaziou
2012-12-13 13:50   ` Alan Schmitt
2012-12-13 13:49     ` Nicolas Goaziou
2012-12-13 14:03       ` Alan Schmitt
2012-12-13 16:16         ` Nicolas Goaziou
2012-12-20  7:21           ` Alan Schmitt
2012-12-20  8:19             ` Achim Gratz
2012-12-20  8:22               ` Bastien
2012-12-20  9:00               ` Alan Schmitt
2012-12-13 18:03         ` Achim Gratz
2012-12-13 19:16           ` Alan Schmitt

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=20121207152100.GN4294@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    /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).