emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Julien Cubizolles <j.cubizolles@free.fr>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Is there a *Org PDF LaTeX Output* buffer ?
Date: Sat, 1 Oct 2016 13:29:27 +0100	[thread overview]
Message-ID: <87wphstfq0.fsf@ucl.ac.uk> (raw)
In-Reply-To: <55929700b6fd4b07ac0d3c7ad1d328f8@HE1PR01MB1898.eurprd01.prod.exchangelabs.com> (Julien Cubizolles's message of "Fri, 30 Sep 2016 21:09:25 +0000")

On Friday, 30 Sep 2016 at 21:09, Julien Cubizolles wrote:
> When an export from org to pdf fails, the error message refers to a *Org
> PDF LaTeX Output* buffer that doesn't seem to have been created on my
> setup. Is it an old message from a previous behaviour long gone ?

No, this is current behaviour.  The buffer should definitely be created
but probably only if the org is exported to LaTeX without error.  It could
be the exporter is failing before it attempts to compile the LaTeX into
PDF.  Check your messages (C-h e)?  Typical error that causes the first
step to fail would be dangling links, for instance.

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.2.50.1, Org release_8.3.6-1184-g29830f

       reply	other threads:[~2016-10-01 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55929700b6fd4b07ac0d3c7ad1d328f8@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-10-01 12:29 ` Eric S Fraga [this message]
2016-10-03 17:08   ` Is there a *Org PDF LaTeX Output* buffer ? Nick Dokos
     [not found]   ` <464cb23e40da4e3d9faac4faee37d296@DB5PR01MB1895.eurprd01.prod.exchangelabs.com>
2016-10-04  6:37     ` Eric S Fraga
2016-09-30 21:09 Julien Cubizolles
2016-09-30 22:12 ` Nick Dokos
2016-10-03 14:08   ` Julien Cubizolles

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=87wphstfq0.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=j.cubizolles@free.fr \
    /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).