title: Fix Sublime Text 3 Clojure Syntax Highlighting (Regexes especially)
body: <p>Sublime Text 3's Clojure syntax highlighting often breaks on/after regular expressions. I see that Anthony Grimes noticed this on the Sublime Text Forum: <a href="http://sublimetext.userecho.com/topic/82983-clojure-regexes-are-not-parsed-properly/" rel="nofollow noreferrer">http://sublimetext.userecho.com/topic/82983-clojure-regexes-are-not-parsed-properly/</a></p>
  
  <p>This answer was suggested:</p>
  
  <blockquote>
    <p>Inside <code>Clojure.tmLanguage</code> try changing</p>
    
    <p><code>&lt;string&gt;source.regexp.oniguruma&lt;/string&gt;</code></p>
    
    <p>to </p>
    
    <p><code>&lt;string&gt;#string_escape&lt;/string&gt;</code></p>
  </blockquote>
  
  <p>But where is <code>Clojure.tmLanguage</code>? After I make the change, do I just save it in place? (See <a href="https://stackoverflow.com/questions/19790062/where-to-put-tmlanguage-in-sublime-text-3">Where to put .tmLanguage in sublime text 3?</a>)</p>
  
  <p>I see have this in my Sublime Text 3 directory:</p>
  
  <pre><code>$ tree -L 1
  .
  ├── Cache
  ├── Index
  ├── Installed\ Packages
  ├── Local
  └── Packages
  </code></pre>
  
  <p>Inside <code>Cache</code> I see <code>Clojure/Clojure.tmLanguage.cache</code> but that probably isn't right.</p>
  
  <p>Update: I'm using Mac OS X 10.9.</p>
  
  <p>Update: I'm looking over <a href="http://www.sublimetext.com/forum/viewtopic.php?f=2&amp;t=10933" rel="nofollow noreferrer"> Where are .tmLanguage files stored for ST3</a></p>
  
  <p>Update: There are other Clojure syntax issues detailed here, too: <a href="http://www.sublimetext.com/forum/viewtopic.php?f=3&amp;t=14077" rel="nofollow noreferrer">http://www.sublimetext.com/forum/viewtopic.php?f=3&amp;t=14077</a></p>
  
  <p>Update: I've tried uncompressing the <code>Clojure.tmLanguage.cache</code> file by renaming it to <code>Clojure.tmLanguage.zip</code> first. That was bizarre; I get an alternating and endless loop of <code>.cpgz</code> and <code>.zip</code> files as I try to uncompress them. See: discussions.apple.com/thread/1446784</p>