Fix interpolated selector match regression

[seven-phases-max]

Fixes #2216 (regression introduced with #1831, see also comments in #1877).

[lukeapage]

Thanks.
btw I just pushed another big change to the 2_0_0 branch that breaks some of the browser tests - will fix tomorrow, but I figured the sooner big changes get onto the branch the better.

getting close... ;) This change allows drop-in file managers

[lukeapage]

Oh did you get anywhere with a logger for warnings?

[seven-phases-max]

Oh did you get anywhere with a logger for warnings?

Nope :(

[lukeapage]

@seven-phases-max I've added a logger system (just have one final test to fix then will push). The idea is there is a logger that can be required (or got from less.logger) and by default it does nothing and the different implementations add listeners - this then means I can remove the silent and verbose options from the core. Not sure if that was what you had in mind, but it means the less core code is alot more tidy (and warnings can be made from anywhere)

[seven-phases-max]

@lukeapage Thanks. I hope I'll be able to get back to it next week or so. Yes, this logging system looks promising. In fact I do not have too much requirements in mind, just two:

• Warnings should be logged after the code when we compile to a shell console
• We don't want to pass a context (file/line) into every built-in function so ideally this should somehow be handled transparently.

(And additionally a warning list needs also be available somewhere after/at toCSS/render functions so that external tools could use it on their own).
All this is pretty trivial and I only stalled at the point of composing all that to be not so hardcoded for various environments (i.e. cli/node-lib/browser).