From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Export PDFs in Emacs Org
Date: Fri, 12 Mar 2021 23:35:07 +0100 [thread overview]
Message-ID: <87pn04f1b8.fsf@web.de> (raw)
In-Reply-To: <87lfasnz4k.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Phil,
>
>> 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.
>
> “texlive-base” is certainly not sufficient for any real world LaTeX
> document. It contains what LaTeX developers consider the base set of
> files (i.e. texlive-latex-base), texlive-bin (which provides the
> executables), and LaTeX packages from the “required” set.
this is what I use:
https://hg.sr.ht/~arnebab/vorlesung-verteilte-systeme/browse/guix.scm
(propagated-inputs
`(
("python-pyzmq" ,python-pyzmq)
("python" ,python)
("which" ,which)
("emacs" ,emacs)
("texlive" ,texlive)
("graphviz" ,graphviz)
("plantuml" ,plantuml)
("python-pygments" ,python-pygments)
;; for ditaa
("openjdk" ,openjdk14)
))
Some of these are only necessary for source-blocks.
In addition to that a ton of fonts (all fonts guix has).
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2021-03-12 22:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 14:55 Export PDFs in Emacs Org Phil
2021-03-12 15:57 ` Ricardo Wurmus
2021-03-12 20:33 ` Phil Beadling
2021-03-12 22:35 ` Dr. Arne Babenhauserheide [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn04f1b8.fsf@web.de \
--to=arne_bab@web.de \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.