From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: [ox bug] batch export seems to be broken or have changed
Date: Sat, 18 Jul 2015 23:05:47 +0200 [thread overview]
Message-ID: <87bnf9jhw4.fsf@gmx.us> (raw)
In-Reply-To: 87h9p1ewdy.fsf@nicolasgoaziou.fr
Hi,
I hope you had a pleasant break from the PC.
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> I used to be able to something like
>>
>> emacs -Q --file foo.org --batch --no-init-file -f org-latex-export-to-pdf
>> # tex output
>>
>> And everything would work.
>>
>> Now I get something like
>>
>> emacs -Q --file foo.org --batch --no-init-file -f org-latex-export-to-pdf
>> Output file: # RET
>> Processing LaTeX file ./.tex...
>> PDF file ./.tex.pdf wasn't produced
>>
>> i.e. I'm asked about output file name.
>
> I cannot reproduce it.
I still see the problem. Are you tracking Emacs-git? I'm currently
using:
commit fa5a880f733cbbe3b0d515ed3e1cf7c6fd54cfd8
Date: Thu Jul 16 20:04:07 2015 +0200
My Makefile calling something similar to the above is not working on my PC
and asks for an input file. On my Debian 7 CI machine the Makefile is
still working... I don't have access to my other laptop ATM so I haven't
tested it there.
I tried to downgrade to Emacs 24.5, but when I batch export as above I
get:
Symbol's function definition is void: cl-struct-define
Rasmus
--
In theory, practice and theory are the same. In practice they are not
next prev parent reply other threads:[~2015-07-18 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 21:55 [ox bug] batch export seems to be broken or have changed Rasmus
2015-07-18 7:51 ` Nicolas Goaziou
2015-07-18 21:05 ` Rasmus [this message]
2015-07-19 8:21 ` Nicolas Goaziou
2015-07-19 8:55 ` Rasmus
2015-07-20 7:02 ` Nicolas Goaziou
2015-07-20 9:11 ` Rasmus
2015-07-20 9:45 ` Nicolas Goaziou
2015-07-20 13:54 ` Rasmus
2015-07-20 15:21 ` Rasmus
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=87bnf9jhw4.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
/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).