-
Notifications
You must be signed in to change notification settings - Fork 453
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
Update GitHub syntax high-light for Lean 4 #377
Comments
The syntax highlighting is taken from the vscode-lean extension: We should probably make a new syntax highlighting grammar that works for both Lean 3 and Lean 4, and then have github switch to that. |
https://github.com/github/linguist is responsible for the highlighting on github. I think the best way to do this would be:
|
Although we may run into trouble with:
|
…nprover#377) It seems that Lean 4's `dsimp` has gotten closer to parity with Lean 3's `dsimp` since this code landed. Compare to the mathlib3 version of `injective.dite` here: https://github.com/leanprover-community/mathlib/blob/f089486a9af40d019f9ecf7d86a055eb2801124b/src/logic/function/basic.lean#L114-L126
I did this in github-linguist/linguist#6616 |
@eric-wieser Nice! I put this on hold because I wanted to do an improvement pass on the vscode-lean4 textmate grammar first, but wasn't aware that linguist references the repository itself, and so there is no need to improve the grammar before the corresponding linguist PR. |
github-linguist/linguist#6616 is now merged! |
Does this mean we can close this issue? |
The linguist release should be tomorrow; so hopefully we'll see if it worked by the end of the week |
https://gist.github.com/eric-wieser/b41f0125324b0ba767da53e6bfdaa357 suggests this is working as intended; now we have the long tail of improving the grammar in places where it looks bad on github (since elsewhere we normally rely on the semantic highlighting anyway) I think this issue can be closed as completed! |
@Kha @gebner Do you know where we have to add the new keywords?
I did it once, but I forgot where we should add them.
The text was updated successfully, but these errors were encountered: