What is "the inspector", can you tell more in detail what you are doing?

Of course: 1. Start babaska with bb --nrepl-server 2. Open a babashka file in emacs 3. cider-connect-clj to localhost and port 4. connection stablishes ok 5. I can evaluate forms (ns, defs, defns) as I usually do in Clojure projects. The inline evaluation overlay works just fine (for example: "(+ 1 2) => 3" in the same buffer). Everything is just fine until here, same experience as normal clojure development. 6. When I call cider-inspect on that same sexp, (C-c M-i in my key mapping), pops a new cider-inspect buffer with the text "Inspector error for 3". Thanks for your interest and quick answer.

I'm not sure what cider-inspect does, I'd have to reverse engineer that using https://github.com/lambdaisland/nrepl-proxy to find out. Perhaps you could check what the messages are that are being sent back and forth between JVM Clojure vs bb? Then we'd know what to implement. Could be some special op. /cc @U051BLM8F @U02CV2P4J6S

With that info in hand, feel free to create an issue at babashka.nrepl

Will look into it, thanks.

@UM4CBJVLZ If you do not have a namespace and eval the ns form first, irrc currently it might throw somewhere because some nil namespace is passed nvm 1 I was wrong and 2 you where asking about "Inspector"

the way it works is that cider makes a eval request with "inspect" "true". https://github.com/clojure-emacs/cider/blob/master/cider-inspector.el#L354 . The "value" response, then is an alist with inspect data. babashka currently has no concept of {:inspect true} , it returns a normal eval result value, then further in the code there is an error. Here is inspect.clj in cider-nrepl: https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/middleware/inspect.clj . The golden fix might be e.g. a pod with the whole cider middleware

You can also use portal for inspecting deeply nested data structures. It works with bb

The bb nrepl doesn't support all CIDER specific things, but perhaps we can make some middleware pluggable in user space

@U04V15CAJ Portal is a great alternative, works like a charm! Again, thanks.

Btw, cider-nrepl's inspect middleware is just a think wrapper around https://github.com/clojure-emacs/orchard/blob/master/doc/inspector.org

@U051BLM8F Thanks. Is the inspector also supported in other environments like Calva and neovim?

Not sure. The functionality is certainly not CIDER-specific, but I have no idea of someone has implemented so far or not. @U0ETXRFEW mentioned today he's interested in adding this in Calva.

I've been interested in adding it to Calva for a long time. And lately I've spoken to several users who wish Calva had it. It's going to happen when I or someone else find a time slot large enough to allow some focus.

I just wanted to bump this. I love cider inspect and not having it is something that makes me trade babashka for clojure.

I was looking into making cider middleware work on bb. Will make a discussion issue on github soon

https://github.com/babashka/babashka.nrepl/discussions/57

What are you specifically looking for, the task runner as a command line thing?

Mostly access to ...tasks/shell and ...tasks/clojure from the JVM

I see. I think we could just expose that namespace in the babashka project, would this be enough?

then you can depend on babashka as a dependency

I guess so yes, essentially renaming babashka.impl.tasks to babashka.tasks?

well, for starters, just exposing those two functions

I'm careful to not expose any internal details, so I can still make changes to those

Sounds sensible 🙂

ok issue welcome

and / or pr