all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Florian Lindner <mailinglists@xgm.de>
To: emacs-orgmode@gnu.org
Subject: Re: There is no line to end here at LaTeX org-ref export
Date: Mon, 5 Sep 2016 22:55:40 +0200	[thread overview]
Message-ID: <nqkm4b$gh1$1@blaine.gmane.org> (raw)
In-Reply-To: <87lgzaigye.fsf@ucl.ac.uk>

Am 02.09.2016 um 15:12 schrieb Eric S Fraga:
> Can you post an actual org test file as an attachment?  And also the
> resulting LaTeX file on export?

Hey,

sorry for the late reply. I tried to reproduce the problem firstly using emacs -Q but it worked like that.

After some bisect debugging I found out that setting

(setq org-latex-pdf-process '("latexmk -f -pdf %f"))

triggered the error.

But the usual latex process also causes the error, but gives the error message

Processing LaTeX file ./test2.tex...
PDF file produced with errors.

and continues. You have no errors using that snippet? Can you compile ther resulting tex file using auctex or the
latexmk command above? And why does latexmk -f does not continue despite the error? That's what the -f option should do?
I want to use latexmk to include also bibtex generation.

Ok, after some debugging and bisecting my .emacs, org-export-preserve-breaks t seems to cause the faulty export.

Best,
Florian

  parent reply	other threads:[~2016-09-05 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30  8:22 There is no line to end here at LaTeX org-ref export Florian Lindner
2016-08-31  7:45 ` Florian Lindner
2016-09-01  6:02   ` Nick Dokos
2016-09-02 13:04     ` Florian Lindner
     [not found]     ` <97bdf173ef3049a9871038d52cd55df7@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-02 13:12       ` Eric S Fraga
2016-09-02 16:01         ` Nick Dokos
2016-09-05 20:55         ` Florian Lindner [this message]
2016-09-05 21:34           ` John Kitchin
     [not found]         ` <f07593c389194c028f4a2ca0a5933e13@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-09-06  6:41           ` Eric S Fraga
2016-08-31  7:48 ` Florian Lindner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='nqkm4b$gh1$1@blaine.gmane.org' \
    --to=mailinglists@xgm.de \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.