From: henry atting <email@example.com>
Subject: Re: new html exporter
Date: Sat, 29 Sep 2012 18:19:25 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Robert Klein <email@example.com> writes:
> On 09/29/2012 01:36 PM, henry atting wrote:
>> I gave the new html exporter a try (org-e-html-to-file). The export
>> obviously ignores my setup file, and so the path to my css and js files.
>> Maybe with the new exporter everything has changed and I only miss a
>> good tutorial?
> Do you want to export a single file or do you want to publish a
> complete project?
Only a single file. I understand that something like this will no work
anymore with the new exporter.
whereby the content of the setup file is:
#+STYLE: <link rel="stylesheet" type="text/css" href="/home/me/.style.css" />
#+INFOJS_OPT: view:info toc:t path:/home/me/.org-info.js
Besides I'm pretty happy with the old exporter and was only curious
because I read that it will be replaced with the new one in a future
stable version. I hope the old one will remain part of contrib (or
antique or whatever) so I can choose to my liking.
> As for projects, the setup is very similar to the old exporter. I
> noticed however, I used some deprecated options or options not in the
> right way, so I did have my own problems getting publishing to work.
> Until recently you had to require org-e-html in your .emacs for
> publishing to work. Thanks to Nicolas great help this and some other
> obstacles are removed in recent git versions (master branch, not
> I attached a description of an example project using the new exporter.
> The example isn't comprehensive, but it should get you started.
> Best regards
next prev parent reply other threads:[~2012-09-29 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 11:36 henry atting
2012-09-29 15:18 ` Robert Klein
2012-09-29 16:19 ` henry atting [this message]
2012-09-29 16:51 ` Nicolas Goaziou
2012-09-30 10:06 ` henry atting
2012-09-30 10:29 ` Nicolas Goaziou
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).