add the variable env to css scope

[kadkaz]

For some styles to apply I need to know is it prod or test execution.

Real scenario:
right now I necessary to have to files
index.css
indextest.css

with @mode = normal
and @mode = test

.rotate(test, @Angle) {
//nothing
}

.rotate(normal, @Angle) {
content: @mode;
-moz-transform: rotate(@Angle);
-webkit-transform: rotate(@Angle);
-o-transform: rotate(@Angle);
}

.rotate(@Angle) {
.rotate(@mode, @Angle);
}

and there is another hack for auto selenium testing, cause FF transforms bad (DOM disappeared and selenium could not find it)

But I hope the real scenario does not scary you and it can be useful for any other scenario.

and it will be great to have the variables from request too, not only from script.
I mean:
script src="js/less.js?env=test" type="text/javascript"></script

[lukeapage]

is this relevant for how to pass variables to a script... #1131

then you can use mixin guards (http://lesscss.org/#-pattern-matching-and-guard-expressions) to change which mixins get used (or use the variables directly in content).

when posting code, use a tab/4 spaces indentation in order to tell guthub its code. Or use backticks around code. Then you won't notify @angle and @mode

[jonschlinkert]

Could this be accomplished with #1134?

[matthew-dean]

@jonschlinkert I agree, switching testing / dev modes is better handled via options (whether it ends up being a config file or within the library).