From: Bastien <firstname.lastname@example.org>
To: Dmitri Makarov <email@example.com>
Cc: "firstname.lastname@example.org" <email@example.com>
Subject: Re: htmlize doesn't work in --batch mode
Date: Wed, 19 Sep 2012 19:03:53 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <3F22EBFC-FB52-42B1-B717-482FBD010B5B@gmail.com> (Dmitri Makarov's message of "Fri, 14 Sep 2012 11:38:19 +0200")
Dmitri Makarov <email@example.com> writes:
> If anyone interested, it's easy to explicitly load the required ELPA
> packages in batch mode. For example, the following command loads htmlize
> for publishing org files in batch mode
> emacs --batch -l ~/.emacs.d/init.el --eval "(progn (add-to-list 'load-path
> \"~/.emacs.d/elpa/htmlize-20120616.1716\") (require 'htmlize))" -f
> 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.
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.
> Still I wonder why ELPA packages are not loaded by default in --batch
> mode even though (package-initialize) is being evaluated.
Please ask this on the emacs-devel mailing list, I'm sure this will help
many other users. Several users (including me) have been puzzled by the
way ELPA packages are loaded/initialized in Emacs.
next prev parent reply other threads:[~2012-09-19 17:04 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 [this message]
2012-09-19 18:29 ` Achim Gratz
2012-09-19 18:40 ` Dmitri Makarov
-- strict thread matches above, loose matches on Subject: below --
2012-09-11 13:16 Dmitri Makarov
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).