From 529146decf7f0e390964bb7aa709082af6e8639b Mon Sep 17 00:00:00 2001
From: Albert Krewinkel <albert@zeitkraut.de>
Date: Thu, 14 Jul 2016 13:23:18 +0200
Subject: Org reader: fix parsing of verbatim inlines

Org rules for allowed characters before or after markup chars were not
checked for verbatim text.  This resultet in wrong parsing outcomes of
if the verbatim text contained e.g. space enclosed markup characters as
part of the text (`=is_substr = True=`).  Forcing the parser to update
the positions of allowed/forbidden markup border characters fixes this.

This fixes #3016.
---
 tests/Tests/Readers/Org.hs | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'tests/Tests/Readers')

diff --git a/tests/Tests/Readers/Org.hs b/tests/Tests/Readers/Org.hs
index fdd9bc6bf..1f8a8a01e 100644
--- a/tests/Tests/Readers/Org.hs
+++ b/tests/Tests/Readers/Org.hs
@@ -185,6 +185,9 @@ tests =
                       , "3" <> subscript "{}"
                       , "4" <> superscript ("(a(" <> strong "b(c" <> ")d))")
                       ])
+      , "Verbatim text can contain equal signes (=)" =:
+          "=is_subst = True=" =?>
+          para (code "is_subst = True")
 
       , "Image" =:
           "[[./sunset.jpg]]" =?>
-- 
cgit v1.2.3