summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2009-01-06 15:02:05 -0500
committerJoey Hess <joey@gnu.kitenet.net>2009-01-06 15:02:05 -0500
commit26d3ba61467cdd5d05722015a38dc0fbd5053926 (patch)
treedbe4fb57b86f7981b097a5a913f41103eb0f86ff
parent0e7db6bd6f0288b3671daee4ec58b578c7581cee (diff)
analysis, found another bug
-rw-r--r--doc/bugs/links_misparsed_in_CSV_files.mdwn10
-rw-r--r--doc/bugs/table_external_file_links.mdwn7
2 files changed, 17 insertions, 0 deletions
diff --git a/doc/bugs/links_misparsed_in_CSV_files.mdwn b/doc/bugs/links_misparsed_in_CSV_files.mdwn
index 169c070e7..4dae4aeab 100644
--- a/doc/bugs/links_misparsed_in_CSV_files.mdwn
+++ b/doc/bugs/links_misparsed_in_CSV_files.mdwn
@@ -12,6 +12,16 @@ Oh, wait, I see the problem. IkiWiki::linkify is only called if the external fil
(this is inside /usr/share/perl5/IkiWiki/Plugin/table.pm).
+> To reproduce this bug, I had to install the old, broken markdown 1.0,
+> instead of the now-default Text::Markdown.
+>
+> Why is linkify not called for external files? Well, I checked the
+> history, and it's probably best to say "for historical reasons that no
+> longer apply".
+
I am rather confused what this check does, and the fact the comments are very different for CSV and DSV when the code is the same doesn't seem to help.
+> The code is not the same; two operations are run in different orders for
+> CSV and DSV, as the comments note. --[[Joey]]
+
-- Brian May
diff --git a/doc/bugs/table_external_file_links.mdwn b/doc/bugs/table_external_file_links.mdwn
new file mode 100644
index 000000000..f86808c77
--- /dev/null
+++ b/doc/bugs/table_external_file_links.mdwn
@@ -0,0 +1,7 @@
+If wikilinks are put in an external table file, those links are not seen at
+scan time, and so ikiwiki does not know to update the page containing the
+table when the pages the links point to change (are added, removed, etc).
+
+There seem only two solutions to that bug -- either really make wikilinks
+in an external table file not work (probably by escaping them),
+or run the preprocess code also in scan (expensive!). --[[Joey]]