This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-31
Channels
- # announcements (1)
- # babashka (11)
- # beginners (33)
- # calva (11)
- # clj-kondo (6)
- # clojars (8)
- # clojure (28)
- # clojure-europe (16)
- # clojure-nl (1)
- # clojure-norway (6)
- # clojure-sweden (23)
- # clojure-uk (5)
- # clr (10)
- # gratitude (6)
- # hyperfiddle (14)
- # jobs-discuss (1)
- # lsp (7)
- # pathom (6)
- # pedestal (3)
- # polylith (4)
- # ring (4)
- # specter (6)
- # squint (8)
hey folks, I'm using debux https://github.com/philoskim/debux to debug my code, basically it is a glorified print. I want to know if there is a way for it to show results on Calva's inspector? Is it possible to redirect non-eval output to it? for example if I print something, can I redirect to Calva's Inspector?
Absolutely new to Calva. Clean install on Win11Pro64 (VS Code, Java, Leiningen, Calva). My extensions in VS Code: Calva v2.0.452, Rainbow Brackets, SVN and WSL. When trying to start the debugger on my mini clojure pgm (about 222 lines) I get the message "You don't have an extension for debugging Clojure. Should we find a Clojure extension in the Marketplace?"
Welcome to Calva! Calva’s debugger doesn’t fit the VS Code model of a debugger completely. It works a little bit differently. One such difference is that you don’t really start the debugger. Calva is attached to the running application and the debugger will stop at breakpoints. However, you don’t place breakpoints the VS Code way either (at least not yet). Instead you instrument functions for debugging. Instrumenting is easier than it sounds. Instead of evaluating a function the normal way, you use a special inststument command that will evaluate it in a way such that breakpoints are attached. See https://calva.io/debugger/ for how to use it. There you will also find the various limitation that the implementation has. One of which is that it does not work in ClojureScript, only in Clojure.