From: Brett Viren <bv@bnl.gov>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Overriding org-html-headline or other export functions?
Date: Mon, 29 May 2017 14:20:34 -0400 [thread overview]
Message-ID: <86poer1q4t.fsf@bnl.gov> (raw)
In-Reply-To: <alpine.OSX.2.20.1705291012091.772@charles-berrys-macbook.local> (Charles C. Berry's message of "Mon, 29 May 2017 10:38:06 -0700")
"Charles C. Berry" <ccberry@ucsd.edu> writes:
> You do have that wrong. This is exactly what export filters and
> derived backends are for. In fact, you can use both. For an example,
> see
>
> http://orgmode.org/worg/exporters/filter-markup.html
>
> You will want to change `latex' to `html' in the
>
> `(org-export-define-derived-backend ...)'
>
> call and delete all filters except for `:filter-headline'. And revise
> `ox-mrkup-filter-headline' accordingly.
Thanks for checking me on this, but I still don't see it.
If I understand, a derived HTML backend with my own filter-headline
would let me add my own extra HTML *outside* the "<h1>...</h1>",
"<h2>...</h2>", etc, HTML that is generated by the base
org-html-headline filter. But for the output I want I need to add my
extra HTML *inside* the contents of the "<hN>...</hN>" tags. And I
don't see an export filter for this "..." part.
Or, maybe you suggest I do direct "surgery" on the TEXT argument that
gets passed in to the filter and insert the "..." that way? I guess it
could work to find the end of the "<hN...>" opening tag and then insert
my "..." part. I'll try this approach.
-Brett.
next prev parent reply other threads:[~2017-05-29 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 12:22 Overriding org-html-headline or other export functions? Brett Viren
2017-05-29 17:38 ` Charles C. Berry
2017-05-29 18:20 ` Brett Viren [this message]
2017-05-29 20:34 ` Brett Viren
2017-05-29 20:35 ` Charles C. Berry
2017-05-29 18:33 ` Marcin Borkowski
2017-05-29 19:14 ` Brett Viren
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=86poer1q4t.fsf@bnl.gov \
--to=bv@bnl.gov \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.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.
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).