From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Julius Dittmar <Julius.Dittmar@gmx.de>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: minimal testing setup for pdf export?
Date: Tue, 27 Aug 2019 08:26:55 -0400 [thread overview]
Message-ID: <CAJ51ETr3ZxBt1UHfJg1PcKXm3sx42RM5MznVBRHVarwOYJGX0A@mail.gmail.com> (raw)
In-Reply-To: <8fc0dad7-f387-0d81-7196-259f328f7f19@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Can you manually compile the empty.tex file from the command line? eg
pdflatex empty
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Tue, Aug 27, 2019 at 7:57 AM Julius Dittmar <Julius.Dittmar@gmx.de>
wrote:
> Am 27.08.19 um 12:34 schrieb Matt Price:
> > This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019/Arch
> > Linux) (preloaded format=pdflatex)
> > restricted \write18 enabled.
> > entering extended mode
> > ! I can't find file `empty.tex'.
>
> So pdflatex is called and found. Then pdflatex can't find empty.tex.
> That looks like pdflatex is called in another directory than where
> empty.tex resides. How that could happen, no idea.
>
> Julius
>
>
[-- Attachment #2: Type: text/html, Size: 1520 bytes --]
next prev parent reply other threads:[~2019-08-27 12:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 1:20 minimal testing setup for pdf export? Matt Price
2019-08-27 3:26 ` Ken Mankoff
2019-08-27 6:14 ` Robert Klein
2019-08-27 10:34 ` Matt Price
2019-08-27 11:55 ` Julius Dittmar
2019-08-27 12:26 ` John Kitchin [this message]
2019-08-27 12:57 ` Matt Price
2019-08-27 17:32 ` John Kitchin
2019-08-27 23:33 ` Matt Price
2019-08-28 8:29 ` Julius Dittmar
2019-08-29 15:27 ` John Hendy
2019-08-30 14:13 ` Matt Price
2019-08-30 14:45 ` John Hendy
2019-08-30 18:11 ` Jude DaShiell
2019-08-30 20:07 ` Nick Dokos
2019-08-30 21:10 ` Jude DaShiell
2019-08-30 23:31 ` Tim Cross
2019-08-30 23:59 ` Jude DaShiell
2019-08-31 1:46 ` Tim Cross
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=CAJ51ETr3ZxBt1UHfJg1PcKXm3sx42RM5MznVBRHVarwOYJGX0A@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=Julius.Dittmar@gmx.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 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).