From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Bastien <bzg@altern.org>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: backend specific preprocess hook
Date: Fri, 19 Aug 2011 00:03:35 +0200 [thread overview]
Message-ID: <CAMXnza1gGrJbiceg3e9dCt_UmbCuspRTsG2tcVFAJD82AV0euw@mail.gmail.com> (raw)
In-Reply-To: <8739gymyft.fsf@gnu.org>
Hi Bastien,
On Thu, Aug 18, 2011 at 7:17 PM, Bastien <bzg@altern.org> wrote:
>> [1] IIUC I have to customise the `org-export-preprocess-hook'?
>
> Yes, and test against `org-export-current-backend' to see whether you
> are exporting to HTML or LaTeX.
I have this working now. Works great. I should have reported back with
my solution:
(defun my-org-export-preprocess-hook ()
"My backend specific export preprocess hook."
(save-excursion
(if (eq org-export-current-backend 'latex)
(let* ((tag "ignoreheading")) ; Thanks to Nick for this
(org-map-entries (lambda ()
(delete-region (point-at-bol) (point-at-eol)))
(concat ":" tag ":"))))
(if (eq org-export-current-backend 'html)
(let* ((match "Qn"))
(org-map-entries (lambda ()
(org-set-property "HTML_CONTAINER_CLASS"
"question"))
match)))))
(add-hook 'org-export-preprocess-hook 'my-org-export-preprocess-hook)
The html customisation is incomplete for the moment (for the lack of
time :-p). My goal is to have custom styles for headlines tagged with
"Qn" (unanswered questions) and "QnA" (questions with complete
answers).
Actually I was also hoping to colour code my latex export based on a
similar philosophy using \todo[inline] and PROPERTIES. But I haven't
had the time to investigate the possibilities yet. I will put it on
Worg if I do manage to figure it out. :)
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2011-08-18 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 14:28 backend specific preprocess hook suvayu ali
2011-08-18 17:17 ` Bastien
2011-08-18 22:03 ` suvayu ali [this message]
2011-08-19 7:46 ` Bastien
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=CAMXnza1gGrJbiceg3e9dCt_UmbCuspRTsG2tcVFAJD82AV0euw@mail.gmail.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=bzg@altern.org \
--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).