From: email@example.com (Thomas S. Dye)
To: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: Different spacing in html output compared to info and pdf
Date: Mon, 11 Mar 2013 12:48:09 -1000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <87li9t8yea.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 11 Mar 2013 21:38:53 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Thomas S. Dye writes:
> Nice riddle. But here's what I think is happening: your macro expansion
> ends with a texinfo export snippet. That export snippet is ignored by
> the the HTML backend as it should, but in doing so the post-blank that
> the export snippet has gobbled up greedily during parsing also
> vanishes. What I'm unsure about is how it gets back into the game for
> the texinfo export, as the plain expansion does not seem to insert it.
Oh, I didn't realize there are two sets of html files generated. The
html generated by makeinfo --html is fine. The problem is with html
generated by Org.
I haven't worked with the new html exporter at all, so I won't be much
help debugging this (as if!).
I'll need to wait for Jonathan or Nicolas to chime in.
All the best,
Thomas S. Dye
next prev parent reply other threads:[~2013-03-11 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 16:52 Different spacing in html output compared to info and pdf Thomas S. Dye
2013-03-11 20:38 ` Achim Gratz
2013-03-11 22:48 ` Thomas S. Dye [this message]
2013-03-12 10:34 ` Bastien
2013-03-13 18:25 ` Nicolas Goaziou
2013-03-21 19:12 ` Nicolas Goaziou
2013-03-25 5:41 ` Bastien
2013-03-25 19:30 ` Nicolas Goaziou
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).