This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-23
Channels
- # announcements (10)
- # babashka (7)
- # beginners (31)
- # boot (4)
- # calva (8)
- # chlorine-clover (19)
- # cider (12)
- # clj-kondo (27)
- # cljsrn (7)
- # clojure (68)
- # clojure-colombia (2)
- # clojure-europe (47)
- # clojure-italy (16)
- # clojure-nl (4)
- # clojure-spec (13)
- # clojure-uk (39)
- # clojurescript (103)
- # code-reviews (8)
- # community-development (2)
- # conjure (38)
- # core-async (37)
- # cursive (2)
- # datascript (1)
- # datomic (31)
- # figwheel-main (22)
- # fulcro (18)
- # jobs (2)
- # jobs-discuss (6)
- # juxt (3)
- # keechma (1)
- # lambdaisland (6)
- # malli (30)
- # meander (20)
- # off-topic (29)
- # reagent (1)
- # reitit (16)
- # shadow-cljs (4)
- # tools-deps (70)
- # xtdb (19)
Dear Calva-friends: We've been working on a new evaluation result output window and it is time to let you help in testing it before we unleash it onto the marketplace. So, instead of printing evaluation results to the Calva says output pane, this build prints it to a ”regular” vscode file window. This has several advantages: • The output is syntax highlighted • Paredit is enabled in the window, making it easy to navigate and copy • The window is connected to the REPL making it an alternative to the REPL window for explorations. We have made it behave like a CLJC window, so with ClojureScript projects you can choose which REPL the file should be connected to (CLJ/CLJS). • Unlike the REPL window, the VIM extension will work in this window, to the extent it works in any editor window. In addition to this we now also print stack traces to this output window (when available) with clickable links to the file locations in the stack frames. Please help test this. Here's the VSIX: https://6580-125431277-gh.circle-artifacts.com/0/tmp/artifacts/calva-2.0.108-681-output-to-file-decefda4.vsix
One minor comment - I didn't initially see the temp output file window and was briefly puzzled. Perhaps on first run (or on jack-in) you should focus it? I do have tabs disabled, which I guess is probably unusual - presumably with visible tabs the user would immediately see the new tab. In any case this seems like a good idea - I find the current output window annoyingly zealous about popping up over other windows.
Didn't know you could hide the tabs. But even if i do, the output file window shows up when I connect the repl. Can you record a gif or something showing what happens on your machine? Focusing the window feels a bit interruptive to me.