Compatibility with mylatex

[koppor]

There is mylatex (Source: mylatex.ltx) for ultrafast latex compilation.

However, mylatex does not work "well" together with markdown:

\documentclass{article}
\usepackage{markdown}
\begin{document}
test    
\end{document}

pdflatex --ini "&pdflatex" mylatex.ltx mwe.tex

(C:\MiKTeX\tex/latex/graphics\keyval.sty)
! Illegal parameter number in definition of \MYLATEXline.
<to be read again>
                   1
l.367   \gdef\FV@BeginScanning#1^^M
                                   {%
?

[koppor]

With mylatexformat (source: https://tex.stackexchange.com/a/687427/9075):

luahbtex -ini -jobname=mwe "&lualatex" mylatexformat.ltx mwe.tex

(C:/MiKTeX/tex/generic/markdown/markdown.tex
! Use of \??? doesn't match its definition.
<argument> \???
                 ! LaTeX Error: Access to an entry beyond an array's bounds.
l.357   { true }

[Witiko]

Interesting. Do you have any idea if this is a natural limitation of the approach used by mylatex and mylatexformat or if this is something that we can fix easily? I am happy to do the fixing but I am not too keen on learning about the implementation details of mylatex and mylatexformat.

[koppor]

Interesting. Do you have any idea if this is a natural limitation of the approach used by mylatex and mylatexformat or if this is something that we can fix easily?

I was hoping, you can see it with a quick look ^^.

https://github.com/davidcarlisle/dpctex/blob/ae3e67f71b6f25720d18ce66942780c5ffa3dbf8/mylatex/mylatex.ltx#L200

I assume, because \catcode is used, several packages break...

I am happy to do the fixing but I am not too keen on learning about the implementation details of mylatex and mylatexformat.

Since "lipsum" also doesn't work, I mailed to the luatex mailing list. Lets see, what happens.

[Witiko]

I was hoping, you can see it with a quick look ^^.

I am afraid you overestimate my ability to read low-level plain TeX / LaTeX2e. I wasn't even able to determine where mylatex.ltx actually executes \MYLATEXline after reading it.

That said, there is still a lot of low-level catcode magic in markdown.tex that is bound to confuse any naïve line scanner. I have been meaning to replace it with nicer expl3 code for some time now but it's been a low priority for me.