This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # beginners (64)
- # calva (40)
- # cider (76)
- # clara (13)
- # clojure (72)
- # clojure-dev (34)
- # clojure-italy (4)
- # clojure-nl (14)
- # clojure-poland (1)
- # clojure-uk (30)
- # clojurescript (58)
- # clr (10)
- # core-async (101)
- # crux (14)
- # cursive (31)
- # datomic (9)
- # emacs (20)
- # fulcro (2)
- # jackdaw (1)
- # jobs (3)
- # juxt (3)
- # luminus (4)
- # lumo (15)
- # mount (4)
- # nrepl (29)
- # nyc (1)
- # off-topic (27)
- # qlkit (1)
- # quil (5)
- # re-frame (19)
- # reitit (8)
- # remote-jobs (4)
- # rewrite-clj (5)
- # shadow-cljs (45)
- # spacemacs (22)
- # sql (9)
- # uncomplicate (1)
Calva 1.3.66, VSCode 1.33.1 (are these latest versions?) -
Running the contributed command: 'calva.reconnect' failed. every time on running reconnect command - is it normal? autoconnect on open clojure file works fine
@ivana, that's the latest published version. There is also a dev/beta version that sometimes get posted here. Re your problem: I don't think you need to use the
Connect should work. Do you get the same error if you do that instead?
Running the contributed command: 'calva.connect' failed. the same thing on connect command
I have to close/open VScode and it solves the problem, and it is not hard to me to do this 🙂 But I think it may be interesting for you 🙂
It sounds a bit like Calva isn't activated. It needs a clojure-ish file to be opened to activate. Do you have that?
I should probably try to remove that requriement. I have, in fact tried a few times, but so far my attempts to do so have failed.
The only difference between 1.3.65 and 1.3.66 is that the latter logs some usage data to google analytics. But only if the user allows telemetry logging in settings. Thinking it could have to do with that in some strange way. Do you allow telemetry in your settings?
OK. So then it shouldn't have to do with that I think. At least I haven't noticed anything like that.
If you uncheck them Calva won't log any usage from your sessions. That's the simple relationship. 😃
For the record, Calva really does not log anything personal. And you don't have to take my word for it. It's open source. 😍
I think we all should be a bit more paranoid, but yeah, open source is cool in that way too.
The stats tell me that most of the attempts to connect a cljs repl fail. Which makes me cry, of course, but better that I know it, than I go around thinking everything is dandy.
I understand why stats are important for software developers. But I guessed that these logs only for Microsoft, not for side extensions behaviour
The API is there for extensions to check if telemetry is enabled. I know some extensions add an extra setting about their logging, but I kinda hate settings. 😃
I typed and deleted long sentensies twice, so in a pair of words - thank you for fast answers and your work! 🙂
@pez I now in installed the above 2.0.0-SNAPSHOT. When I run jack-in command, I get an error that
calva.jackIn is not found.
@jehrhardt: I’m glad you didn’t wait for the more stable version. 😃 (It is stuck in production.)
This is from a secret Getting Started with Calva 2 doc:
1. Install VS Code.
2. Install Calva (via the Extensions pane).
3. Open a Clojure(Script) file in the root of your project.
4. Issue the *Calva Jack-in* command,
OK, it worked after using the short cut. I have selected, what to run. But I could not start figwheel. Thus I got only a Clojure, but no ClojureScript REPL.
I might have changed it to
ctrl+alt+v ctrl+alt+j in that version you are testing, I don’t recall.
Any clojure-ish file will do. Calva won’t really wake up until such a file is opened. (Because reasons).