> I've tried pprint and found it lacking as it inserts newlines in > awkward places apart from the medatada/comments issue mentioned.
Are you using pprint with code-dispatch? That tends to work a lot better, though it will put newlines where it deems fit. This is either a good thing or a bad thing depending your context. It also handles all the read macros that it can: (with-pprint-dispatch code-dispatch (pprint '#(+ % 1) )) => #(+ % 1) But some get eaten by the reader and are therefore impossible for pprint to deal with (since it's working on clojure data structures and not the raw text). These are: `, ~@, ;, ^, and the comma character. > I think your best bet is to use Emacs from the command-line. Even if I agree that when you're just trying to reindent human written source code, emacs is going to produce the best results. pprint is probably better for machine generated code, as long as you're not depending on the macros above. (It would also be possible to annotate your code in clojure with that and have some custom dispatch that generated those characters as appropriate.) HTH, Tom -- 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
