inspect.lua VS luacheck

inspect and strong

I've used inspect.lua to inspect the client table and I can see valid-looking formatCommand settings (using the exact efm folder that u/lukas-reineke uses)

For more complex string matching tasks that the built-in patterns cannot handle, LPeg is a good choice. It's more powerful than regexes while also being easy to use. I also wouldn't expect something like PCRE to ever be included in the Lua standard library. PCRE by itself would already be larger than the rest of the Lua interpreter + standard library.

By the way, for formatting Lua tables I like using inspect[1]. (It's not part of the standard library but oh well, that's the whole topic of today's discussion).

https://github.com/kikito/inspect.lua

Luacheck is now maintained by lunarmodules.

I first started by reading some tutorials but most of those used parser combinators. For me, parser combinators always caused some issues sooner or later (at least in Lua when trying to parse recursive / nested nodes). An example project that uses this technique is vim-vsnip: https://github.com/hrsh7th/vim-vsnip/blob/master/autoload/vsnip/snippet/parser.vim. Later, I found out that Luacheck uses a different approach which I liked better: https://github.com/lunarmodules/luacheck/blob/master/src/luacheck/parser.lua. That's the project that helped me the most while writing my own parsers for different snippet engines.

I'm just a contributor to Gabe, but I use luacheck in my other projects. Install it (with hererocks+luarocks on Win and luarocks elsewhere), set it up in your editor, and you'll get warnings about typos and other potential bugs. luacheckrc lets you configure it: turn off warnings you don't care about, customize it for different files.

Use luacheck to find all global and unused variables in your project.

I’m not really really sure what exactly you’re relying on that is so specific to Python, but Lu’s appears to have a static analysis linter. https://github.com/luarocks/luacheck