98e2a586eb0e911ec6b5bedeec4af5f00ee2bf6c Mon Sep 17 00:00:00 2001
From: Roland Kaufmann rlndkfmn+orgm...@gmail.com
Date: Sun, 27 Feb 2011 20:52:31 +0100
Subject: [PATCH] Fix markup problems when using references in source fragments
* org-exp.el (org-export-format-source-code-or-example): fontify one
line
On 2011-05-11 21:51, Bernt Hansen wrote:
Both the new and old patch are on the patchwork server waiting to be
addressed.
Oops, sorry my bad. I didn't realize that!
However, only the discussion from the first thread:
http://patchwork.newartisans.com/patch/525/
is revelant. The patch which
Sorry for taking so long to come back to this; I had some unrelated
problems with my system.
Please let us know if there is a useful way to generalize the workaround
presented earlier in the thread.
Attached is against the latest git tree for org-mode a patch which I
believe does the trick.
htmlize doesn't operate on the level of syntax-based fontification, it
examines the display-related properties attached to buffer text (not
necessarily by font-lock) and renders them into the corresponding HTML.
Good point.
And, as you point out, it is probably better to deal with the problem
Your patch may work in this particular case, but the idea behind
htmlize is to describe the state of the buffer. If a property ends
after the newline, it is intended that the generated HTML reflect
The philosophical question is then: Is the newline character part of the
syntax construct that
htmlize-buffer-1 does the actual insertion in the buffer.
I have tested this with all three kinds of htmlize-output-type, and it
seems to give the expected result.
--
Roland.
From 86f1508f58dd304471d768481944d34e220e24f1 Mon Sep 17 00:00:00 2001
From: Roland Kaufmann rlndkfmn+orgm...@gmail.com
