On Aug 8, 2013, at 5:44 AM, Lee Spector <lspec...@hampshire.edu> wrote:
> Agreed. But good brace/paren *matching* (highlighting the mate and/or > unmatched brackets) solves this problem without all the downsides (IMHO) of > paredit. I too had a similar experience. Often when writing code I don't even produce it in the LISP form but more like a freehand drawing, and then, if the idea turned out to be valid, correct the syntax and put in the parenthesis. Paren matching helps me to do it without any effort by showing which parens are complimentary and, more importantly, without getting in the way. Having said that, paredit can be a great tool depending on your editing habits. One should definitely try it to see if it works for him, but saying it is a panacea for balancing parens/braces is a bit for stretch as other tools solve this problem as well. -- ST4096-RIPE -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
