-
Notifications
You must be signed in to change notification settings - Fork 62
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
Not compatible with lpeg version 0.11-2 #8
Comments
This should be fixed in lpeg 0.12. From the lpeg
|
I am afraid it is not compatible with lpeg 0.12 either :( fails with: loop body may accept empty string |
I believe that this was an error with cosmo and was fixed with this issue mascarenhas/cosmo#6 |
I still have the same issue. sudo luarocks install lpeg luajit: loop body may accept empty string |
I've been working on a fix for this. When I get time, I'll try to wrap up a patch. |
@craigbarnes Any indication when this will be fixed? Thanks in advance. :) |
@mauvm All I can say is "when I get time". As a small pointer -- if you change line 893 of (Blank^0 / function() return writer.interblocksep end * Block)^-0 * to: (Blank^0 / function() return writer.interblocksep end * Block)^-40 * ...and run This is not a real solution at all, since it makes the |
@craigbarnes Thanks for the quick response! Unfortunately the suggested "fix" does not work for me. I can't really figure out why, except that the code I have does not have the negation sign:
I have tried
To me it looks like a problem in the regexp in Also I'm quite new to Lua/LuaRocks and am not really sure where to run the |
Yes, sorry, I forgot to mention that. I'm using cosmo from git master, where compatibility with LPeg 0.12 is already fixed. If you install the latest cosmo from the git repository, the error in Lunamark should cascade down to the line I mentioned. The
|
Investigated this a little because this bug annoys me. The issue is apparently I have no idea how this capture should be fixed though, this is as far as my current LPEG-fu gets. |
Quick addition
After downgrading to lpeg |
I'd like to think we can close this issue. lpeg 0.11 was a buggy release. |
Confirmed, lapis 1.5.0 pulled in lpeg 1.0 and lunamark 0.4 reused it?, basically everything works fine. |
This closes jgm#8.
I installed lunamark (version 0.3-1) using luarocks on OS X, which installs lpeg version 0.11-2 to solve dependency. When run lunamark, I got the following error:
I manually installed lpeg version 0.10-2 and then lunamark works.
The text was updated successfully, but these errors were encountered: