From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Andrea <agiugliano91@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: EXPORT_FILE_NAME error [9.0.3 (9.0.3-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20161224/)]
Date: Wed, 28 Dec 2016 09:56:47 -0800 [thread overview]
Message-ID: <alpine.OSX.2.20.1612280945060.668@charles-berrys-macbook.local> (raw)
In-Reply-To: <877f6kp1y3.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]
On Wed, 28 Dec 2016, Andrea wrote:
>
> Hello,
>
> thanks for org mode, it is great!
> I am having a problem with the latest version of org: I really would
> like to be able to export buffers in a different directory, and so far I
> used the :EXPORT_FILE_NAME: property for this use case.
>
> However, after upgrading to the latest release it seems that something
> does not work anymore: the pdf file is generated but the output
> directory is ignored!
>
> You could reproduce this by:
I cannot reproduce this. I get files /tmp/bla.pdf /tmp/bla.tex and my
reader opens the former file.
FWIW, there have been some discussions in recent months about pdf export.
On my macbook, C-h v org-latex-pdf-process RET gives:
org-latex-pdf-process is a variable defined in ‘ox-latex.el’.
Its value is ("latexmk -g -pdf -pdflatex=\"%latex\" -outdir=%o %f")
Original value was
("%latex -interaction nonstopmode -output-directory %o %f" "%latex
-interaction nonstopmode -output-directory %o %f" "%latex -interaction
nonstopmode -output-directory %o %f")
[...]
which works for macOS Sierra. See the full docstring for details.
IIRC, the original value does not work for me to export to another
directory.
HTH,
Chuck
prev parent reply other threads:[~2016-12-28 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 14:23 Bug: EXPORT_FILE_NAME error [9.0.3 (9.0.3-elpaplus @ /home/andrea/.emacs.d/elpa/org-plus-contrib-20161224/)] Andrea
2016-12-28 17:56 ` Charles C. Berry [this message]
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=alpine.OSX.2.20.1612280945060.668@charles-berrys-macbook.local \
--to=ccberry@ucsd.edu \
--cc=agiugliano91@gmail.com \
--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).