This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (25)
- # beginners (132)
- # boot (89)
- # cider (26)
- # clara (12)
- # cljs-dev (10)
- # cljsrn (11)
- # clojure (151)
- # clojure-germany (8)
- # clojure-russia (1)
- # clojurescript (137)
- # cursive (33)
- # datavis (28)
- # datomic (3)
- # devcards (8)
- # hoplon (5)
- # immutant (11)
- # jobs (4)
- # ldnclj (58)
- # lein-figwheel (7)
- # off-topic (95)
- # om (114)
- # onyx (91)
- # parinfer (38)
- # portland-or (1)
- # re-frame (26)
- # reagent (1)
Opening a clojure project from the command line with
idea . used to create a new Clojure module, but it doesn’t seem to anymore?
Out of curiosity - recent discussion in #C03RZGPG3 made me wonder if there's any chance to support having some sort of tooltips for
schema.core/defn that could explain the nominal schema inline? That is, if you have
(defn function :- ReturnSchema [argument :- ArgumentSchema] ...) you could hover over the name and get it explained.
I watched a guy on Emacs and he was evaluating functions and the value would return in the editor beside the function - as far as I know Cursive can’t do this - I thought this was cool but not necessary
@tbrooke: At some point I’d like to have LightTable-style in-editor eval, but that requires interaction from the IntelliJ editors. It’s there at the moment as you can see in the debugger, but only supports results on a single line. I’d hoped the improvements to that would make it into v15 but it looks like they didn’t.
@cfleming: is this clear enough description of that? https://github.com/cursiveclojure/cursive/issues/1175
One thing I didn’t demo at the conj was that the grammars are now displayed in the doc popup
They’re tricky to follow by eye, though - I’m still not sure what the best way to display them is.
Gotcha. Cursive is still pretty awesome as-is. First thing that convinced me IDEs may not suck.
Good to hear. Now I just have to start earning money again so I can compensate the awesome work you did P ;
Yeah, it helps a lot. I haven’t had time to investigate, but v15 might allow me to do expression-level debugging instead of line-level.
Which reminds me, using remote debugger with JDPA sometimes starts being unresponsive when I evaluate something on a breakpoint. Is there any way to investigate what's causing it?
I’m not sure - the debugger is sometimes really slow in general, and I’m not sure how to investigate it.
I see. It's a bit vexing to be deprived of the debugger when it decides it won't be evaling, since it's one of the shiny things in Cursive. I hoped that maybe there would be some way to maybe help in debugging this.
Additionally, most of the functionality is provided by IntelliJ and I don’t pretend to understand it.
Yeah, hopefully they have some insight where to at the very least start looking, it would be cool to get it even more reliable. It's already come a long way since it was first introduced, I remember it being quite finicky back then.