Programming

17492 readers

45 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

108

Rider and Webstorm from JetBrains are now free for non-commercial use (blog.jetbrains.com)

submitted 4 weeks ago* (last edited 4 weeks ago) by [email protected] to c/[email protected]

49 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

If you're feeling bold, check out the NeoVim VSCode plugin. It's delightful.

It's essentially the VSCode remote plugin, but connecting to the NeoVim back-end.

It gives all the functionality of NeoVim along with all the functionality of VSCode.

Also, annecdotaly, it's substantially faster than the VSVim plugin.

[–] [email protected] 2 points 4 weeks ago (1 children)

I've had issues with that one because I'm using VS Codium flatpak. I've exposed system binaries and the extension found the nvim binary, yet it kept erroring out with the message that Nvim was disconnected. VSVim is better in that regard for my case, because it is a stand-alone extension.

[–] [email protected] 2 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

I saw an error like that, too. (Also with the flatpak.)

I want to say I had an error in my init.vim that was the underlying cause, and the error message cleared up once I had that fixed. I also had to make sure both executables were on my path, and I had to correct where the NeoVim plugin was looking for Nvim, as well, in settings.json.

[–] [email protected] 2 points 4 weeks ago* (last edited 4 weeks ago) (1 children)

I didn't have any errors in the init.vim file because I didn't have any. I added an example init.lua file with contents from here and configured the extension to pull this config file, yet it still says Nvim disconnected each time I restart it. I just gave up and resorted to VSVim

[–] [email protected] 3 points 3 weeks ago (1 children)

That makes sense. Did you also set the path to Nvim in settings.json? I had to do so to clear at least one error.

I also sometimes get that "disconnected" error too, but the have it work fine. I think there's a race condition and it raises the error right after it starts, but then connects anyway, once everything else is set.

[–] [email protected] 2 points 3 weeks ago

Did you also set the path to Nvim in settings.json? I had to do so to clear at least one error.

Yup. I set it to /run/host/usr/bin/nvim after exposing system libraries and binaries to VS Codium through KDE's flatpak permission manager. Prior to that it kept throwing me ENOF errors (or something like that, I don't remember now).

Unfortunately, that "disconnected" error is either not caused by a race condition for me or I was really unlucky, because at some point I restarted the extension 30 or some times out of frustration and nothing changed 😅