This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-10
Channels
- # announcements (4)
- # babashka (40)
- # beginners (39)
- # calva (16)
- # cljdoc (1)
- # cljs-dev (8)
- # clojure (72)
- # clojure-europe (10)
- # clojure-losangeles (1)
- # clojure-nl (4)
- # clojure-spec (9)
- # clojure-uk (12)
- # clojurescript (16)
- # community-development (15)
- # conjure (5)
- # cursive (5)
- # datomic (26)
- # eastwood (1)
- # emacs (7)
- # events (1)
- # figwheel-main (15)
- # fulcro (27)
- # graphql (7)
- # gratitude (4)
- # introduce-yourself (1)
- # malli (4)
- # meander (4)
- # off-topic (2)
- # other-languages (13)
- # polylith (7)
- # reagent (5)
- # reitit (5)
- # shadow-cljs (27)
- # spacemacs (4)
- # sql (3)
- # tools-deps (6)
- # xtdb (13)
hey, I'm thinking about adding functionality to jump around the log buffer more easily:
• jump to bottom of log from whatever window you're in. To prevent the HUD from going without having to switch into the log and do G
• jump to top of latest evaluation results. To allow one to not have to manually scroll back up to fully read the results of the last thing you evaluated in the repl.
Does something like this already exist? Anyone have suggestions or comments on such ideas?
On the second one, it would be great to have a couple navigation bindings in the log buffer itself to go up and down (first/prev/next/last result)
I implemented the second point, but without any generic nav bindings, though I like the idea https://github.com/Olical/conjure/pull/302
I'm also interested in tools that might help navigate large stacktraces that are printed to the log buffer. Things like autofolding exceptions or shortcuts to jump to next/prev exception. I know CIDER has some stuff like this but I'm not very familiar with them (or CIDER). Has anyone thought about how conjure could help with clojure's large stacktraces?