Inserting a quote can cause loss of information about parinfer.js

[shaunlebron]

We can fix this by not removing unmatched delimiters. I think this solves the problem completely for single line strings, because delimiters are then only removed when they fall at the end of a line. And by definition of a single string, the contents of the string will always end with a quote, preventing its removal.

This doesn't help multiline strings:

(def foo

  "(a b)
      c")

Inserting two quotes on the second line results in this:

(def foo
  ""
  "(a b
      c")

So I think the true solution is to just hold prevent processing if there is an unmatched quote anywhere in the file.

[shaunlebron]

Another breaking bug caused by quotes in comments being overtaken by strings:

Steps to recreate. Delete the quote at the end of line 2, and reinsert it.

(def foo
  ""
  "(a b)
      c" ;; "
   c)

You will get this:

(def foo
  ""
  "(a b
      c" ;; ")
   c)

[shaunlebron]

crazy idea: detect if there are an even number of unescaped quotes in a string. if there aren't, escape the last one so that an imbalanced string state will be guaranteed to pass through it.

with all these crazy cases coming up, maybe parinfer should just be isolated to a "restructure selection by indentation" function in an editor.

[shaunlebron]

escaping quotes in comments was a bad idea, we can't quickly comment/uncomment a line of code with a string in it.

I will just make a note that strings must be balanced in comments