Fork me on GitHub
#calva
<
2019-06-20
>
cheatex10:06:38

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?

cheatex10:06:39

Sorry if it's inappropriate place for the questions.

pez10:06:54

Hello, @cheatex, this is a perfectly appropriate place for the questions!

pez10:06:27

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.

pez10:06:07

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.

pez10:06:49

Not sure what the question about settings and hotkeys is about. Can you elaborate some?

cheatex10:06:23

Some of my customized hotkeys don't work when I disable old plugin and enable new. Do I need to port them manually?

pez10:06:07

Can you give me an example?

pez10:06:24

I am sorry for the confusion. It gets a bit extra bad with Calva Paredit and Calva Formatter. Have you uninstalled those as well?

cheatex10:06:09

Moving cursor to start end of an expression not working

cheatex10:06:35

Nope. Are they integrated into new calva? Do I need to disable them too?

pez10:06:29

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.

pez10:06:20

start/end of an expression... those are by default ctrl+cmd+right/left. If you are using a Mac.

cheatex10:06:41

I'll try again with all older plugin disabled

pez10:06:30

Hmmm, wait, I think I have messed something up there...

cheatex10:06:19

I think marketplace page for the new plugin better have a quick overview of migration procedure

pez10:06:23

Yes, I'll consider that.

pez10:06:34

Are you using Mac or something else?

cheatex10:06:50

Linux + MATE

pez10:06:58

What's MATE?

cheatex10:06:23

Desktop, recent remake of gnome 2

pez10:06:42

Thanks. What would your preferred keybinding for forward and backward sexpr be?

cheatex10:06:07

Just Ctrl+Arrow probably. But its personal, I'm very unexperienced paredit user

pez10:06:49

That's now occupied by slurp/barf forward... I agree it's personal preferences.

pez10:06:27

Calva will now use ctrl+alt+left/right for moving to start/end of sexpressions.

cheatex10:06:53

But generally the hotkey settings for old paredit are ignored and I need to reconfigure them?

cheatex10:06:53

Also, is there an option to disable that parens coloring thing?

pez10:06:16

Yes, those are configured via Clojure Warrior.

cheatex10:06:27

Whats that?

pez10:06:45

It's an extension. Search for Clojure Warrior in settings.

pez10:06:10

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?

cheatex10:06:42

Its so fucking irresponsible

pez10:06:47

Seems broken.

cheatex10:06:48

Sorry to say this

cheatex10:06:13

Just hour of time with precisely 0 added value

pez10:06:40

Hmmm, what is hour of time?

cheatex10:06:20

Getting my perfecty working dev environment back to usable state

pez11:06:16

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.

minhnn11:06:49

I had install joker in wsl, is this right path ? "calva.jokerPath": "\\home\\linuxbrew\\.linuxbrew\\bin\\joker",

pez11:06:07

Sorry for not being able to answer that, @minhnhat10bk, I'm not a Windows user. Hopefully someone else here can help you.

minhnn11:06:31

when I lint current file, It prompt this error

pez11:06:04

Do you have a clojure file opened, and get that error?

pez11:06:26

I can reproduce it. Will check what's going on. Please file an issue about it.

orestis12:06:52

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.

Felix Linker12:06:05

Is Ctrl+Alt+C, Enter supposed to do the same as use-ing the same ns?

cheatex12:06:04

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".

cheatex12:06:32

For example, when figwheel switched to main it was clear "Hey, wanna spend a couple hours diggin wiki and playing with configs?".

cheatex12:06:56

Sorry again

pez12:06:57

@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?

Felix Linker12:06:34

Yes, I can't use namespaces by just Ctrl+Alt+C, Enter-ing them

Felix Linker12:06:59

I have to use them first but after that, reloading them via they keycombo above works fine

pez12:06:03

Do you get any errors?

pez12:06:49

Yeah, sounds strange. I

pez13:06:20

@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.

pez13:06:58

And people here helped with testing that the upgrade should be smooth.

cheatex13:06:31

The 'calva.startCLJSREPLCommand' option is now ignored, right?

pez13:06:00

Yes, it should probably be removed. But it will come back as more like a ”custom cljs repl setup”.

cheatex13:06:04

And I still can't get repl working

cheatex13:06:23

Bright side, after switching back to the old plugins everything works 🙂

cheatex13:06:14

Guess I can only ask to keep the old extensions on market.

pez13:06:55

No worries. It'll be there till I've solved the problems with some connecting scenarios. Can you share a repro for the error?

cheatex13:06:05

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 cljs.user 5. Type @<app state>. It's not known. Used to print the state atom.

pez14:06:08

Hmmm, is the file active (has focus) when you load the namespace?

cheatex18:06:45

I'll retry on my second machine tomorrow