emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <eric.schulte@gmx.com>
To: Mikhail Titov <mlt@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to get to work non-interactive publishing?
Date: Mon, 21 May 2012 14:10:47 -0400	[thread overview]
Message-ID: <87zk91l80o.fsf@gmx.com> (raw)
In-Reply-To: <008101cd378b$e993c5d0$bcbb5170$@us> (Mikhail Titov's message of "Mon, 21 May 2012 14:57:10 -0500")

"Mikhail Titov" <mlt@gmx.us> writes:

>> -----Original Message-----
>> From: emacs-orgmode-bounces+mlt=gmx.us@gnu.org [mailto:emacs-orgmode-
>> bounces+mlt=gmx.us@gnu.org] On Behalf Of Eric Schulte
>> Sent: Saturday, May 19, 2012 5:39 PM
>> To: Mikhail Titov
>> Cc: emacs-orgmode@gnu.org
>> Subject: Re: [O] How to get to work non-interactive publishing?
>> 
>> >>> I can publish project if I don’t use –-batch . So the following works
>> >>> just fine: emacs -nw --eval '(org-publish-project "myproj")'
>> >>>
>> >>> However nothing happens if I try emacs --batch --eval '(org-publish-
>> project "myproj")'
>> ...
>> >> Using batch mode shouldn't be causing any problems with the export
>> >> process, is it possible that something in your personal config is not
>> >> compatible with batch-mode
>> ...
>> > I really did not want to create a separate init file as I was quite
>> > happy with existing dot emacs. You are right. Something was in the way.
>> > After I created a separate file that loads only necessary stuff, it
>> > published fine.
>> >
>> 
>> Happy it works, if you find the offending element of your persona
>> configuration you could remove it and continue to use your personal
>> config for batch publishing.
>> >
>> > So weird emacs did not give any error before that something is not
>> > quite right. Is there an option for emacs so that some module can say
>> > it can't work in a batch mode?
>> >
>> 
>> I don't believe that there is an automated way to raise such warnings.
>> You could do a binary search through your init.
>
> Part of my question was if there is an easy way to find it other than by dichotomy? I guess not :-)
>
>> > I mean what is the point to make a separate init file other than
>> > speed?
>> >
>> 
>> Your main init file is used to customize Emacs for interactive editing,
>> many (if not most) of these settings won't apply to batch evaluation.
>> 
>> By separating your personal customization from the project init file
>> used for publishing it becomes possible to distribute your project with
>> the publication init file without sharing your personal configuration.
>
> That makes it clear.
>
> Another weird issue I experience when batch-publishing is that even
> with a separate init file, I get different "htmlization" of babel
> blocks. I mean if I load
>
> emacs -nw -Q -l myinit.el project_part.org
>
> and publish that with C-c C-e P , then I get nicely colored babel block in HTML starting like
>
> <pre class="src src-R">  <span style="color: #cd00cd;">library</span>(RODBC)
>
> However, if I do
>
> emacs -Q --batch -l myinit.el -f 'org-publish-all'
>
> then I get something like
>
> <pre class="src src-R"><span style="font-weight: bold; text-decoration: underline;">library</span>(RODBC)
>
> It seems odd to me that same config results in different outputs when
> publishing interactively and in a batch mode. I would prefer colored
> output.
>
> What should I pay attention to? I have a feeling that something is not loaded which does in interactive mode, or vice versa.
>

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.

Best,

>
> Mikhail
>
>

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

  reply	other threads:[~2012-05-21 20:11 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 [this message]
2012-05-21 21:06           ` Mikhail Titov
2012-05-21 21:09             ` Mikhail Titov

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=87zk91l80o.fsf@gmx.com \
    --to=eric.schulte@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mlt@gmx.us \
    /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).