I don't quite understand why we can't instrument clojure core functions, so can't comment on how doable it is. I think that would be quite awesome to be able to do.

As for alternatives. The Cursive debugger is the best traditional debugger for Clojure that I know of. For your purposes though, maybe a tracer like @U02EMBDU2JU’s omni-trace would be a good fit? https://github.com/Cyrik/omni-trace Lukas demoed it at ClojureD 2022: https://www.youtube.com/watch?v=JitNGtiuNOA

I've mostly switched to using https://github.com/jpmonettas/flow-storm-debugger since I don't have the time to work on omni-trace right now

Thanks, guys!

I suppose the core fns don't work because of direct linking. All of core is compiled with that, which means no var indirection, which means no instrumentation. Should be able to get a core lib with that disabled though.

Just tried out flow-storm-debugger. It's a nice tool. The key difference between it and Calva's debugger is that flow-storm-debugger shows what happened after the fact. It doesn't allow you to step through code yourself; it shows you what code was stepped through when you ran it previously.

I never realized that Clojure was so lacking in the debugging world, since we all just use our REPLs and generally understand the flow of execution. But for someone learning Clojure as a first language, that really doesn't cut it. Makes me realize that jank can bring big wins here with some out of the box DAP tooling.

To me it seems like showing a beginner the flow using flow-storm after execution is just as good, if not better, than showing it during execution, since you can step backwards in time too. I think showing a beginner how to use inline defs to be able to execute any part of the code in question at will is also probably pretty important. I added much of the debugger functionality to Calva when I was still fairly new to Clojure, but I don’t even use it (or any debugger). I do think it might be a good idea for me to try using something like flow-storm more in some situations, but so far I don’t really feel a need for something like that. It could be the case that I just don’t know what I’m missing, though.

I've just gotten used to having it in my dev deps and staring it with a hot key if I'm doing something that could use it.

Ah I should put it within easy reach like that.

Hard to tell without knowing more about the project structure. Can you describe it a bit?

Sure, I can share it with you even if you want

its not a private thing

not on gh just yet tho

It's not normal. To answer your question. sounds like something is wrong.

Push it to GH and I'll have a look.

sure, just need to remove some stuff first

Here's a quick repo, will delete it when youre done https://github.com/LouDnl/yls-pez

I must be doing something wrong somewhere wit hconfig

with configuring*

I can't easily test this because postgres and possibly other things. There is nothing that strikes me as wrong at a glance. (I would remove the nrepl dependencies from the project unless they are needed for something else than editor tooling.) Can you describe the steps you take to start, and what you expect should happen?

The nrepl deps are needed for the repl namespace. Steps: Open VSCode project Jack-In choosing the project root Select dev and calva aliases Wait for repl clj:user:> (require 'youless.core) Try to start statemanagement:

; Execution error (ClassNotFoundException) at java.net.URLClassLoader/findClass (URLClassLoader.java:476).
; mount.lite

(require 'youless.core)
; Execution error (FileNotFoundException) at youless.config/eval7237$loading (config.clj:1).
; Could not locate taoensso/timbre__init.class, taoensso/timbre.clj or taoensso/timbre.cljc on classpath.

But

When I dont select aliases the (require 'youless.core) works - disregard this

But I dont know why and I dont know why I have to require first

@U0ETXRFEW you can test it without postgres, I cant even get a namespace after jackin without starting the project using mount.lite

I had an error in the :dev alias that overrided the main deps, so thats solved. I used :deps instead of :extra-deps. But that still doesnt explain why I need to do (require 'youless.core) first?

What does ”Try to start statemanagement” mean?

Ah, you can ignore that but its (mount.lite/start)

If I do a require first everything works fine.

But that shouldnt be necessary am I right?

Calva does not require anything for you, so if your project needs a special order of requires, it could be that you need to require some namespace before some other for things to work. In this case it seems like it is unintended so I would go from the error messages you get and see what might be missing in your ns forms.

Also have a look at the leiningen project to see if it had some init-fn configured our something. Might give some clues to what you need to do with the deps project to make it work.

Okay, thanks for the tips

Will let you know what the outcome is

I think what I am missing are the deps.edn equivalents of project.clj's :

:main youless.core
:aot [youless.core]

@U0ETXRFEW I think I solved it by using "afterCLJReplJackInCode": "(require 'youless.core)", in my custom calva.replConnectSequences

I was about to suggest that. It could be the right solution even.

You don't need any :calva alias if you are using jack-in, btw. Jack-in will override those (as well as the global nrepl dependencies you have there.)

Thanks for the tip, removed it from my project and indeed works as you describe

I most often ask here. 😀

IIRC there’s a Slack for vscode

It’s dev-related, but might be helpful for you.

https://code.visualstudio.com/blogs/2022/10/04/vscode-community-discussions There’s a link on this page near the bottom, and there’s also a link to the VS Code community GH discussions.

thanks!