From 43033a2a6e80a67f29b78d4a6ecfb072ea6165e0 Mon Sep 17 00:00:00 2001 From: smcv Date: Wed, 13 Jun 2018 04:21:52 -0400 Subject: proposed patch would break the ability to have links in lists and other non-code-block indented content --- ...__91____91__this__93____93___in_code_blocks.mdwn | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) (limited to 'doc') diff --git a/doc/todo/Don__39__t_change_text_like___91____91__this__93____93___in_code_blocks.mdwn b/doc/todo/Don__39__t_change_text_like___91____91__this__93____93___in_code_blocks.mdwn index eca054e61..daf5d9e99 100644 --- a/doc/todo/Don__39__t_change_text_like___91____91__this__93____93___in_code_blocks.mdwn +++ b/doc/todo/Don__39__t_change_text_like___91____91__this__93____93___in_code_blocks.mdwn @@ -33,3 +33,24 @@ Related to [[bugs/wiki links still processed inside code blocks]] and [[forum/How_to_format___91____91__foobar__93____93___in_code_blocks__63__]]. [[!tag patch]] + +> It looks as though this patch would break linkification in any syntactic construct that +> uses indentation but isn't a code block, for instance a list: +> +> * This is a list +> * So is this +> * And \[[this is a link|http://example.com]] +> +> rendered as: +> +> * This is a list +> * So is this +> * And [[this is a link|http://example.com]] +> +> It's also assuming that Markdown is the only language available (trying to use Markdown +> rules), and even in Markdown it doesn't support Github-style fenced code blocks if enabled. +> +> This is not something that can be done correctly by just patching the link plugin. +> I'm not sure whether it's something that can be done correctly at all, unfortunately. +> +> [[!tag reviewed]] --[[smcv]] -- cgit v1.2.3