emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alex Fenton <alex.fenton@pressure.to>
To: emacs-orgmode@gnu.org
Subject: Re: latex exporting to different directory with v9.0
Date: Thu, 10 Nov 2016 17:30:13 +0100	[thread overview]
Message-ID: <5e2a85ad-90f1-de3c-7bcd-1d80374dd733@pressure.to> (raw)
In-Reply-To: <87oa1pkgkb.fsf@nicolasgoaziou.fr>

Hello,

On 08/11/16 18:49, Nicolas Goaziou wrote:
> Per above, you could use latexmk "-C" option and move both ".tex" and
> ".pdf" file to appropriate directories.

I wasn't aware of the "-C" option, it looks like it could - with some 
settings - blow away the intermediate files that latexmk uses to 
minimise compile passes.

> This breaks the export process, because `org-compile-file' can no longer
> find, and return, the produced file. `org-compile-file' has to know
> where the output is.

Ah, OK. I'm curious, however, how a compiler (eg tex2dvi) cd'd to a 
different working directory can ever resolve links to image files.


> One problem is that we already provide compilation commands that do not
> set it (e.g., the "texi2dvi" command above). As I wrote, if we leave
> default-directory alone, something else has to be fixed.
>
> In any case, I removed default-directory setting and, hopefully, applied
> the necessary changes to commands.

I'm very grateful for your help with this and for trying this 
change/reversion. I'll try it with the next release.

Best,
alex

  reply	other threads:[~2016-11-10 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 11:54 latex exporting to different directory with v9.0 Alex Fenton
2016-11-05 22:54 ` Nicolas Goaziou
2016-11-06 11:39   ` Alex Fenton
2016-11-08 17:49     ` Nicolas Goaziou
2016-11-10 16:30       ` Alex Fenton [this message]
2016-11-11  9:26         ` 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=5e2a85ad-90f1-de3c-7bcd-1d80374dd733@pressure.to \
    --to=alex.fenton@pressure.to \
    --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).