calva

Wednesdays you might find @U0ETXRFEW in the Gather Calva space. Invite is https://gather.town/invite?token=GZqrm7CR and the password is `Be kind`.
borkdude 2021-01-07T13:28:59.203400Z

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

mauricio.szabo 2021-01-08T11:42:05.231500Z

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

borkdude 2021-01-07T13:30:34.203800Z

(https://github.com/clj-kondo/clj-kondo.lsp/issues/13)

ericdallo 2021-01-07T13:32:59.204300Z

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

ericdallo 2021-01-07T13:34:04.204700Z

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

pez 2021-01-07T13:34:36.205400Z

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

borkdude 2021-01-07T13:36:07.207400Z

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

pez 2021-01-07T13:37:25.209300Z

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.

pez 2021-01-07T13:38:24.210300Z

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

pez 2021-01-07T13:39:43.210400Z

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
borkdude 2021-01-07T13:42:17.210800Z

ok, oh well. https://github.com/EclipseFdn/open-vsx.org/issues/292

borkdude 2021-01-07T13:43:40.211100Z

ok, signed

😄 2
pez 2021-01-07T13:57:56.211500Z

Nice! That’ll take care of this:

pez 2021-01-07T13:59:36.212700Z

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

1
🆒 2
borkdude 2021-01-07T13:59:37.213Z

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

pez 2021-01-07T14:00:13.213200Z

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

borkdude 2021-01-07T14:00:23.213400Z

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

borkdude 2021-01-07T14:00:31.213600Z

hmm

borkdude 2021-01-07T14:00:34.213800Z

whatever

borkdude 2021-01-07T14:01:15.214Z

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

borkdude 2021-01-07T14:01:26.214200Z

or I guess that's too late already

borkdude 2021-01-07T14:01:39.214400Z

since people are already subscribed to this namespace

borkdude 2021-01-07T14:01:52.214600Z

fine

pez 2021-01-07T14:01:59.214800Z

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.

pez 2021-01-07T14:02:54.215Z

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

borkdude 2021-01-07T14:03:02.215200Z

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

borkdude 2021-01-07T14:03:22.215400Z

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

borkdude 2021-01-07T14:03:31.215600Z

but I guess we'll keep this as a heritage

pez 2021-01-07T14:04:14.215800Z

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

pez 2021-01-07T18:53:52.218500Z

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
gabo 2021-01-07T19:18:49.218900Z

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

❤️ 1
bringe 2021-01-07T20:52:02.222400Z

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.

1
bringe 2021-01-07T20:52:55.223200Z

Thanks to @ericdallo for the classpath issue fix

1
😉 1