From: Bernt Hansen <bernt@norang.ca>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org, "itmejl@chrikro.net" <itmejl@chrikro.net>
Subject: Re: export to pdf tags showing
Date: Sat, 23 Jun 2012 09:44:50 -0400 [thread overview]
Message-ID: <878vfe3zxp.fsf@norang.ca> (raw)
In-Reply-To: <5383.1340222501@alphaville> (Nick Dokos's message of "Wed, 20 Jun 2012 16:01:41 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> itmejl@chrikro.net <itmejl@chrikro.net> wrote:
>
>> The new and the old exporter. How is the new envoked?
>>
>
> You have to do two things in your .emacs (or equivalent):
>
> (require 'org-export)
> (add-to-list 'load-path (expand-file-name "/path/to/org/contrib/lisp"))
>
> where you have to change the path appropriately for your situation: the
> second step allows the new exporter to pick up the new latex and html
> backends (org-e-latex.el and org-e-html.el resp.)
>
> You can then invoke the export dispatcher with
>
> M-x org-export-dispatch
>
> There is no key assigned to it yet (presumably it will sit under C-c C-e
> eventually), but you can of course define your own binding for now.
Hi Nick,
Is it possible to use the new exporter for publishing (org-publish-*)
versus standalone exports?
Thanks,
Bernt
next prev parent reply other threads:[~2012-06-23 13:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 17:22 export to pdf tags showing itmejl
2012-06-17 2:12 ` Nick Dokos
2012-06-17 8:49 ` itmejl
2012-06-17 21:39 ` Nick Dokos
2012-06-17 23:40 ` Nicolas Goaziou
2012-06-17 23:56 ` suvayu ali
2012-06-18 8:41 ` Nicolas Goaziou
2012-06-18 14:10 ` Nick Dokos
2012-06-18 16:29 ` Nicolas Goaziou
2012-06-20 19:53 ` itmejl
2012-06-20 20:01 ` Nick Dokos
2012-06-23 13:44 ` Bernt Hansen [this message]
2012-06-23 15:44 ` Nick Dokos
2012-06-23 15:45 ` Bernt Hansen
2012-06-23 15:55 ` Nick Dokos
2012-06-23 16:24 ` Nicolas Goaziou
2012-06-18 0:13 ` Nick Dokos
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=878vfe3zxp.fsf@norang.ca \
--to=bernt@norang.ca \
--cc=emacs-orgmode@gnu.org \
--cc=itmejl@chrikro.net \
--cc=nicholas.dokos@hp.com \
/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).