On Tue, Jan 31, 2012 at 02:48, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> >> However there are a lot of things that can go wrong when you work withThat would be perfect, yes. Patch welcome,
>> >> things like css.
>> > I don't think it should be the job of CSS mode to highlight ad-hoc
>> > mistake conditions like that.
>> There's cwarn-mode for something similar, so the question really is
>> whether this error is common or specific to a particular user.
>> I have no idea which it is.
> The "!important" is colored as it is now even when I happen to put it
> after the ";". Not syntax coloring that would be enough to easily
> detect the problem.