Fix: Unsupported marker content in checkboxes

[micsama]

This PR addresses an issue where unsupported markers inside [ ] brackets in checkboxes cause errors during rendering, which prevents the Markdown from being displayed correctly.

Problem Details:

When opening a Markdown file containing unsupported checkbox content, an error occurs, leading to a failure in rendering the Markdown. The error message observed is:

Error executing Lua callback: ...al/share/nvim/lazy/markview.nvim/Lua/markview/parser.Lua:658: invalid capture index
Stack traceback:
c: in function 'find'

This fix is crucial because the error prevents proper rendering of Markdown files containing these specific checkbox markers. By addressing this issue, the plugin will provide a more robust and error-free experience when working with checkboxes, ensuring that users can render their Markdown content correctly without interruption.

I would like to thank the author for this great plugin. I really enjoy using it, and I appreciate all the hard work that has gone into making it so helpful!

[OXY2DEV]

unsupported markers inside [ ].

There shouldn't be any unsupported markers. When did the error occur?

[micsama]

unsupported markers inside [ ].

There shouldn't be any unsupported markers. When did the error occur?

I open a file with marker like '[1]', although I realize this might be an incorrect marker. If the plugin encounters this marker, it could cause issues and won't work. Therefore, we
should add an error-checking mechanism here to inform the user if there is a problem.

[OXY2DEV]

Ah, I found the issue.

I was doing %1, a bit of an oversight on my part.

---

I unfortunately can't merge this, as I have reworked a bit how list items work.

So, the code looks a bit different now(check dev branch).

Also parser.escape_string() is now used to fix this issue as this doesn't cause an error and doesn't stop users from using numbers for special checkboxes.

Thanks for the PR!

[micsama]

Ah, I found the issue.

I was doing %1, a bit of an oversight on my part.

I unfortunately can't merge this, as I have reworked a bit how list items work.

So, the code looks a bit different now(check dev branch).

Also parser.escape_string() is now used to fix this issue as this doesn't cause an error and doesn't stop users from using numbers for special checkboxes.

Thanks for the PR!

okey, I'll check dev branch ,and try it