<blockquote>
<p>I agree with <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=793526" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/b4n">@b4n</a> the current implementation isn't the best</p>
</blockquote>
<p>Ok, your example is fairly pathological, its not likely in real documents (not impossible, but not likely), and quite frankly the parser breaks way too often on real documents before something like that needs to be worried about (I can say that since I wrote it)  Examples like mine with repeated headings in different sections are common but work ok.</p>
<blockquote>
<p>but I'd prefer not introducing a diff in Geany now and rather fix it upstream.</p>
</blockquote>
<p>Totally agree, the whole point of the exercise is to align with upstream, so lets get to that point (for those parsers where we can eg not c.c) so things get easier.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/geany/geany/pull/2019#issuecomment-449187684">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ABDrJ08gjuFDDGA-LkSZCHrtaFr6YhX1ks5u7CxugaJpZM4ZXxvS">mute the thread</a>.<img src="https://github.com/notifications/beacon/ABDrJy6leZWBRY2EA5kv2EUmDqYm-OLZks5u7CxugaJpZM4ZXxvS.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/geany/geany","title":"geany/geany","subtitle":"GitHub repository","main_image_url":"https://github.githubassets.com/images/email/message_cards/header.png","avatar_image_url":"https://github.githubassets.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/geany/geany"}},"updates":{"snippets":[{"icon":"PERSON","message":"@elextr in #2019: \u003e I agree with @b4n the current implementation isn't the best\r\n\r\nOk, your example is fairly pathological, its not likely in real documents (not impossible, but not likely), and quite frankly the parser breaks way too often on real documents before something like that needs to be worried about (I can say that since I wrote it)  Examples like mine with repeated headings in different sections are common but work ok.\r\n\r\n\u003e but I'd prefer not introducing a diff in Geany now and rather fix it upstream.\r\n\r\nTotally agree, the whole point of the exercise is to align with upstream, so lets get to that point (for those parsers where we can eg not c.c) so things get easier.  "}],"action":{"name":"View Pull Request","url":"https://github.com/geany/geany/pull/2019#issuecomment-449187684"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/geany/geany/pull/2019#issuecomment-449187684",
"url": "https://github.com/geany/geany/pull/2019#issuecomment-449187684",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>