public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Ulrike Fischer <luatex-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Re-open #2889? Or create a new bug?
Date: Tue, 3 May 2016 12:27:55 +0200	[thread overview]
Message-ID: <1m7ye3farembp.dlg@nililand.de> (raw)
In-Reply-To: <6f5f70b7-802d-4fcb-ba05-e211149c890a@googlegroups.com>

Am Mon, 2 May 2016 07:57:22 -0700 (PDT) schrieb kurt.pfeifle via
pandoc-discuss:

> I don't know if (or how) I could re-open issue #2889, or wether I should 
> start a new issue.
> 
> However, I'm experiencing the same (I think) page-overflowing bug as in 
> issue #2889. 

There are lots of (different) ways to get overfull pages. One is to
assemble enough material without legal break point.

http://tex.stackexchange.com/a/57861/2388




-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/


  parent reply	other threads:[~2016-05-03 10:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 14:57 kurt.pfeifle via pandoc-discuss
     [not found] ` <6f5f70b7-802d-4fcb-ba05-e211149c890a-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2016-05-02 15:36   ` John MacFarlane
     [not found]     ` <20160502153607.GB43753-jF64zX8BO091tJRe0FUodcM6rOWSkUom@public.gmane.org>
2016-05-02 15:44       ` kurt.pfeifle via pandoc-discuss
2016-05-02 15:52   ` John Muccigrosso
2016-05-02 16:33   ` Joost Kremers
     [not found]     ` <87mvo8zafi.fsf-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2016-05-02 18:00       ` BP Jonsson
2016-05-03 10:27 ` Ulrike Fischer [this message]
     [not found]   ` <1m7ye3farembp.dlg-bMiYgyzgJ3Ab1SvskN2V4Q@public.gmane.org>
2016-05-03 18:39     ` John MACFARLANE
     [not found]       ` <20160503183915.GB21146-nFAEphtLEs/fysO+viCLMa55KtNWUUjk@public.gmane.org>
2016-05-05 18:30         ` BP Jonsson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1m7ye3farembp.dlg@nililand.de \
    --to=luatex-bmiygyzgj3ab1svskn2v4q@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).