-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
M (MUMPS) syntax highlighting doesn't work in Markdown #1468
Comments
Or is it markdown engine issue? |
The lexer for M is the same as for Common Lisp. So if you use lisp as keyword it will work: set cna = ##class(CNA.CNA).%New("путь к libcna") ; Создаем объект класса CNA.CNA. В аргументах указываем путь к libcna.dll или libcna.so
do cna.LoadLibrary("путь к libtest") ; Загружаем библиотеку libtest в CNA @arfon If we add |
@pchaigno I'm pretty sure the |
This wouldn't have any effect on the markdown rendering. I'm not really sure why it's not working properly in markdown. :( |
I imagine that Linguist uses the alias for the lexers from Pygments as the source for the keywords to use in the mardown rendering. Since M doesn't have a lexer it doesn't work. We would need to explicitly define somewhere |
@bkeepers I think it's an issue for the GitHub repository which renders Markdown documents. Would it be possible to open it there and close this one? |
This is actually an issue with the SyntaxHighlightFilter in html-pipeline, which does not use linguist to determine which lexer to use. |
I opened two issues at jch/html-pipeline to solve this: gjtorikian/html-pipeline#152 and gjtorikian/html-pipeline#153. |
This is the test repo:
https://github.com/daugeldauge/mtest
As your see, MUMPS syntax highlighting works fine in the source file. But it doesn't work in README.md. Neither with
M
keyword nor withmumps
.The text was updated successfully, but these errors were encountered: