Fork me on GitHub
#calva
<
2021-01-07
>
borkdude13:01:59

Open VSX <- does anyone use this? I just got an issue that the clj-kondo extension will be delisted unless I change a license

ericdallo13:01:59

Never heard about that Eclipse VSCode marketplace extensions, but I know that Eclipse org is annoying with signing stuff... I needed to sign too to contribute to https://github.com/eclipse/lsp4j

ericdallo13:01:04

For this project ☝️ it's all online and fast to sign at least

pez13:01:43

Yeah, its all online and fast for OpenVSX too. And I think I can forgive them for the paperwork. So many license trolls out there.

👍 1
borkdude13:01:40

ok, signed

😄 2
sogaiu07:01:14

fwiw, something similar showed up in @U3Y18N0UC’s clover repository: https://github.com/mauricioszabo/clover/issues/21

mauricio.szabo11:01:05

Oh, I never saw that issue. I signed because they sent me an e-mail recently...

pez13:01:36

It seems like they want you to add a licence, not change it?

borkdude13:01:07

This feels like paperwork to me. If nobody is using this Eclipse stuff... I'll just get it delisted at look at it later ;P

pez13:01:25

Regardless. I think it is worth keeping our extensions there. There are quite a few VS Code-“compatible” editors out there already, and the numbers are growing. Sadly Calva doesn’t work with the ones I’ve tested so far. But your extension works on most I think, @borkdude. I have made the changes and signed the agreements, anyway. I plan to find the time to figure out how to make Calva work in Theia and Gitpod at the very least.

pez13:01:24

Yeah, since they say you can enlist at anytime, you can probably wait. But I bet you have users there.

pez13:01:56

Nice! That’ll take care of this:

borkdude13:01:37

Oh crap, I'm using the namespace borkdude...

pez14:01:13

Ah, good catch. That’s a nice namespace though, right?

borkdude14:01:23

I can change it to clj-kondo, I think that's nicer

borkdude14:01:15

I will change it in the issue and will claim the namespace clj-kondo some other time

borkdude14:01:26

or I guess that's too late already

borkdude14:01:39

since people are already subscribed to this namespace

pez14:01:59

You’ll lose the history on the vscode marketplace. I changed namespace once because I felt it was necessary, but it cost some 100k download count.

pez14:01:54

And some 25 five-star ratings. And it has taken us a while to rebuild that.

borkdude14:01:02

yeah, I'll leave it like this then. It's not as nice as github

borkdude14:01:22

I just moved clj-kondo to its own org a week ago

borkdude14:01:31

but I guess we'll keep this as a heritage

pez14:01:14

Yeah, the VSIX package namespace isn’t all that visible anyway. And it is quite beautiful legacy, IMO.

pez13:01:36

On my laptop Calva is above the fold on the open-vsx start page. Too bad it doesn’t work in Theia and Gitpod though. 😃

🆒 2
calva 1
pez18:01:52

Thank you, Gabriel! This is the kind of fuel that keeps me going. I showed this to my family, and they are just so happy on my account. ❤️

❤️ 4
gabo19:01:49

It's really inspiring seeing the effort you and everyone behind calva put in the project. It's the least I could do 😄

❤️ 1
bringe20:01:02

I released version 2.0.147 and 2.0.148 today, which include the following noteworthy changes: • Fix: https://github.com/BetterThanTomorrow/calva/issues/908 • Update clojure-lsp to version 2021.01.07-20.02.02 This includes a fix that should make clojure-lsp work better by default on Windows, without needing to add/modify your .lsp/config.edn file. Before, the classpath lookup was failing on Windows probably in most cases, resulting in some features being broken. Also if the classpath lookup by clojure-lsp does fail, you'll see an error notification so you know immediately what went wrong.

hyper-clap 1
bringe20:01:55

Thanks to @ericdallo for the classpath issue fix

1
😉 1