You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should find ways to discourage using ad-hoc ways of putting math in the documentation and encourage using the $ ... $ and $$ ... $$ notation.
Here are some ideas:
We could have more strict requirements when reviewing pull requests, but we should make this easy on the reviewer. For instance, GitHub actions could automatically uploaded the generated documentation somewhere easy to view.
As a heuristic, we could have the documentation system temporarily give an error for symbols like ^ and _ or + and * in the text sections of every node and use those to identify a list of nodes that need fixing.
Tangentially, it would be great if M2-mode could replace strings wrapped in $ .. $ with rudimentary tex, but this may be nontrivial.
The text was updated successfully, but these errors were encountered:
We should find ways to discourage using ad-hoc ways of putting math in the documentation and encourage using the
$ ... $
and$$ ... $$
notation.Here are some ideas:
^
and_
or+
and*
in the text sections of every node and use those to identify a list of nodes that need fixing.Tangentially, it would be great if M2-mode could replace strings wrapped in
$ .. $
with rudimentary tex, but this may be nontrivial.The text was updated successfully, but these errors were encountered: