Multiple bugs related to comment grammar

[Xeverous]

Example 1:

- item A
- item B

...text after triple dot

Expected: elements are recognized as a list and text block.

Actual: the entire paragraphs that starts with ... is treated as a comment, which is just wrong.

Example 2:

- list item A
- list item B

..

    indented text

text

Actual: indented text is highlighted as a comment, which is incorrect. .. is used intentionally here to end the list, otherwise intended text would be treated as a subelement of the list item B. Such use of .. is even presented in reST examples.

---

Edit: I will try to post more examples if I encounter something reproducible, but so far I can say everything I have seen gone wrong was related to parsing of ...

[trond-snekvik]

Hi, perhaps I'm misunderstanding what you would consider the expected behavior, but I'm not able to reproduce these examples:

Would you be able to provide a screenshot of the issue?

[Xeverous]

VSC Help -> About:

Version: 1.62.3 (system setup)
Commit: ccbaa2d27e38e5afa3e5c21c1c7bef4657064247
Date: 2021-11-17T08:11:14.551Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 6.1.7601

[trond-snekvik]

Thanks! Which version of the extension do you have installed, and do you have any other extensions that would affect rst files?

[Xeverous]

v1.5.1

other reST extensions:

• reStructuredText v167.0.0 (from LeXtudio)

[trond-snekvik]

Thanks, I was able to reproduce this, and made a fix in #26, but this introduces a new issue where all blank lines in comments terminate the comment block, which isn't correct. I'll work on it some more, but if you want to test it, you can find the .vsix as a build artifact in that PR

[trond-snekvik]

Sorry for the crazy long delay on this. I was able to resolve the issues I were seeing, and with the help of the test framework contributed in #34, I've added a couple of test cases that covers this scenario.

I have merged the fix, and will make a new release on the marketplace.