-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
There's always three lines for every function #276
Comments
I believe at least the HTML comment (the first of the two lines) is used for parsing the stan-functions.txt which is consumed by emacs stan-mode #180 and I believe also rstudio stan-dev/stan#2740 I am not sure about the second line though. |
Ooops, I need to add the html ones back to the ode functions then |
hi @bbbales2 (can I call you b3n? b3n2?). these are great questions which need to be documented somewhere - like a wiki page on "all the hacks that go into the docset" - line 1 is used by script https://github.com/stan-dev/docs/blob/master/extract_function_sigs.py line 2 is used by Latex so that the pdf version of the docs has an index. they are both entirely very necessary. |
(maybe you know this) - the hack here is that when rendering pdfs via Latex, html directives are ignored, and when rendering html pages via bookdown, latex directives are ignored. so the Rmd files are cluttered up w/ crap. when I converted the latex version of the functions ref manual to Rmd, I somehow generated the HTML comments from the Latex index directives via Python scripts. I think I could do something similar again to get the _lupmf entries. |
Oooo, alright, makes sense. I did not know this. |
Added back html for ode docs (Issue #276)
Summary:
This line renders:
And that's great.
Do these two lines do anything? How do I know I've done them right? Can I delete them?
Current Version:
v2.24.0
The text was updated successfully, but these errors were encountered: