title: Why were the new JSLint errors "use spaces, not tabs" and "unsafe character" introduced?
body: <p>I have been validating my JavaScript using JSLint for about 2 years now and once in a while there are rules that change. In general when JSLint introduces a new rule, there is a checkbox to ignore this rule when parsing, or if you choose to not ignore it then to make your code compliant to it.</p>
  <p>As I was running my JSLint validation today, however, I run into these two new errors:</p>
  <blockquote>
  <p>Use spaces, not tabs.</p>
  </blockquote>
  <p>This is not the &quot;mixing of tabs and spaces&quot; error. I am using only tabs. This is a recently modified version of &quot;mixing of tabs and spaces&quot; which now disallows tabs in general.</p>
  <p>And:</p>
  <blockquote>
  <p>Unsafe character.</p>
  <p>*/</p>
  <p>Unsafe character.</p>
  <p>_const: {</p>
  </blockquote>
  <p>There are no new options to ignore. I cannot understand what is unsafe about closing a block comment, why it considers _const: { as unsafe when I have <code>nomen: true</code>, (dangling _ in identifiers) or why should I be suddenly switching from spaces to tabs, when I still have the configuration about indentation of 4 spaces being a tab.</p>
  <p>Does anyone have an idea why those were introduced to at least how to make JSLint ignore these new rules?</p>
  <p><strong>Update:</strong>
  The <em><code>Messy White Space</code></em> option works around the issue but it would cause other unexpected behavior:</p>
  <pre><code>if (condition) { 
    //            ^-- there is a space but it won't indicate an error
  </code></pre>