aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-09-17 12:42:40 -0400
committerJoey Hess <joey@gnu.kitenet.net>2009-09-17 12:42:40 -0400
commit356188f7c65c0e9b78e8be1e477acb785d48d3c2 (patch)
tree64ea00fe37784121bcf232359e1865129ea83dbc
parent470712618401fb3cd322c84d1c57e4b8835850d5 (diff)
downloadikiwiki-356188f7c65c0e9b78e8be1e477acb785d48d3c2.tar
ikiwiki-356188f7c65c0e9b78e8be1e477acb785d48d3c2.tar.gz
response
-rw-r--r--doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn b/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn
index 7adcb5c09..c98723f2d 100644
--- a/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn
+++ b/doc/todo/Resolve_native_reStructuredText_links_to_ikiwiki_pages.mdwn
@@ -9,6 +9,11 @@ Right now it changes rendering so that undefined pages (previous errors) are res
The page is rST-parsed once in 'scan' and once in 'htmlize' (the first to generate backlinks). Can the parse output be safely reused?
+> The page content fed to htmlize may be different than that fed to scan,
+> as directives can change the content. If you cached the input and output
+> at scan time, you could reuse the cached data at htmlize time for inputs
+> that are the same -- but that could be a very big cache! --[[Joey]]
+
Desing issues in general:
We resolve rST links without definition, we don't help resolving defined relative links, so we don't support specifying link name and target separately.