Fork me on GitHub

did the sesman-integration recently change? I just updated cider, and when I do C-c C-s s to connect a sibling, I get a Select command: prompt with nothing suggested.


Usually it would suggest a whole series of cider-connect-* commands


Disregard that. For some other reason my completing-read is not completing anything anymore.


do you use use-package and the lazily loaded helm/swiper hasn't been loaded yet?


No, that's not it. But I do use several ido-packages. Luckily I made a backup of my elpa-directory before upgrading, so I'll now dig in and find the culprit with some good old bisecting.

parens 1

Turns out it was my fault all along, unsurprisingly, I just noticed it right after upgrading cider. I had a function that would temporarily disable ido-ubiquitous-mode - and then sometimes fail to enable it again. Fixed with an unwind-protect

Yehonathan Sharvit13:09:50

Hello there Is there a way to automagically inject figwheel main when lauching a cljs repl. I am getting this error

error in process filter: Figwheel-main is not available.  Please check 


This seems to be the relevant doc. You can add [com.bhauman/figwheel-main"0.2.3"] to your user deps.edn, if no one here shows up and tells us that it can be configured to be inlcuded in jack-in.


It should be enough to do (cider-add-to-alist 'cider-jack-in-cljs-dependencies "com.bhauman/figwheel-main" "0.2.3") I believe.


much better to put it in an alias or a profile


adding it to that alist will put it in every cljs project which seems inadvisable


Unless the alist thing can be made so that it is “workspace” (using vscode terms…) local?

Yehonathan Sharvit19:09:10

@dpsutton Why is it better to put it in an alias or a profile?


It’s a true dependency of your project. Nothing cider specific but your project depends on figwheel main

👍 1

The development of the project depends on Figwheel Main. So it is not clear cut, I’d say. But, yeah, there are profiles for that, of course. Yet, it is also something CIDER could help with, when it sees that Figwheel Main is involved. Calva does, because I think it makes sense.


sure. so put it in a dev profile/alias


if you don't have that, how would anyone run your project. its not piggieback that a CIDER dep needs, its a dep required to compile your cljs


CIDER shouldn't help with this because people not using CIDER need this as well

👍 2

Yes, makes sense.

Yehonathan Sharvit19:09:21

@dpsutton any idea how to add figwheel-main to dev profile for clojure-cli and let CIDER aware of it?


do you mean how do you start CIDER with a profile/alias?


@viebel Add a .dir-locals.el file to root of project, specifying it for cider. Here's mine:

  (cider-clojure-cli-global-options . "-A:dev")
  (cider-default-cljs-repl . figwheel-main)
  (cider-figwheel-main-default-options . ":dev")))


just stick it in the dev profile. then you can use dir locals as posted above or you can use a prefix argument when jacking-in to edit the command

Yehonathan Sharvit19:09:14

how do I pass aprefix arg to jack-in command? Sorry I am new to spacemacs?


i actually don't know for spacemacs. But for emacs, the normal cljs-jack in command is C-c M-J and to send the prefix is C-u C-c M-J


its just a control U before the normal invocation


and quite possibly its the same

Yehonathan Sharvit20:09:51

Thanks a lot @dpsutton and @dpsutton. You helped me made another small but significant step towards the epiphany

cider 1
👍 1

So useful he thanked you twice 😄

😜 1

thank @magnars for the helpful .dir-locals.el syntax. i get that wrong three times every time

Yehonathan Sharvit20:09:11

(Sorry for the typo @dominicm)

😜 2