Markdown Snippet Not Rendering Properly in Markrender v1.0.7 CLI Utility

[gneff]

This snippet of markdown from a file I was drafting doesn't render properly in the CLI utilty:

## Managing sudo Users
Users that are able to become root are managed by the
`/etc/sudoers.d/99-cyberinv-custom` file.  Don't fuck it up.  Use the
`visudo(8)` command if you have to.


## Managing PAM Config
TL;DR - Don't touch it!
pam-auth-update(8) will break the PAM config badly, because some of the
/etc/pam.d/* files are manually modified, so don't do it.

The good news is that pam-auth-update does backup the individual files before
changing them, so they can be fixed via a local admin account, but this is a
huge pain, so we're back to "Don't do it!"

If you have PAM concerns, then bring them up with myself (jschmoe) or Hector
(hramirez).


## Adding Groups to Who Can Login
These must be added in two places:
 * The `AllowGroups` line in `/etc/ssh/sshd_config`
 * The `ldap_access_filter` in `/etc/sssd/sssd.conf`
   Note: Editing this is a bit tedious.  It has to be all one line and it's
   parentheses hell.  Use the 'cyberinv-us' entry as a template:
   `(memberOf=cn=cyberinv-us,ou=Example Groups,dc=example,dc=com)`

I'm going to paste how it's re-ordering parts of the text (coloring and bullet point characters lost , of course):

$ markrender tools-admin-guide.md

Managing sudo Users
Users that are able to become root are managed by the
/etc/sudoers.d/99-cyberinv-custom file.  Don't fuck it up.  Use the visudo(8)
command if you have to.


Managing PAM Config

Adding Groups to Who Can Login
TL;DR - Don't touch it! pam-auth-update(8) will break the PAM config badly,
because some of the /etc/pam.d/* files are manually modified, so don't do it.
The good news is that pam-auth-update does backup the individual files before
changing them, so they can be fixed via a local admin account, but this is a
huge pain, so we're back to "Don't do it!" If you have PAM concerns, then bring
them up with myself (jschmoe) or Hector (hramirez). These must be added in two
places:

● The AllowGroups line in /etc/ssh/sshd_config
● The ldap_access_filter in /etc/sssd/sssd.conf    Note: Editing this is a bit
tedious.  It has to be all one line and it's    parentheses hell.  Use the
'cyberinv-us' entry as a template:
(memberOf=cn=cyberinv-us,ou=Example Groups,dc=example,dc=com)
$ markrender --version
markrender 1.0.7
$

Note now the text for the "Managing PAM Config" section is being rendered below the header for the "Adding Groups to Who Can Login" section.

Interestingly, your markdown-it utility seems to handle it correctly.

$ markdown-it tools-admin-guide.md
<h2>Managing sudo Users</h2>
<p>Users that are able to become root are managed by the
<code>/etc/sudoers.d/99-cyberinv-custom</code> file.  Don't fuck it up.  Use the
<code>visudo(8)</code> command if you have to.</p>
<h2>Managing PAM Config</h2>
<p>TL;DR - Don't touch it!
pam-auth-update(8) will break the PAM config badly, because some of the
/etc/pam.d/* files are manually modified, so don't do it.</p>
<p>The good news is that pam-auth-update does backup the individual files before
changing them, so they can be fixed via a local admin account, but this is a
huge pain, so we're back to "Don't do it!"</p>
<p>If you have PAM concerns, then bring them up with myself (jschmoe) or Hector
(hramirez).</p>
<h2>Adding Groups to Who Can Login</h2>
<p>These must be added in two places:</p>
<ul>
<li>The <code>AllowGroups</code> line in <code>/etc/ssh/sshd_config</code></li>
<li>The <code>ldap_access_filter</code> in <code>/etc/sssd/sssd.conf</code>
Note: Editing this is a bit tedious.  It has to be all one line and it's
parentheses hell.  Use the 'cyberinv-us' entry as a template:
<code>(memberOf=cn=cyberinv-us,ou=Example Groups,dc=example,dc=com)</code></li>
</ul>
$