This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-16
Channels
- # announcements (3)
- # babashka (48)
- # beginners (35)
- # calva (3)
- # chlorine-clover (5)
- # clj-kondo (9)
- # cljdoc (20)
- # cljsrn (1)
- # clojure (55)
- # clojure-europe (33)
- # clojure-nl (3)
- # clojure-norway (6)
- # clojure-spec (7)
- # clojure-uk (27)
- # clojurescript (95)
- # closh (1)
- # conjure (1)
- # cursive (16)
- # datomic (30)
- # emacs (7)
- # honeysql (1)
- # hugsql (2)
- # introduce-yourself (2)
- # jobs (1)
- # lsp (30)
- # malli (22)
- # nbb (11)
- # news-and-articles (1)
- # off-topic (8)
- # pathom (21)
- # polylith (39)
- # portal (4)
- # practicalli (4)
- # protojure (1)
- # re-frame (14)
- # releases (1)
- # restql (1)
- # reveal (24)
- # sci (1)
- # sql (21)
- # vim (11)
- # xtdb (33)
Hello 🙂 👋 When manually upgrading a clj REPL to a cljs one, is there a way to tell calva that that happened? It looks like the REPL is still in a “clj” state, not allowing me to eval forms from a .cljs file
👋 4
That is not working very well today at all. I think that what you might get away with is to do :cljs/quit in the REPL that Calva has upgraded, and then upgrade that one.
Also, if it mainly is that you need your cljs REPL to be created in some special way, you can use Custom REPL Connect Sequences for that: https://calva.io/connect-sequences/