From: Eric S Fraga <esflists@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: what settings would make original export to pdf as good as pandoc conversion?
Date: Mon, 19 Mar 2018 09:52:52 +0000 [thread overview]
Message-ID: <87370ws87f.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <CAJcAo8uEV45QamjR=zCHe09LT-jmJ2wuhDW4OmD2nOE-=gRAmg@mail.gmail.com> (Samuel Wales's message of "Sun, 18 Mar 2018 21:41:29 -0700")
[-- Attachment #1: Type: text/plain, Size: 1484 bytes --]
On Sunday, 18 Mar 2018 at 21:41, Samuel Wales wrote:
> On 3/13/18, Eric S Fraga <esflists@gmail.com> wrote:
>> Could you post a minimal example that illustrates this?
>
> here is the minimal example. [btw, it turns out that pandoc erros
> now, so i have to either get your direct export code to work, or fix
> pandoc's export.]
Couple of things:
1. Start your document with a top level heading, i.e. single * heading.
2. Remove any whitespace before the \[...] entries in your
org-latex-classes setting.
For instance, this seems to work fine for me although obviously with no
real content it is difficult to see the settings taking effect:
* NEXTKA fixing pdf to have better paragraphs
SCHEDULED: <2018-03-21 Wed>
#+begin_src emacs-lisp
(add-to-list 'org-latex-classes
'("article"
"
\\documentclass{scrartcl}
\[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}")))
#+end_src
--
Eric S Fraga via Emacs 27.0.50, Org release_9.1.7-475-g3ffc7d
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2018-03-19 9:53 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 [this message]
2018-03-25 0:23 ` Samuel Wales
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=87370ws87f.fsf@delle7240.chemeng.ucl.ac.uk \
--to=esflists@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).