-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verbatim bugs #71
Comments
Note that it would be quite nice to review #39 at the same time for the release. |
OK, the problem is that in strings like this one:
The verbatim block is terminated by the This could be improved by requiring some kind of blank just before the terminator (which, I think, is what ocamldoc does). |
Btw, the change to better handle blanks at the beginning/end of verbatim block is exactly the same as the one needed for preformatted code blocks. And will be fixed at the same time. But not before the release. |
Yes |
The commit linked above fixes this. There is a new test, Line 366 in f973950
which checks that a correct comment AST is produced:
|
odoc
chokes ontopkg
's use of verbatims. @trefis thinks this is an octavius bug:The corresponding lines are
https://github.com/dbuenzli/topkg/blob/1bcd6ca66f81c7306ec424aa5b8988c4a39edb94/src/topkg.mli#L747
https://github.com/dbuenzli/topkg/blob/1bcd6ca66f81c7306ec424aa5b8988c4a39edb94/src/topkg.mli#L1956
Note that this breaks a significant part of
topkg
's documentation as it drops all the remaining sections of the docs which in turns breaks many internal links to them.Worked around by turning a few of these verbatims into code fences in dbuenzli/topkg@56c82f7
The text was updated successfully, but these errors were encountered: