emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: async export not working for me
Date: Thu, 18 Sep 2014 14:55:36 +0200	[thread overview]
Message-ID: <87mw9xccl3.fsf@gmx.us> (raw)
In-Reply-To: 87a95x8rrf.fsf@free.fr

Hi Julien,

Julien Cubizolles <j.cubizolles@free.fr> writes:

> I could get it to work at last, thank you a lot. I noticed something
> though: when I run org-latex-export-to-pdf async on a very simple test
> org file, the *Org Export Stack* buffer displays
>
>  latex            0:07   /home/wilk/tmp/test.pdf
>
> and the minibuffer indicates that the process completed.
>
>
> When I publish a complex project, the line in this buffer is
>
>                   exit   *Org Export Process*<6>
>
> same as if there had been a problem. There is no success message in the
> minibuffer, but no error message in the *Org Export Process* buffer.

Async is solid so most likely you're still facing a bug.  Maybe
something is missing from your async init file that is available to
Org when you export without async — 'cause I expect the file to export
just fine without async.

I debug async errors by starting emacs -q, evaling my asyc init file
and exporting my non-functioning buffer without async.

Alternatively you should look for clues in `temporary-file-directory'
cf. the docstring of `org-export-async-debug'.

Hope it helps,
Rasmus

-- 
The Kids call him Billy the Saint

  reply	other threads:[~2014-09-18 13:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 15:39 async export not working for me Julien Cubizolles
2014-09-17 17:03 ` Rasmus
2014-09-17 19:45   ` Julien Cubizolles
2014-09-18  4:41     ` Julien Cubizolles
2014-09-18 12:55       ` Rasmus [this message]
2014-09-17 17:16 ` Nicolas Goaziou

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=87mw9xccl3.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).