This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-03-07
Channels
- # announcements (1)
- # architecture (9)
- # babashka (3)
- # calva (10)
- # clj-http (13)
- # clj-kondo (11)
- # clojure (23)
- # clojure-europe (11)
- # clojure-nl (1)
- # clojure-norway (112)
- # clojure-uk (4)
- # clojuredesign-podcast (8)
- # clojurescript (10)
- # core-async (5)
- # cursive (7)
- # data-science (15)
- # datascript (2)
- # datomic (29)
- # emacs (5)
- # events (1)
- # hugsql (1)
- # hyperfiddle (9)
- # midje (1)
- # missionary (3)
- # music (1)
- # off-topic (34)
- # polylith (1)
- # re-frame (16)
- # shadow-cljs (117)
- # squint (19)
- # yamlscript (1)
When I evaluate something in calva and it fails with an exception, how hard would it be to highlight the lines of the source code from the stacktrace in the editor? Similar to how it is done for failing tests? This would’ve sped up the development quite noticeably. Because today I have to switch to the repl output, click on Show stacktrace, find the line related to my source code, switch back to the source code, perform navigate to line number and type in the number that I found in the stacktrace.
➕ 2
Should I file an issue?
I guess we need to figure out when/how to clear the marker. But let’s discuss such things in the issue.