Code block inside list not rendered as <pre> if containing lines starting with +, - or *

[dynamind]

In Hugo 0.14/0.15 I noticed that code blocks are not rendered correctly if they contain lines starting with +, - or * and are nested inside a list.

Example:

1. Some list item

    ```plain
    + this doesn't work
    ```

The generated HTML is:

<ol>
    <li><p>Some list item</p>
    <p>```plain</p>
    <ul>
        <li>this doesn&rsquo;t work
        ```</li>
    </ul></li>
</ol>

Removing or replacing the offending character, prepending 4 spaces, or taking the block out of the list solves it.

[moorereason]

This is not a bug. According to the Markdown spec:

To put a code block within a list item, the code block needs to be indented twice — 8 spaces or two tabs.

[dynamind]

I'm afraid you're referring to the standard syntax. The bug is in fenced code blocks, which allow us to specify the language (for client-side highlighting).

See also: https://gohugo.io/extras/highlighting/#using-client-side-highlighting

[moorereason]

My mistake. This looks like a bug in Blackfriday.

[bep]

What is the reference to the Blackfriday issue?

[moorereason]

Reported upstream as blackfriday #239.

[bep]

This issue has been automatically marked as stale because it has not been commented on for at least four months.

The resources of the Hugo team are limited, and so we are asking for your help.

If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, and you feel that it is still valuable, please open a proposal at https://discuss.gohugo.io/.

This issue will automatically be closed in four months if no further activity occurs. Thank you for all your contributions.

[bep]

Note/Update: This issue is marked as stale, and I may have said something earlier about "opening a thread on the discussion forum". Please don't.

If this is a bug and you can still reproduce this error on the latest release or the master branch, please reply with all of the information you have about it in order to keep the issue open.

If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[kaushalmodi]

I can understand that this is not a Hugo problem. But it would be really awesome if the Go experts here can fix this problem in the Blackfriday repo. I've been noticing for quite a few months that that project is not in a very healthy development state.. This issue has been opened since 2 years, and no one in that team bothers to fix it!

[moorereason]

@kaushalmodi,
I understand, but please don't complain about how we (or the Bf team) choose to volunteer our time. No one is getting paid for this. If you're not willing to fix it yourself, it's better to keep your complaints to yourself. None of us likes having unfixed bugs, but there's only so many hours in the day and too few contributors willing to take those hours away from their families (or whatever) and donate them to you guys.

[kaushalmodi]

I am a heavy open-source contributor too. Sorry, I'm just feeling helpless here as I don't know Go.. and I fear the impact that the lack of maintenance on Bf project will have on Hugo.. that's all.

and donate them to you guys.

Just to clarify, I am not one of "you guys". I contribute a lot of my free time to open source projects, actively contributing, helping folks, etc.

That said, I won't talk about this in Hugo issues any more.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. The resources of the Hugo team are limited, and so we are asking for your help.
If this is a bug and you can still reproduce this error on the master branch, please reply with all of the information you have about it in order to keep the issue open.
If this is a feature request, and you feel that it is still relevant and valuable, please tell us why.
This issue will automatically be closed in the near future if no further activity occurs. Thank you for all your contributions.

[moorereason]

This has been fixed upstream.

[kaushalmodi]

@moorereason Awesome! Though, shouldn't this be closed after the Blackfriday ref is updated? (or does that happen automatically now?)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.