emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Samuel Wales <samologist@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: what settings would make original export to pdf as good as pandoc conversion?
Date: Sat, 24 Mar 2018 17:23:18 -0700	[thread overview]
Message-ID: <CAJcAo8ttxs5Pcv29zeh-SjL5_1VvnX-We2djJ=5n8iUxgC_QMw@mail.gmail.com> (raw)
In-Reply-To: <87370ws87f.fsf@delle7240.chemeng.ucl.ac.uk>

i find that the following does not take effect the first time, but
works the second time.  not sure why that would be.

it looks much better now.  i think the main thing i would want is to
color links differently from the default red box, like maybe color the
text "#8968cd" and underline it so it looks kind of like a web page.

also, the pronoun "I" is boldface, which is disconcerting.  Acronyms
are also, but that is less disconcerting.

(add-to-list 'org-latex-classes
             '("article"
               "
\\documentclass{scrartcl}
% alpha is the single \ for these three correct?
\[DEFAULT-PACKAGES]
\[PACKAGES]
\[EXTRA]
\\setlength{\\parindent}{0pt}
\\setlength{\\parskip}{6pt}
"
               ("\\section{%s}" . "\\section*{%s}")
               ("\\subsection{%s}" . "\\subsection*{%s}")
               ("\\subsubsection{%s}" . "\\subsubsection*{%s}")
               ("\\paragraph{%s}" . "\\paragraph*{%s}")
               ("\\subparagraph{%s}" . "\\subparagraph*{%s}")))

> 1. Start your document with a top level heading, i.e. single * heading.

subtree.

> 2. Remove any whitespace before the \[...] entries in your
>    org-latex-classes setting.

this seemed to work [when i run it twice at least].  thank you!

aren't the single \ removed by emacs lisp's string object parsing?

  reply	other threads:[~2018-03-25  0:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-01 23:09 what settings would make original export to pdf as good as pandoc conversion? Samuel Wales
2018-03-02  3:08 ` Samuel Wales
2018-03-02  7:08 ` Eric S Fraga
2018-03-02 18:53   ` Samuel Wales
2018-03-02 19:37     ` Diego Zamboni
2018-03-03 11:26     ` Eric S Fraga
2018-03-08 19:55       ` Samuel Wales
2018-03-09  6:34         ` Eric S Fraga
2018-03-09 20:26           ` Samuel Wales
2018-03-10  0:05             ` Eric S Fraga
2018-03-10  0:30               ` Samuel Wales
2018-03-12  9:42                 ` Eric S Fraga
2018-03-12 20:55                   ` Samuel Wales
2018-03-12 23:42                   ` Samuel Wales
2018-03-13  7:21                     ` Eric S Fraga
2018-03-19  4:41                       ` Samuel Wales
2018-03-19  4:48                         ` Samuel Wales
2018-03-19  9:52                         ` Eric S Fraga
2018-03-25  0:23                           ` Samuel Wales [this message]
2018-03-25 11:54                             ` Eric S Fraga

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='CAJcAo8ttxs5Pcv29zeh-SjL5_1VvnX-We2djJ=5n8iUxgC_QMw@mail.gmail.com' \
    --to=samologist@gmail.com \
    --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).