2011/5/22 mike.w.me...@gmail.com <m...@mired.org>: > Lee Spector <lspec...@hampshire.edu> wrote: >>If I understand correctly you're suggesting that a user working with an >>editor and a REPL, which aren't connected > > That being the mimimal configuration that I think of as "useabe". >> , run something in the REPL to see the structure of the code. > >>Not un-useful, but of course the user >>will probably want the code in the editor to reflect that structure, >>which will require either manual matching of what they see in the REPL, >>or cut/paste, or the kind of overwrite functionality that you describe > > This is a *different* problem than the one being solved, which is getting an > accurate representation of the structure of the code. In particular, it's > different enough that I don't think it makes the required list for a minimal > "getting started with clojure" package. So it'd be nice to offer, but it > being missing or a bit painfull isn't a show-stopper. > >>(which might then confuse JEdit, if you're overwriting a file out from >>under it). I don't think I'm insisting that the solution has to be the >>one that I'm used to, but none of these sound like great options while >>the decades-old in-editor-reindentation approach seems to be viable and >>time-tested. > > I'd be surprised if stand-alone code beautifiers weren't decades older than > auto-indenting editors. So they are both viable and time-tested. More > importantly, it should be a lot easier to write a Clojure function to > pretty-print a file than to write a Jedit plugin to auto-indent one,
Don't forget that what you're calling "pretty-printing" is not what clojure.pprint is currently offering : clojure.pprint will remove your comments, transform or remove from view your metadatas, ignore your #_(...) code, etc. Your discussion has been slowly getting me into the mindstate that I'll add this missing "reindent whole file/current selection" feature in CCW, AH ! >or at least find someone willing to do so assuming it doesn't already exist. >While I'd prefer an in-editor solution, I don't think it's important enough to >delay things even a few minutes. That, of course, is the real issue - how >quickly can we put up an acceptable "single-download to clojure" distribution? >Which is why all this is academic until someone who can update clojure.org to >point to the download steps up and says "these are my requirements to do that." > -- > Sent from my Android tablet with K-9 Mail. Please excuse my brevity. > > -- > 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 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
