< a quantity that can be divided into another a whole number of time />

Emacs Org and Tufte handout

August 8, 2020

I’ve been using Pandoc as my main backend for exporting Org documents to PDF, mainly because it was convenient way to manage bibliographic entries using Markdown markup. It is pretty nice and easy to setup. Moreover, it works with HTML output too using a template indicated either in the document header or using org-pandoc-options-for-html5. Problem is that it does not work with Babel, or at least I couldn’t export the block results (mostly R, Lisp and Python code) at some point, and I switched back to the default HTML or PDF exporter. First off, unless you give it a proper CSS file, you won’t get much from the HTML exporter. Same for the PDF output: the default Latex class is basically the “article” format. In both cases, without Pandoc it becomes harder to manage bibliographic entries and I’m looking for a lightweight solution whereby we do not have to use header options or inline Latex commands. I want my Org file to look as mauch as possible like an Org file, without extra markup. I don’t mind writing \cite commands, though.

I have used org-ref in the past, but I wanted a simpler solution, which also does not involve ox-bibtex which I found too limited. Furthermore, this time I was interested in using the Tufte handout template. I used it some years ago for my handout before looking for more standard layout with nice typographic rendering. I am aware of the Tufte Org Mode, and I should probably be using the ebib package as well. But I’m happy with my minimal setup which relies on ivy-bibtex. As I said in previous posts, Ivy really is a booster in my workflow, especially when taking notes, for I can quickly navigate into my file system or project, à la fzf, while having my Bibtex database available at any time. Also I don’t mind if I don’t get all the features from Tufte handout, like unnumbered margin notes.

Here is what I finally ended up adding my init file:

(eval-after-load "ox-latex"
  '(add-to-list 'org-latex-classes
                   --%<--- snip --->%--
                  ("\\section{%s}" . "\\section*{%s}")
                  ("\\subsection{%s}" . "\\subsection*{%s}")
                  ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
                  ("\\paragraph{%s}" . "\\paragraph*{%s}")
                  ("\\subparagraph{%s}" . "\\subparagraph*{%s}"))))

This defines a new template where we define the main document class and the packages we want to use. In this case, we do not want the default packages but we allow to define additional settings via a header option like #+LATEX_EXTRA:. Also, it is worth noting that the nobib option for the document class is the right way to avoid biblatex clashes with the natbib package. (I tried setting natbib=true in the options for the biblatex package, but it didn’t work.)

Next, we just have to define this template as our default Latex class and indicate how to compile the file(s). We can use either texi2pdf or latexmk. I use either one depending on my mood, and I no longer have to bother with multiple runs of pdflatex or lualatex.

(font-lock-add-keywords 'org-mode
                        '(("\\\\autocite{.+?}" . font-lock-keyword-face)))

(setq org-latex-default-class "tufte-handout"
      org-latex-pdf-process '("latexmk -pdf -bibtex-cond -f -outdir=%o %f"))

The bibtex-cond option allows to skip the bib(la)tex step if no bib file is used.

Note that a default config file for latexmk can be used if it is available in the $HOME directory. I have these settings in mine (~/.latexmkrc):

@default_files = ('main.tex');
$clean_ext = "bbl nav out snm";

$latex = 'latex -interaction=nonstopmode -shell-escape';
$pdflatex = 'pdflatex -shell-escape -interaction=nonstopmode';
$pdf_previewer = 'open -a Preview';

That’s it. Here’s the output for a simple memo I started writing for myself:

emacs tex

See Also

» Color schemes for Emacs and TeX » Running Emacs in a terminal » Recently » Editor war » Code & Co.