emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <esflists@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: does this pandoc error look familiar to anybody?
Date: Mon, 19 Mar 2018 09:56:48 +0000	[thread overview]
Message-ID: <87tvtcqtgf.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <CAJcAo8tkwZtSkRbJ_OHqb6nMM0Sodxn0oext0TDyPGL1NP7BNw@mail.gmail.com> (Samuel Wales's message of "Sun, 18 Mar 2018 21:43:58 -0700")

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

On Sunday, 18 Mar 2018 at 21:43, Samuel Wales wrote:
> exporting to html, then converting to pdf errors.  it worked ok
> before.  just wondering if anybody has seen this before and can guess
> if i did something wrong at the org level?

hard to know without seeing the actual input file but, if this happens
to be related to your other posting regarding exporting to PDF, LaTeX
has a limit on the number of levels, both headings and items.  If you
have an org document (assuming you started with org to generate the
HTML) which has >8 levels, you are likely to run into this problem.

-- 
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 --]

  reply	other threads:[~2018-03-19  9:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-19  4:43 does this pandoc error look familiar to anybody? Samuel Wales
2018-03-19  9:56 ` Eric S Fraga [this message]
2018-03-19 22:10   ` Samuel Wales
2018-03-20  7:42     ` Eric S Fraga
2018-03-20 18:04       ` Nick Dokos
2018-03-20 20:00       ` Samuel Wales
2018-03-24 23:58         ` Samuel Wales
2018-03-25  8:57           ` Julius Dittmar
2018-03-25 23:55             ` Samuel Wales
2018-03-19 12:02 ` Adonay Felipe Nogueira
2018-03-19 12:30   ` Colin Baxter
2018-03-19 13:33     ` Peter Neilson

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=87tvtcqtgf.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).