Inline 'std' directive not obeyed about luacheck HOT 5 CLOSED

Yes, right now inline options can be used only to remove some warnings, but not to re-add warnings removed by default. I'm not sure what's expected behaviour when std is used both inline and as an argument/in config. Probably sets of globals should be joined in that case.

from luacheck.

My expectation is that std has a set of values (none, min, max, etc.), and I expected std to be 'none' for this file, and override what was specified on the command line (or the default). Other files in the same run would be handled using the default std value.

If it helps, the root problem we are trying to solve is that luacheck does not detect:

_ENV = nil
print("hello world")

I expected that this would fix that:

--luacheck: std none
_ENV = nil
print("hello world")

from luacheck.

The goal here is to point to a line and say "Any use of a global variable below this line is an error", such as with the common pattern of putting everything you are going to use into locals at the top of the file.

from luacheck.

This should be fixed on master branch, sorry to have kept you waiting. Can you test it?

from luacheck.

Late, but yes, it seems to work. Thanks!

from luacheck.