-
Notifications
You must be signed in to change notification settings - Fork 60
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
fix #467, "docstring oddities #662
Conversation
Perl command: perl -i -p -e 'BEGIN{undef $/;} s/"""\n (\S)/"""\n \1/smg' $(find -name \*\.jl)
Perl command: perl -i -p -e 'BEGIN{undef $/;} s/"""\n (\S.*)\n>/"""\n \1\n\n>/g' $(find -name \*\.jl)
Perl commands: perl -i -p -e 's/^> (.+)/\1/g' $(find -name \*\.jl) perl -i -p -e 's/^>$//g' $(find -name \*\.jl)
Looks like this causes the docs to stop building. See the documentation test on travis. |
On Mon, Oct 26, 2020 at 03:15:51PM -0700, wbhart wrote:
Looks like this causes the docs to stop building. See the documentation test on travis.
Not helpful, but looks like an error in documenter
…
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#662 (comment)
|
Yes... I force-pushed on another PR to check if the build still passes there. |
A painfully boring bisection allowed to find the problem, a |
The julia markdown parser is very brittle when it comes to |
There is also this issue: JuliaDocs/Documenter.jl#1020 |
Thee commits (which make it easier to review, so github highlights the parts which changed)
>
characters at the beginning of lines in docstrings.I used Perl commands (included in the commit messages), so this limit the chance for human errors, but I'm not expert in regexes either... I also reviewed "manually", and this seems to have done what was expected.