From: Phil <phil@beadling.co.uk>
To: help-guix@gnu.org
Subject: Export PDFs in Emacs Org
Date: Fri, 12 Mar 2021 14:55:15 +0000 [thread overview]
Message-ID: <857dmcmnfw.fsf@beadling.co.uk> (raw)
Hi,
I've been trying to export emacs org files into PDFs using Guix.
I've the PDF generation from the .tex file is failing.
The issue has been discussed a few times previously, eg:
https://lists.gnu.org/archive/html/help-guix/2019-02/msg00087.html
But there is conflicting advice over what packages should or shouldn't
be installed typically some combinaton of:
texlive-base, texlive-bin, texlive-latex-base, texlive-latext-font
The latest advice seems to be the only texlive-base should be necessary
and installing others will cause an issue - with that in mind I
attempted the below, but got a new failure.
I've recreated the pdflatex step on the command line - it gives exactly
the same error as the emacs error buffer contains.
The org file exports without issue in Ubuntu 18.04 with the following
(which may be more than I need):
sudo apt-get install texlive-latex-base texlive-fonts-recommended
texlive-fonts-extra texlive-latex-extra emacs python3 python3-pygments
Any ideas what the minimum Guix package set is (or even a carpet-bomb
approach with a meta-package would be OK)?
Thanks,
Phil.
$ guix package -p profiles/book -m profiles/book.manifest
guix package: warning: Your Guix installation is 47 days old.
guix package: warning: Consider running 'guix pull' followed by
'guix package -u' to get up-to-date packages and security updates.
The following packages will be installed:
emacs 27.1
python 3.8.2
python-pygments 2.6.1
texlive-base 51265
hint: Consider setting the necessary environment variables by running:
GUIX_PROFILE="/home/foo/profiles/book"
. "$GUIX_PROFILE/etc/profile"
Alternately, see `guix package --search-paths -p "/home/foo/profiles/book"'.
$ GUIX_PROFILE="/home/foo/profiles/book"
$ . "$GUIX_PROFILE/etc/profile"
$ pdflatex Developer-Setup.tex
This is pdfTeX, Version 3.14159265-2.6-1.40.20 (TeX Live 2019) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./Developer-Setup.tex
LaTeX2e <2018-12-01>
(/home/foo/profiles/book/share/texmf-dist/tex/latex/base/book.cls
Document Class: book 2018/09/03 v1.4i Standard LaTeX document class
(/home/foo/profiles/book/share/texmf-dist/tex/latex/base/bk10.clo)) (/home/foo/profiles/book/share/texmf-dist/tex/latex/base/inputenc.
sty) (/home/foo/profiles/book/share/texmf-dist/tex/latex/base/fontenc.sty (/home/foo/profiles/book/share/texmf-dist/tex/latex/base/t1e
nc.def)
kpathsea: Running mktextfm ecrm1000
mktextfm: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ecrm1000
This is METAFONT, Version 2.7182818 (TeX Live 2019) (preloaded base=mf)
kpathsea: Running mktexmf ecrm1000
! I can't find file `ecrm1000'.
<*> \mode:=ljfour; mag:=1; nonstopmode; input ecrm1000
Please type another input file name
! Emergency stop.
<*> \mode:=ljfour; mag:=1; nonstopmode; input ecrm1000
Transcript written on mfput.log.
grep: ecrm1000.log: No such file or directory
mktextfm: `mf-nowin -progname=mf \mode:=ljfour; mag:=1; nonstopmode; input ecrm1000' failed to make ecrm1000.tfm.
kpathsea: Appending font creation commands to missfont.log.
! Font T1/cmr/m/n/10=ecrm1000 at 10.0pt not loadable: Metric (TFM) file not found.
<to be read again>
relax
l.105 \fontencoding\encodingdefault\selectfont
next reply other threads:[~2021-03-12 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 14:55 Phil [this message]
2021-03-12 15:57 ` Export PDFs in Emacs Org Ricardo Wurmus
2021-03-12 20:33 ` Phil Beadling
2021-03-12 22:35 ` Dr. Arne Babenhauserheide
2021-03-12 22:53 ` Ricardo Wurmus
2021-03-14 1:04 ` Phil
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=857dmcmnfw.fsf@beadling.co.uk \
--to=phil@beadling.co.uk \
--cc=help-guix@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.
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).