This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-12-31
Channels
- # adventofcode (4)
- # ai (1)
- # announcements (13)
- # babashka (1)
- # beginners (42)
- # calva (15)
- # chlorine-clover (28)
- # cider (7)
- # cljsrn (1)
- # clojure (3)
- # clojure-china (1)
- # clojure-dev (4)
- # clojure-europe (7)
- # clojure-losangeles (1)
- # clojure-nl (3)
- # clojure-nlp (2)
- # clojure-sweden (12)
- # clojure-uk (2)
- # clojurescript (30)
- # code-reviews (36)
- # core-async (5)
- # cursive (10)
- # data-science (1)
- # datalevin (1)
- # fulcro (11)
- # introduce-yourself (1)
- # lsp (10)
- # malli (7)
- # minecraft (24)
- # missionary (10)
- # monads (6)
- # nrepl (4)
- # off-topic (11)
- # portal (4)
- # rdf (1)
- # reagent (3)
- # releases (4)
- # shadow-cljs (4)
- # spacemacs (4)
Calva version 2.0.232 is out! Here are the changes: • https://github.com/BetterThanTomorrow/calva/issues/1355 • Fix: https://github.com/BetterThanTomorrow/calva/issues/1386 • Fix: https://github.com/BetterThanTomorrow/calva/issues/1448
Hey I am having slight problem with Calva, when using Jack-in, sometimes it gets buggy and spits evals into both output window and editor window. This doesn't happen when I am reusing terminal started repl. I don't have much vscode knowledge to debug what can be causing this. I have parinfer and vim extension (but I disabled them to try and it seems to still happen)
when evaling, the output appears in calva output window and also completely replaces current editor window with text from calva-output, after ctrl+z returns to normal
I don’t think Calva binds ctrl+k on Windows. What is the command that those bindings are executing on your machine?
So, it seems this behaviour happens after some logging happens, using timbre. Before eval and After eval pics included
it sort of barfs the output from calva window, into both calva window and current editor window
Looks like that test.clj file is located in the .calva/output-window folder? Maybe if you jack-in while having that file opened, that Calva gets confused about the project root and/or about which file the output window is written to. Not sure, but please file an issue.