From: Nick Dokos <nicholas.dokos@hp.com>
To: rpgoldman@sift.info
Cc: nicholas.dokos@hp.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: centering blocks cause latex export to crash
Date: Wed, 14 Dec 2011 17:16:07 -0500 [thread overview]
Message-ID: <7353.1323900967@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Robert Goldman <rpgoldman@sift.info> of "Wed, 14 Dec 2011 15:41:14 CST." <4EE917FA.6080305@sift.info>
Robert Goldman <rpgoldman@sift.info> wrote:
> Thanks. But the workaround is not ideal here --- the centering block is
> supposed to say "Not Cleared for Public Release" for reasons of
> conditions on my research grant, and that really is not supposed to be
> in a heading.
>
Can it be in a watermark? Something like this perhaps:
#+LATEX_HEADER: \usepackage{draftwatermark}
#+LATEX_HEADER: \SetWatermarkText{Not Cleared for Public Release}
#+LATEX_HEADER: \SetWatermarkFontSize{42pt}
> I have another work-around, but I think the general principle is that
> forbidding text before the first header is not an ideal constraint. If
> there's a way to have a header that doesn't produce output (a la
> noexport), but that doesn't suppress its children, that might be a handy
> way to accomplish this. I don't know if that's possible (that would
> also be handy for outlines where you want the outline structure to "fade
> away" and just leave you with the text that the outline inspired).
>
Agreeed - I believe it's a long standing weakness in the implementation
of the exporter and I also believe we'll see a reimplementation (soon?)
based on Nicolas's parser. BTW, I wonder what the parser says about text
before the first headline.
Nick
next prev parent reply other threads:[~2011-12-14 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 21:06 centering blocks cause latex export to crash Robert Goldman
2011-12-14 21:13 ` Nick Dokos
2011-12-14 21:41 ` Robert Goldman
2011-12-14 22:16 ` Nick Dokos [this message]
2011-12-14 21:28 ` Robert Goldman
2011-12-23 17:54 ` Bastien
2011-12-23 18:41 ` Nick Dokos
2011-12-24 22:27 ` Robert Goldman
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=7353.1323900967@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=rpgoldman@sift.info \
/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).