Fork me on GitHub

@katox You reported in another thread: > Another thing that stopped working in the latest build is that kill stopped working on multi-line strings. The workaround is to to join the lines, then kill. I just checked the code, and nothing has changed here in forever. I think this has always worked like that.


Bad memory then, sorry. I'd expect it to behave like in a sexp so likely projecting...


Is this a known problem: REPL tabs are unnamed


Here I have three REPLs running, but their tabs are empty. It would be nice to have some text e.g repl configuration name in them.


hmm, mines show names. Are you setting a name in the config?


Using now IDEA 2020.3.2 and latest Cursive, the issue has been some time now, I don’t remember when this started.

Jeff Evans14:02:57

Mine also show the correct names


Names should definitely be shown. @U1G5P6G0L can you email me your log file to <mailto:[email protected]|[email protected]>?


Yes, but how/where to find it? The log file

Jeff Evans22:02:33

I believe it’s Help/Show Log in … and it’s called idea.log


I just sent the email


Is there a way I can get Cursive to 'recognise' defspec forms ( as tests that I can run with 'run test under caret in repl' and suchlike? At the moment I have to switch to the namespace and manually call the spec in question, which is not a massive hardship it's just I'm used to the shortcuts by now (also the manual run doesn't set the gutter icons on any (is ...) forms in the defspec like 'run test under caret' or 'run all tests in namespace' do (but that's slow when the namespace contains a lot of defspec tests)


I’m not sure there is. I’ve been meaning to look at this for a while, I think this probably needs to work in a slightly different way due to the phases (running, shrinking etc)

Zak Singh09:02:07

You can resolve it as `deftest`. The last option of `Resolve as` is `Specify...` and let you type the name of the var you want. Just type `deftest` and you’re good to go —


You know, I was going to say "That doesn't work", because I tried it before and it didn't seem to where it did for other macros I'd told Cursive to interpret as defn, but it looks like it now is working, without me having to re-specify. Fills the gutter icons and everything. All I've done is restart the IDE (which I didn't have to for the other ones), so :man-shrugging::skin-tone-2: , but it's working so hurrah! Ta both

🎉 3

I tried to tell Cursive to recognise/treat defspec like deftest, and that didn't seem to work, and I have to admit beyond that is beyond my current Cursive-fu


will cursive work with shadow-cljs style imports of npm modules? .. like in the sense jump to definition etc.?


Not at the moment, but this is something I’m hoping to improve soon. It’ll be subject to the limitations of how insane JavaScript is though.


haha, thanks for letting me know and thanks for Cursive! 🍻


I have “Prettify stacktrace elements with folding” checked in the Cursive settings but stacktraces in the REPL do not appear to be folded (I’m assuming that a folded stacktrace will show the full error and then a folded stacktrace). What should a “folded” stacktrace look like?


What the prettifying does is fold the Java-y bits and replace them with more Clojurefied versions, e.g. replace package names with namespaces, class names with demunged fn names etc.


It doesn’t work for the printed error objects at the moment unfortunately, since it’s regex based and they’re more subject to formatting.


@U0567Q30W Thanks for the clarification!


Here’s what I’m seeing with “Prettify stacktraces with folding” set to “on”:


Answering my own question here: I think I know what’s going on here. I have a REPL command which restarts my server and which calls tools-ns/refresh which is returning the error. Pressing the “print last stacktrace” button shows a prettified stacktrack with the error at the end as expected.