calva 2021-06-28 | Slack Archive

zimablue02:06:10

sorry, I asked a question on a thread earlier and @brandon.ringe helped me a lot, I just wanted to follow up on the last question: is there any Clojure tooling which doesn't have this limitation? (of only being able to debug forms which were explicitly re-evaluated using the REPL)

pez05:06:38

Possibly Cursive. It has a very strong debugger.

zimablue06:06:16

I wondered that, but it says that it uses cider/nrepl ("extensively") in the docs, so it seems that it would share any limitations.

pez06:06:56

It is also using other stuff. 😃 The debugger is implemented directly on the JVM. Check this out: https://www.youtube.com/watch?v=ql77RwhcCK0

bringe16:06:31

@U63D7UXJB You may also be interested in flow-storm. There are a couple of links to info about it in this issue: https://github.com/BetterThanTomorrow/calva/issues/1119

bringe16:06:35

It works a bit differently, though, and is not integrated with the editor. Well, it also probably wouldn't help with the issue you're talking about either. Even still, it may interest you. :man-shrugging:

zimablue03:07:20

thanks a lot for this, belatedly, very interesting

👍 2

grierson12:06:23

Hey, How do I turn off inline eval? I prefer just seeing the results in the REPL.

pez13:06:36

You can't turn that off.

Yuner Bekir13:06:55

Hello guys, I am trying to start my project with calva and I am using the leiningen + Legacy Figwheel project type. I usually don't have problems with it. But recently it started behaving strangely and it doesn't want to connect to a cljs repl. After which if you attempt to evaluate anything on it, it just doesn't happen. Sometimes the problem gets fixed on its own. For example if I wait till tomorrow it may startup normaly

pez13:06:51

That looks like a bug. Can you file an issue on Github about it? If you do it from VS Code’s Help menu some info about your setup will be attached.

👍 3

2021-06-28

Channels