[tex-live] Possible lacheck Bug Report

Zayd Hammoudeh hammoudeh at gmail.com
Sat Jan 26 01:03:44 CET 2019

Hi Karl,


Is the source code for lacheck available in a repository?  I looked around but did not find it.  I am not familiar enough with CTAN to have intelligent thoughts on where to look.  I would be open to looking into it and possibly issuing a pull request if that were an option.






From: Karl Berry <karl at freefriends.org>
Date: Friday, January 25, 2019 at 3:43 PM
To: <hammoudeh at gmail.com>
Cc: <tex-live at tug.org>
Subject: Re: [tex-live] Possible lacheck Bug Report




    I read on the CTAN website that TeXLive is now maintaining lacheck.


Unfortunately true, since no other volunteers have come forward since

the original author(s) stepped down.  If anyone is interested, please

write me.




    "hw01.tex", line 5: <- unmatched "end of file hw01.tex"

    "hw01.tex", line 2: -> unmatched "{"


It's certainly a bug. 


    when \newcommand is followed by {\def*} (where * is zero or more other

    characters). Removal of the curly brackets around \def* or any term

    other than def causes the issue to go away.


I believe it comes from this line in lacheck.l:


"\\"[exg]?(def|newcommand)[^\n\{]+    BEGIN(DEF);


which I believe says a "definition" starts whenever \def followed by

something that is not a newline or left brace, which is clearly not the

case. It seems the \newcommand and \[exg]def cases should be separated

and made more precise.


So, if anyone is interested in playing around with the lex file, let me

know. Else I'll give it a try when I have a chance.


Thanks for the report. -k


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://tug.org/pipermail/tex-live/attachments/20190125/733c7d2e/attachment.html>

More information about the tex-live mailing list