From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: do you need a separate LaTeX installation to export org mode files to pdf?
Date: Mon, 22 Jan 2018 17:32:26 +0100 [thread overview]
Message-ID: <871sihj1lx.fsf@gmx.us> (raw)
In-Reply-To: CAM+rpYk+xfAJt6P-p5EhPD032X-5Vpg=gTMF+Fby-=TSX0dg5A@mail.gmail.com
Christopher W Ryan <cryan@binghamton.edu> writes:
> I'm a longtime LaTeX user and a more recent org mode user. So I've always
> had LaTeX installed on any computer on which I was using org mode. I'd like
> to introduce org mode to a co-worker unfamiliar with the whole concept of
> plain text files, markup, and literate programming, etc. Would they need
> to install LaTeX too, or is org mode self-contained and able to export to
> pdf without LaTeX an friends installed?
You /could/ use latexonline. I think it even supports bibtex.
https://github.com/aslushnikov/latex-online
Here’s a minimal example.
* TODO headline
*bf* /emph/ etc.
| a |
#+begin_src emacs-lisp
(let ((str (mapconcat 'identity
'("tar -cj %f" "|"
"curl -L --post301 --post302 --post303 -F file=@-"
"\"https://latexonline.cc/data?command=%latex&target=%f\""
"> %b.pdf")
'" ")))
(setq org-latex-pdf-process (list str)))
#+end_src
How to include all document dependencies (e.g. images) in the tar file is
left as an exercise for the motivated reader. One could probably make a
"dumb" but effective solution by finding all instances of certain file
types in the project folder.
Needless to say, if you use this with real-life documents, you will
probably want to set up your own instance of latexonline.
Rasmus
--
There are known knowns; there are things we know that we know
next prev parent reply other threads:[~2018-01-22 16:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:56 do you need a separate LaTeX installation to export org mode files to pdf? Christopher W Ryan
2018-01-22 15:21 ` Kaushal Modi
2018-01-22 15:44 ` Martin Alsinet
2018-01-22 15:48 ` Oleh Krehel
2018-01-22 16:32 ` Rasmus [this message]
2018-02-09 22:46 ` Adonay Felipe Nogueira
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=871sihj1lx.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).