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: Sat, 19 May 2012 18:38:37 -0400 [thread overview]
Message-ID: <87pq9zbxua.fsf@gmx.com> (raw)
In-Reply-To: <4FB8373D.2030305@gmx.us> (Mikhail Titov's message of "Sat, 19 May 2012 19:13:49 -0500")
Mikhail Titov <mlt@gmx.us> writes:
> On 05/18/2012 07:19 AM, Eric Schulte wrote:
>>> 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")'
>>>
>>> Does anybody have an idea how to pin point the problem? It just
>>> returns almost instantaneously with no output to stderr.
>>>
>>> I do use ESS, and I have lots of R code some of which is intentionally
>>> non-cached. I’m running GNU Emacs 24.1.50.2 (revno: 108254) with
>>> default orgmode if it makes any difference.
>> 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 have a number of projects in which I
>> export using a batch Emacs process (generally from a make file). My
>> Makefile rules tend to look like the following.
>>
>> EMACS=emacs
>> BATCH_EMACS=$(EMACS) --batch -Q -l init.el document.org
>>
>> ...
>>
>> document.tex: document.org init.el
>> $(BATCH_EMACS) -f org-export-as-latex
>>
>> where init.el contains all of the init necessary for the particular
>> project. For a complete working example see the replication materials
>> at http://www.jstatsoft.org/v46/i03.
> 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.
>
> 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.
Best,
>
> M.
>
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2012-05-20 0:38 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 [this message]
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
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=87pq9zbxua.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).