search

stsewd / tree-sitter-rst

reStructuredText grammar for tree-sitter
https://stsewd.dev/tree-sitter-rst/
MIT License
50 stars 7 forks source link

Correctly parse sections with a numeric bullet like text #35

Closed stsewd closed 2 years ago

stsewd commented 2 years ago

Fixes https://github.com/stsewd/tree-sitter-rst/issues/30 Fixes https://github.com/stsewd/tree-sitter-rst/issues/32 Closes https://github.com/stsewd/tree-sitter-rst/pull/33

stsewd commented 2 years ago

@Carreau I'm able to parse your two examples correctly with this change, let me know if you have other examples related to this problem that I could test

Documenting C/C++ Code
======================

NumPy uses Doxygen to parse specially-formatted C/C++ comment blocks. This generates
XML files, which are  converted by Breathe into RST, which is used by Sphinx.

1. Writing the comment blocks
-----------------------------

Although there is still no commenting style set to follow, the Javadoc
is more preferable than the others due to the similarities with the current
existing non-indexed comment blocks.
(document [0, 0] - [12, 0]
  (section [0, 0] - [1, 22]
    (title [0, 0] - [0, 22]))
  (paragraph [3, 0] - [4, 77])
  (section [6, 0] - [7, 29]
    (title [6, 0] - [6, 29]))
  (paragraph [9, 0] - [11, 36]))
This

2) Intrinsic NumPy array creation functions
===========================================
..
  40 functions seems like a small number, but the routies.array-creation
  has ~47. I'm sure there are more. 
(document [0, 0] - [7, 0]
  (paragraph [0, 0] - [0, 4])
  (section [2, 0] - [3, 43]
    (title [2, 0] - [2, 43]))
  (comment [4, 0] - [6, 35]))
Carreau commented 2 years ago

If that works on the example in the issues, then that suits me. I'll try to report more in depth and with links to failing items when I encounter more.

Thanks again for all your work on this, I'm slowly understanding the internals.