Im using sublime to edit html5 docs. But when I started to do quote-free editing like:
<div id=asdf>
instead of
<div id="asdf">
its syntax highlight gone crazy.

Any ideas how to solve this? Is there other up to date parser for sublime?
ty
This Sublime Text thread suggests a way to fix it: http://www.sublimetext.com/forum/viewtopic.php?f=3&t=8129
Open up your HTML.tmLanguage (in ~/.config/sublime-text-2/Packages/HTML) and look for this:
<string>(?<='|")</string>
<key>name</key>
<string>meta.attribute-with-value.id.html</string>
Change the first line to
<string>(?<==|='|=")</string>
Your unquoted values won't be highlighted in the same way that quoted values are highlighted, but it will at least prevent the syntax highlighting from completely breaking.
Quote free html is not a good idea. I recommend you to use quotes. The bytes you will save are not worth the aggravation is going to cost you.
There's no reason to consider it a bad idea. It's about as bad as not requiring ';' after statements, often it's great. Python is considered "not a bad idea" by most. If you're not an idiot you'll never do it wrong, it's dead simple - Lodewijk 2013-07-25 20:14
I have to go with Dbugger on this one. I feel compelled not to assist in helping you configure Sublime to "not report" bad HTML practices. With that said, the answer to your question is- typing in the quotations will eliminate the weird highlighting in Sublime.
XAML: "The attribute name is followed by an assignment operator (=). The attribute value must be a string enclosed within quotes."
XML: "Rule Three - All XML attributes must have quotes around them"
XHTML: "Here are some examples of XHTML rules:... All XHTML attribute values must be quoted. "
HTML5: "Just like in HTML, there are cases where the quotes around the attribute value can be omitted, but doing it blindly will likely result in broken code: - Josh Campbell 2012-10-29 23:02