This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # announcements (1)
- # beginners (164)
- # calva (70)
- # cider (26)
- # cljs-dev (6)
- # cljsrn (1)
- # clojars (3)
- # clojure (123)
- # clojure-berlin (1)
- # clojure-dev (5)
- # clojure-ecuador (9)
- # clojure-europe (2)
- # clojure-italy (14)
- # clojure-nl (21)
- # clojure-nlp (5)
- # clojure-portugal (1)
- # clojure-spain (3)
- # clojure-spec (26)
- # clojure-uk (47)
- # clojurescript (17)
- # clr (1)
- # code-reviews (7)
- # core-async (5)
- # cursive (8)
- # data-science (2)
- # datomic (28)
- # emacs (23)
- # events (1)
- # fulcro (43)
- # graalvm (6)
- # graphql (8)
- # immutant (5)
- # jackdaw (17)
- # jobs (1)
- # jobs-discuss (20)
- # joker (3)
- # leiningen (8)
- # luminus (12)
- # off-topic (61)
- # overtone (5)
- # pathom (2)
- # quil (1)
- # re-frame (15)
- # reagent (2)
- # reitit (23)
- # remote-jobs (1)
- # schema (1)
- # shadow-cljs (26)
- # tools-deps (56)
- # vim (4)
Hi. Whats the rationale behind new plugin? Is older plugin deprecated and not supported? Is it ok that the settings and hotkeys aren't caught when I switch?
The rationale is two-fold.
1. In the process of adding the jack-in functionality, the connect to a running repl got a bit less reliable, and I didn't want to break someones workflow.
2. The old extension wasn't named
calva, which caused a bit of confusion, and I took the opportunity to fix that.
I will remove Legacy Calva when I have confirmed that people who can connect with that one, also can connect using the new Calva extension.
Some of my customized hotkeys don't work when I disable old plugin and enable new. Do I need to port them manually?
I am sorry for the confusion. It gets a bit extra bad with
Calva Paredit and
Calva Formatter. Have you uninstalled those as well?
Yes, they are now integrated. I have tried to make new Calva detect them, and tell you. But maybe that doesn't work for some reason.
start/end of an expression... those are by default
ctrl+cmd+right/left. If you are using a Mac.
I think marketplace page for the new plugin better have a quick overview of migration procedure
But generally the hotkey settings for old paredit are ignored and I need to reconfigure them?
I don't think your custom hotkeys for paredit should be affected by the switch. That sounds like a glitch. Don't they work, even after you have uninstalled old paredit?
It is a bit strange that you get those problems. New Calva usually detects those older extensions and informs the user. And custom hotkeys should keep working. This is the first time I hear about either of this happening.
I had install joker in wsl, is this right path ?
Sorry for not being able to answer that, @minhnhat10bk, I'm not a Windows user. Hopefully someone else here can help you.
Hey @cheatex it’s understandable that you are frustrated when things change and your dev environment breaks. But you should try to be a little more kind to the people who are doing all this hard work for free. Otherwise we wouldn’t have even a Clojure dev environment for VSCode.
Ctrl+Alt+C, Enter supposed to do the same as
use-ing the same ns?
I really appreciate all the work. To be clear I meant decisions to push the replacement via editor notification and not making clear it is incompatible. These are bad. It looked like "Ok, just press a couple buttons and I good to go".
For example, when figwheel switched to main it was clear "Hey, wanna spend a couple hours diggin wiki and playing with configs?".
@linkerfelix I don't know if it's exactly the same, but quite similar. It is using the nrepl op load-file. So check that to see exactly what it's doing. Any particular reason you wonder?
Yes, I can't use namespaces by just
Ctrl+Alt+C, Enter-ing them
I have to
use them first but after that, reloading them via they keycombo above works fine
@cheatex, it is supposed to be pretty much like 1. install new calva 2. get notified you should uninstall old calva extensions 3. do that 4. done I don't know why it didn't work that way for you, but I did try to be responsible about it.
Yes, it should probably be removed. But it will come back as more like a ”custom cljs repl setup”.
No worries. It'll be there till I've solved the problems with some connecting scenarios. Can you share a repro for the error?
1. Connect to existing repl
2. Select Figwheel.main, environment, open CLJS repl tab.
3. Call "Load current namespace" action. Nothing happens. Used to switch repl namaspace to ns of th ecurrent file.
4. Type in
(in-ns 'project.file). Still nothing happens, repl stays in
@<app state>. It's not known. Used to print the state atom.