From: Benjamin Beckwith <bnbeckwith@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: How to customize the org-mode's BEGIN_SRC HTML output
Date: Tue, 24 Aug 2010 09:39:45 -0400 [thread overview]
Message-ID: <AANLkTinLUSkXJRk3Co_yJrPWcfhPULuVG_JkuEc+nMtt@mail.gmail.com> (raw)
Hi, I also was interested in posting these blocks (through org2blog in
wordpress). The code I posted below is added to
'org-export-preprocess-hooks' where it looks for BEGIN_SRC blocks as
well as ':' blocks of code.
In the case of BEGIN_SRC blocks, I add a header option, :syntaxhl where
I can pass in additional settings to the syntaxhighlighter code.
The code below uses Wordpress shortcodes, but I am sure that you can
adapt for your own purposes.
------------------------------------------------------------
(defun bnb/org2blog-src-blocks-to-wp-syntaxhighlighter ()
"Export #+BEGIN_SRC blocks as Wordpress Syntaxhighlighter
tags. There is a special header option, :syntaxhl that contains
the options to pass to syntaxhighlighter.
This is intended to be added to `org-export-preprocess-hooks'"
(interactive)
(save-window-excursion
(let ((case-fold-search t)
(colon-re "^[ \t]*:\\([ \t]\\|$\\)")
lang body headers syntaxhl
beg)
(goto-char (point-min))
(while (re-search-forward colon-re nil t)
(replace-match (match-string 1))
(beginning-of-line 1)
(insert "[text light=\"true\"]\n")
(setq beg (point))
(while (looking-at colon-re)
(replace-match (match-string 1))
(end-of-line 1)
(or (eobp) (forward-char 1)))
(end-of-line 1)
(add-text-properties beg
(if (bolp)
(1- (point))
(point))
'(org-protected t))
(insert "\n[/text]"))
(unless (boundp 'org-babel-src-block-regexp)
(require 'ob))
(while (re-search-forward
(concat "\\(" org-babel-src-block-regexp
"\\|" org-babel-inline-src-block-regexp
"\\)")
nil t)
(setq lang (match-string-no-properties 3))
(if (string-match "-" lang)
(error "SyntaxHighlighter does not support languages with '-' in
the names"))
(setq headers (match-string-no-properties 5))
(setq body (match-string-no-properties 6))
(save-match-data
(setq syntaxhl
(if (string-match ":syntaxhl[ ]+\\([^ ]+\\)" headers)
(concat " " (replace-regexp-in-string "\;" " " (match-string 1
headers))))))
(replace-match
(concat "\n\n[" lang syntaxhl "]\n" body "[/" lang "]\n")
nil t)))))
next reply other threads:[~2010-08-24 13:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 13:39 Benjamin Beckwith [this message]
2010-08-25 2:36 ` How to customize the org-mode's BEGIN_SRC HTML output Rafael
2010-08-25 8:19 ` Eric S Fraga
-- strict thread matches above, loose matches on Subject: below --
2010-08-25 3:32 Benjamin Beckwith
2010-08-25 8:30 ` Eric S Fraga
2010-08-25 12:23 ` Rafael
2010-08-25 12:51 ` Puneeth
2010-08-26 1:54 ` Rafael
2010-08-29 9:37 ` Puneeth
2010-08-29 18:18 ` Rafael
2010-09-01 10:42 ` Puneeth
2010-09-01 14:38 ` Rafael
2010-08-23 9:41 卓强 Will Zhuo
2010-08-23 19:03 ` Erik Iverson
2010-08-26 3:22 ` Andrei Jirnyi
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=AANLkTinLUSkXJRk3Co_yJrPWcfhPULuVG_JkuEc+nMtt@mail.gmail.com \
--to=bnbeckwith@gmail.com \
--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).