Cursive Clojure: A Clojure IntelliJ plugin
41–50 of 61 posts
Re: Cursive Clojure: A Clojure IntelliJ plugin
#42Earlier quoted context omitted.
> I assume you'd want to see those in the Lein toolwindow? Exactly. Good plugin BTW. I like the jump to Java code (I work on a mixed Java/Clojure project), and was very happy to find out that renaming a Java method fixed the Clojure calls, too. And find usages works across languages! Keep up the good work! EDIT: One problem I've found: If a function is defined not with defn but using a macro that expands to defn, the…
Thanks, glad you're liking it! Any issues, let me know. There's still a lot to do but it's very usable right now.
Re: Cursive Clojure: A Clojure IntelliJ plugin
#43Earlier quoted context omitted.
This will be commercial, similar to PyCharm, RubyMine and the other JetBrains IDEs. I'm considering a slightly restricted free edition that can't be used for commercial work, but I haven't worked out the details yet. It almost certainly won't be fully open source, but I'm considering having a small closed source core and then the majority of the Clojure implementation being open source and extensible. This will need…
how does that work if it's a fork of la clojure? are you paying intellij? did they licence their code under a very open licence?
Re: Cursive Clojure: A Clojure IntelliJ plugin
#44Why not Eclipse? 65% of java developers use it. Only 9% uses IntelliJ. Just asking.
I suspect that you'd probably find that the percentage of Java devs using IntelliJ has gone up a lot in recent years too, their market share and mindshare has increased massively recently. I'm not aware of any stats though (and I'm not sure how accurate they would be if there were). Google recently switched from Eclipse to IntelliJ for the official Android development environment, for whatever that's worth.
Re: Cursive Clojure: A Clojure IntelliJ plugin
#45Re: Cursive Clojure: A Clojure IntelliJ plugin
#46Earlier quoted context omitted.
There's still some lein functionality I need to add. Currently the best way to add a non-standard task like lein midje is to create a run config (Run->Edit Configurations..., hit + and select Leiningen). I'm going to be improving this soon - I assume you'd want to see those in the Lein toolwindow? Drop me an email if that doesn't do what you need it to.
> I assume you'd want to see those in the Lein toolwindow? Exactly. Good plugin BTW. I like the jump to Java code (I work on a mixed Java/Clojure project), and was very happy to find out that renaming a Java method fixed the Clojure calls, too. And find usages works across languages! Keep up the good work! EDIT: One problem I've found: If a function is defined not with defn but using a macro that expands to defn, the…
Re: Cursive Clojure: A Clojure IntelliJ plugin
#47Re: Cursive Clojure: A Clojure IntelliJ plugin
#48Earlier quoted context omitted.
> I assume you'd want to see those in the Lein toolwindow? Exactly. Good plugin BTW. I like the jump to Java code (I work on a mixed Java/Clojure project), and was very happy to find out that renaming a Java method fixed the Clojure calls, too. And find usages works across languages! Keep up the good work! EDIT: One problem I've found: If a function is defined not with defn but using a macro that expands to defn, the…
Yeah, that defn problem needs a whole blog post - damn macros.
But it seems that the Java interop aspect of Clojure complicates this picture. The JVM poking through isn't inherently good or bad (for some people that interop is an advantage, for others it's unfortunate), it's just different from other lisps.
So the point I'm ponderously getting around to making is -- it seems like this IDE will be most useful for people using Clojure as a JVM lang, as opposed to using it as a lisp per se. Would you say that's a reasonable characterization, or not?
Re: Cursive Clojure: A Clojure IntelliJ plugin
#49Developer here - I'm happy to answer any questions folk might have!
TIA
Re: Cursive Clojure: A Clojure IntelliJ plugin
#50Earlier quoted context omitted.
Yeah, that defn problem needs a whole blog post - damn macros.
Although you've probably thought about this more than I have, it seems like there's a fundamental tension here. On the one hand there are Java IDEs and code-generation in the sense of (re)writing physical source code files. On the other hand, there are lisp macros in the sense of "an API for the compiler". Fully embracing the latter can obviate much of the need for the former (at least there's a long lisp tradition o…
But even languages with more ephemeral dispatch (Ruby, Javascript, Groovy) can benefit from an IDE. It's often convenient to have an editor, a debugger, and control over the build in a single program (and that's why emacs is an IDE).
So I don't see any connection between IDEs and the JVM. Some people enjoy IDEs and some don't.