Hisham Muhammad

@rboy1 is your LUA53.EXE in your PATH? It should have been auto-detected, so that `detected.lua_interpreter` would have been set in the line referenced by @siffiejoe .

@rboy1 what's the full output of `luarocks config`? (You might want to use a gist.github.com link to post the whole thing)

as for a workaround, you can try `luarocks config lua_interpreter LUA53.EXE` and `luarocks config variables.LUA c:\path\to\your\LUA53.EXE` to force the configuration values and avoid a misbehaving autodetection. Though I'd still like...

> It seems to find it but it's obviously not invoking it, does this look right? It's a bug in LuaRocks; the detection is correct but the `lua_interpreter` entry is...

This happens on all platforms... Yeah, I know it's not the best UX. LuaRocks needs a simple JSON library able to `json.encode` and `json.decode`, and we didn't want to pre-install...

@mpeterv and it's been in the master branch for a while... perhaps it's about time for a new release? Is anything currently holding us back? ( @Tieske , @ignacio ,...

> Can't we just include a simple pure-lua one in the LuaRocks installation? We could, but it gets me torn between "LR should be self-contained" and "shouldn't we start eating...

Yes, @siffiejoe, I had this in the back of my mind when I mentioned "picking a horse in the race-of-JSON-libraries". I'm not sure this is a problem per se, though....

@mpeterv Yes, I was about to make one but I slipped into other things. No need to wait for the Windows testsuite, I think (It's more important to get it...

That's a good idea! Indeed LuaRocks performs this detection internally, it would not be hard to make it print a message when a conflict is detected.