Michal Suchánek

So this is not compatible with `lcov`? I create my report with ``` lcov --capture --base $(pwd) --no-external --directory . --output-file coverage.info ``` and get NaNs in the output.

And apparently when multiple captures are merged the LH/LF records are generated, and merging an initial capture with a test capture is needed to get any usable data at all.

Which they aren't if you build both the base branch and the current branch because there is no way to store and access the base branch data, and you cannot...

On 20 March 2013 20:55, rkumar [email protected] wrote: > Is there any way to merge individual changes one by one, and not the whole > lot ? I've merged these,...

It does work without `--std min` It's not clear these two should interact in any way. `--std min` is about the base library provided by the interpreter, and `files["/tests//*_spec.lua"].std =...

> Default per-path std overrides > luacheck uses a set of default per-path overrides: > ``` files["**/spec/**/*_spec.lua"].std = "+busted" files["**/test/**/*_spec.lua"].std = "+busted" files["**/tests/**/*_spec.lua"].std = "+busted" files["**/*.rockspec"].std = "+rockspec" files["**/*.luacheckrc"].std =...

No, setting the standard in `.luacheckrc` works fine. That however means that that the std option behaves differently between commandline and config file.

That's because you are aware of implementation details of the tool and know it's difficult or even impossible to override the default path rules from the commandline, and that gives...

BTW can users use this +something syntax for their own path overrides? I can't find that documented anywhere either.

Nevermind, the there is a notice about leading + in https://luacheck.readthedocs.io/en/stable/cli.html#sets-of-standard-globals