working on a draft of a blog article, trying to summarise the desirable features provided by (or via) the editors that I use. https://practical.li/blog-staging/posts/desirable-features-for-a-clojure-editor/ One original intent was to help people evaluate an editor, but I think the article is going to be more about the features I use and how they fit into my workflow (which perhaps may still help people evaluate an editor, but maybe something simpler is still needed for those starting Clojure). Constructive feedback welcome - considering this is only about 33% written 😄

imo, the only must have are: connected repl and structured editing. I don't use a lot of the other features on that page. Because I do a lot of interop, I rely heavily on code navigation into Java code, Javadoc support, and Java hierarchy inspection which are not on your list at all. :)

This raises I good point, I should qualify the article by highlighting the kind of things I write with Clojure. This will help understand why I find these features desirable. It would also be useful to add some weight to features, which in some sense covered by the order in which I've been covering the features - top being the most important. I think the only Java interop I've used in production is Java time and a shutdown hook, but then I haven't work on code for a programming language hosted on the Java Virtual machine 😄 It seems useful to mention other features I dont use and why they are useful to others though. I used to find structured editing more important than I do now. It is important, although I've recently moved from paredit style to parinfer. So still working out what I want to say on this feature. Thanks for the feedback Alex

I include parinfer in "structured editing"