Fork me on GitHub

Is there a way to have cursive be able to resolve babashka projects? For example, babashka.curl and other namespaces are always unresolved


(or at least to not complain about those)


You can add a deps.edn with these libs


There isn’t a way to get this to work automatically at the moment, sorry - I’m planning to add an SDK type which will help with this.


There’s an issue discussing problems with bb:

R.A. Porter14:04:34

I see that IJ 2021.1 is released. I used to be aggressive about upgrading and often ran on the EAPs, but because they like to make little changes that break Cursive I’ve become much more gun shy. Were the betas/RCs running well with Cursive so that I can assume it’s safe to upgrade today, or would it be better to wait a few weeks?


I haven't upgraded yet as a few other plugins I use aren't compatible yet. However there was this a few days ago:

👍 3

i just upgraded intellij idea to 2021.1 and got the java.lang.Throwable: Non-idempotent computation: it returns different results when invoked multiple times or on different threads exception as a pop-up notification when opening every existing deps.edn project. i'm not sure if it breaks anything but figured i should report it here in case Colin is interested in fixing it (stacktrace attached).


I upgraded to 2021.1 also and my remote repl configuration stopped working. Error stated that "REPL run configuration is incorrect - no module selected" when I attempted to run it.


Like all things, it works now after invalidating the project caches and restarting


I’ve been using 2021.1 since the start of the EAP and it’s been working well for me. The idempotence check isn’t new in 2021.1, that’s been there for a while now.

👍 3

i see. i am greeted with this error message whenever i open an existing deps.edn project. it would be nice it didn't show up in the first place if it doesn't have any impact on the functionality/stability of the ide/cursive.


Yes, this is unfortunate, and I’m not sure what the implications are since it doesn’t seem to affect anything that I can see. Fixing it is also a significant engineering effort at this stage. I’m going to talk to JetBrains about it and see if I can disable the message in the meantime.

thanks2 3
Ilari Tuominen14:04:10

I just updated and then remembered that I haven’t bought a new Cursive license, I can safely say that Cursive 1.10.0 does not work with Idea 2021.1. Is upgrading cursive the only path for me now?


Right, 2021.1 support was added in 1.10.1. You’ll have to upgrade Cursive in that case, yes.

Endre Bakken Stovner15:04:26

In IdeaVIM, how can I make * search for the whole term? Currently, if the cursor is above create in create-jobs it looks for create not create-jobs.


I’ve wondered the same thing :man-shrugging:


Configure iskeyword

Endre Bakken Stovner15:04:30

Is there a refactoring that allows me to rewrite (deeply (nested (function calls))) into (-> (function calls) nested deeply)


thread form and unthread form

Kari Marttila19:04:16 => is it safe to install (i.e. will Cursive work with this new version)?

Kari Marttila19:04:44

Aah, someone already tried... maybe not yet installing it. 😀

Jeff Evans19:04:35

I have two machines so I’ll be a guinea pig on one of them

Jeff Evans20:04:36

first observation: Recent Projects disappeared

Jeff Evans20:04:43

although that may happen with every major update. I can’t remember

Jeff Evans20:04:53

and my Cursive specific keyboard shortcuts disappeared 😞

Jeff Evans20:04:16

although IntelliJ sync restored those, phew


i haven't experienced any of those issues. (im on latest macOS Big Sur 11.2.3 (20D91) and cursive 1.10.2-eap2-2021.1)


the paren highlighting has definitely changed back to that undesirable state where it was in 2018 😞 if my caret is at the position of | in an expression like (xxx (yyy)|), then the 1st open paren is highlighted, instead of the 2nd open paren as the matching one.


im getting some cursive exceptions though, but those seem to be the same one i was getting on earlier versions of intellij too, so i think it's specific to my actual project. for the record, here is the exception:

java.lang.Throwable: Non-idempotent computation: it returns different results when invoked multiple times or on different threads:
  class cursive.psi.impl.synthetic.ClJavascriptAlias != class cursive.psi.impl.synthetic.ClNamespaceAlias
  which is class of Namespace alias http (org.httpkit.client) and Namespace alias http (org.httpkit.client)
  which is element of cursive.psi.resolve.ClojureResolveResultImpl@3f42ab17 and cursive.psi.resolve.ClojureResolveResultImpl@5c5dd6a
  which is 0th element of [cursive.psi.resolve.ClojureResolveResultImpl@3f42ab17, cursive.psi.resolve.ClojureResolveResultImpl@3e89e311] and [cursive.psi.resolve.ClojureResolveResultImpl@5c5dd6a, cursive.psi.resolve.ClojureResolveResultImpl@5c3437cb]


@U086D6TBN I’m not seeing that paren problem, it’s working fine for me and no-one else has reported that.

👏 3

And yes, the non-idempotent thing is an ongoing problem, not 2021.1 specific.

👍 3

great to hear that the paren thing is not reproducible. most likely it's caused by some plugin then! i will do some bisecting on my plugins!


I’m interested to hear if you figure out which one it is!


one more data point: to me the parens are working as expected


one very subtle detail I noticed (maybe not from the last IntelliJ, but using Intellij with BigSur): the cursor, specially the Text cursor, seems like instead of having the “clicking point” in the middle (as it is in the rest of the OS) it is positioned at the top left corner of the icon (like if it was a pointer cursor)


did anybody else experience that? I noticed this after having a bunch of selections that I though I was starting at a specific char, but off by one, many times


quick documentation is broken for me since the update: colour scheme doesn't follow dark mode, and popup randomly shows up as docked then stops showing at all until restart


@U0567Q30W i've just installed an IntelliJ CE 2021.01 from scratch and only added Cursive stable as a dependency and the highlighting works as expected. I've upgraded Curisve to 1.10.2-eap2-2021.1 and highlighting still works. On my main config, even after removing the Rainbow Brackets plugin, the highlighting is still buggy. Here is my IntelliJ config, with all the plugins listed at the end. Maybe having a glance over them would give u an idea which one might interfere with Cursive:

IntelliJ IDEA 2021.1 (Ultimate Edition)
Build #IU-211.6693.111, built on April 6, 2021
Licensed to Tamas Herman
Subscription is active until November 26, 2021.
Runtime version: 11.0.10+9-b1341.35 x86_64
VM: Dynamic Code Evolution 64-Bit Server VM by JetBrains s.r.o.
macOS 11.2.3
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 16
Registry: ide.allow.merge.buttons=false, ide.settings.move.mouse.on.default.button=true,
Non-Bundled Plugins: AceJump (3.7), IdeaVIM (0.66), Key Promoter X (2021.1.1), Org4Idea (0.4.1), Shell Process (1.3.2), YAML/Ansible support (0.11.2), com.4lex4.intellij.solarized (2.3.0), com.intellij.plugins.watcher (211.6693.44), com.paperetto.dash (3.3), de.dieploegers.develop.idea.shellfilter (3.0.3), de.netnexus.camelcaseplugin (3.0.8), io.protostuff.protostuff-jetbrains-plugin (0.13.0), nix-idea (, org.intellij.RegexpTester (1.0.8), org.jetbrains.plugins.localization (211.6693.44), (211.6693.44), mobi.hsz.idea.gitignore (4.0.4), name.kropp.intellij.makefile (211.6693.108), AWSCloudFormation (211.6693.108), (1.2), org.toml.lang (, com.github.pshirshov.bytecodeeditor (0.2.1), zielu.gittoolbox (203.5.3), com.intellij.plugins.html.instantEditing (211.6693.111), com.cursiveclojure.cursive (1.10.2-eap2-2021.1), com.jetbrains.plugins.jade (211.6693.65), com.dmarcotte.handlebars (211.6693.44), PlantUML integration (5.1.0), Pythonid (211.6693.115), aws.toolkit (1.25-211), net.ashald.envfile (3.2.1), ru.meanmail.plugin.requirements (2021.3-211), org.asciidoctor.intellij.asciidoc (0.32.35)
Kotlin: 211-1.4.32-release-IJ6693.72

Lone Ranger22:04:47

hail mary: there's no chance Cursive has a cljs debugger, is there?


Sadly, no, sorry.

Lone Ranger17:04:29

No worries. Seems really elusive thinking-face