Me too!<p>And I already wanted to learn Lisp. Because I kind of half-assumed this tool to be there already :-P<p>I always assumed, obviously Lisp didn&#x27;t get this popular if people had to keep track of all their parentheses. Sure they probably had to in &quot;the old days&quot; (although I wonder even when?). It just seems like a tedious thing to have to do in order to work with such a consistently structured language.<p>Of course you can get most of it with highlighting matching parens and auto-formatting shortcuts. Like most languages.<p>But I kind of expected Lisp tooling to go the extra mile. Because it is <i>that</i> structured.<p>From my limited knowledge of Lisp, I figured some vague ideas on how such a tool would work &#x2F; should be designed. It&#x27;s kind of cool to see that the author&#x27;s initial steps match up with that idea: define a grammar, some invariants, and &quot;have at it&quot; (ok, so I didn&#x27;t figure that far). And then he made it work!<p>Maybe a silly question, but since the author is in this thread: Was it hard to make? :-)<p>BTW the idea of switching between these two modes is a very clever approach to keeping certain invariants invariant while still being able to modify the code--because the trivial way to preserve the invariant would be the tool immediately reverting your edit :)