Feature request: disable parinfer on files with git conflicts

[timgilbert]

I've found that when files have a git conflict, so that there are tons of lines like this in the file:

(defn foo []
  (println "hello")
<<<<<<< HEAD
  (bar))
=======
  (baz))
>>>>>>> my awesome commit message

...parinfer tends to get very confused by the indentation, and it wreaks havoc on my parentheses. Often just removing the offending lines doesn't fix the problem since the parens have already been changed in such a way that they balance differently.

This isn't a huge deal, but it's an annoyance. One thing that I think would be helpful as a workaround would be for Cursive to turn off parinfer for a file if the file had unresolved conflicts.

[oakmac]

This is a good idea. I might need to borrow it for atom-parinfer ;)