From: "Mikhail Titov" <mlt@gmx.us>
To: 'Eric Schulte' <eric.schulte@gmx.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to get to work non-interactive publishing?
Date: Mon, 21 May 2012 16:09:04 -0500 [thread overview]
Message-ID: <00a001cd3795$f4193580$dc4ba080$@us> (raw)
In-Reply-To: <009a01cd3795$8c04ec00$a40ec400$@us>
> -----Original Message-----
> From: emacs-orgmode-bounces+mlt=gmx.us@gnu.org [mailto:emacs-orgmode-
> bounces+mlt=gmx.us@gnu.org] On Behalf Of Mikhail Titov
> Sent: Monday, May 21, 2012 4:06 PM
> To: 'Eric Schulte'
> Cc: emacs-orgmode@gnu.org
> Subject: Re: [O] How to get to work non-interactive publishing?
>
> ...
>
> > The library used to colorize source code relies on the actual Emacs
> > colorization mechanisms, which aren't available in batch mode. The best
> > solution in this case is to save your colorized CSS information into a
> > .css file with `org-export-htmlize-generate-css', and then use that file
> > in all of your exports by setting `org-export-htmlize-output-type' to
> > 'css. This way your fontification will be consistent across batch or
> > regular export.
>
> Thank you for the explanation!
>
> Also I just noticed [1]. For now, I can just use -nw and (kill-emacs) after
> publishing is done and deal with CSS fine tuning later.
Did not read careful enough about crontab. I'll go CSS way.
>
> [1] http://stackoverflow.com/questions/3591337/emacs-htmlize-in-batch-mode
>
> M.
>
prev parent reply other threads:[~2012-05-21 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 2:40 How to get to work non-interactive publishing? Mikhail Titov
2012-05-18 12:19 ` Eric Schulte
2012-05-20 0:13 ` Mikhail Titov
2012-05-19 22:38 ` Eric Schulte
2012-05-21 19:57 ` Mikhail Titov
2012-05-21 18:10 ` Eric Schulte
2012-05-21 21:06 ` Mikhail Titov
2012-05-21 21:09 ` Mikhail Titov [this message]
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='00a001cd3795$f4193580$dc4ba080$@us' \
--to=mlt@gmx.us \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.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).