From: "G. Jay Kerns" <email@example.com>
To: "Jan Böcker" <firstname.lastname@example.org>
Subject: Re: how to both :body-only t and :table-of-contents t
Date: Fri, 23 Sep 2011 07:32:56 -0400 [thread overview]
Message-ID: <CAJKctopRUHg8Lx9JBL9ZGo+4f4oOxmZeu7-w=qFHzyRhi8MQcw@mail.gmail.com> (raw)
On Fri, Sep 23, 2011 at 3:51 AM, Jan Böcker <email@example.com> wrote:
> Hi Jay,
> I faced the same problem about a year ago.
> See this thread in the mailing list archive:
> The HTML exporter will refuse to include a TOC if body-only is t; the
> atom exporter and a "send HTML messages with Wanderlust" hack relied on
> that behaviour, which is why this was not changed in the official Org
> You can either apply the one-line patch I included in the linked thread
> or ask Ian Barton about his solution using jQuery he mentioned at the
> end of that thread.
Thanks; I was afraid it was going to be something like that, and am
appreciative that I don't need to reinvent this particular wheel. My
previous workaround was to export once with TOC, copy-paste the TOC
bit to the org-file in a #+BEGIN_HTML block, then export again with
:body-only t. But each run takes a couple of hours (another question
for another day), which is a pain, and not convenient should the
document structure change.
I noticed in the thread that Carsten mentioned writing a "hook" that
strips the other stuff. Don't have much experience writing hooks, but
there should be a way to write a custom publishing function just like
the current one which strips everything but the TOC. I'll use your
patch while I continue thinking about it.
prev parent reply other threads:[~2011-09-23 11:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 19:40 how to both :body-only t and :table-of-contents t G. Jay Kerns
2011-09-23 7:51 ` Jan Böcker
2011-09-23 11:32 ` G. Jay Kerns [this message]
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).