emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: htmlize doesn't work in --batch mode
Date: Wed, 19 Sep 2012 20:29:17 +0200	[thread overview]
Message-ID: <87lig5n9xe.fsf@Rainer.invalid> (raw)
In-Reply-To: 87zk4mgd1i.fsf@bzg.ath.cx

Bastien writes:
> Dmitri Makarov <dmakarv@gmail.com> writes:
>> It should be easy to include such a command in a makefile or build.xml and
>> automatically locate the latest installation of necessary packages rather
>> than explicitly specifying the path.

That's what BTEST_POST is there for in the build system, you can set it
up to either load a package directly or add to the load-path first and
then require the package.  Just have a look to see how it is done.

> I let Achim be the final judge on this -- my intuitions in this areas
> are just too fragile.  But my gut feeling is that this would be too
> complicated, and the solution above is simple enough.

It is generally a bad idea to guess how the user configured his/her
system and a lot of init files are simply incompatible with batch mode.

However, the OP didn't have a problem with the build system if I read
him correctly.  My advice there is to make a minimal separate init file
just for the batch export process and load that.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:

  reply	other threads:[~2012-09-19 18:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-14  9:38 htmlize doesn't work in --batch mode Dmitri Makarov
2012-09-19 17:03 ` Bastien
2012-09-19 18:29   ` Achim Gratz [this message]
2012-09-19 18:40   ` Dmitri Makarov
  -- strict thread matches above, loose matches on Subject: below --
2012-09-11 13:16 Dmitri Makarov

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:

  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=87lig5n9xe.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \


* 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).