Tooling update

Because we chose to fork the one that was actually written in Nim

Tooling update

Why not continue with Konstantin Zaitsev?

Tooling update

Report the issue in the extension repo please () so we can troubleshot. Also specify the version of the `nimlangserver` you have installed by running `nimlangserver -v`

Tooling update

Unfortunately I got the same error.

Tooling update

I'm having some trouble with the new version on Windows. Here's what I did to upgrade: 1. Deleted the `.nimble` folder from `users` 2. I took the latest devel release (2024-07-25), replaced the old installation (2.1.1) 3. I ran the `finish.exe` 4. Verified that the Nim version is 2.1.9 a

Tooling update

> I thought perhaps the problem might be that the build requires the latest > version of nimble. This brings me to the second problem - the latest nimble > release binaries do not include a 64-bit version for Linux. For some reason the upload failed, should be up now. > Am I correct in assuming

Tooling update

Nice! Will this version of the extension be in the VSCodium/VSX extension marketplace? :)

Tooling update

Many thanks for the updates! However, there are a couple items of concern. First, when I pulled the latest `vscode-nim` code from github, it refused to build (nim v2.0.8): [~//vscode-nim]$ nimble vsix Verifying dependencies for nimvscode@1.0.0 Executing task vsix in

Tooling update

Thanks for the hard work!

Tooling update

just moved the newly compiled `nimble.exe` from `.../.nimble/pkgs2/...` to `.../.nimble/bin` All fine.

Tooling update

Will the next release of Nim 2.2.0 include Nimble 0.16.0 ?

Tooling update

You can also download the `nimble` binaries from the release page (I just updated it). It will also be shipped with the next Nim release. `nimble install nimble` Likely the `nimble` you still have in your path is the old one but I agree that it should be enough and same for switching `nim` vers

Tooling update

> Will the next release of Nim 2.2.0 include Nimble 0.16.0 ? Yes.

Tooling update

.Sorry if this question is obvious, but how do you update nimble independently of nim? install nimble Run it said it installed nimble@0.16.0, but nimble -v Run results in nimble v0.14.2 compiled at 2024-07-03 01:22:18 git hash:

Tooling update

Thanks a lot for your hard work on nim's tooling. I think this is one of the most important things that can be done to make nim more popular and even more pleasant to use. Sorry if this question is obvious, but how do you update nimble independently of nim? Or should we simply do a `choosenim u

Tooling update

We are pleased to announce that new versions of `nimlangserver`, the `nim-lang.org` VSCode extension, and `nimble` have been released. We have reworked the project discovery in `nimlangserver` to better handle `nimsuggest`. It now uses `nimble dump` to select the `nimsuggest` version and determ

Tooling update

Great work! 👏 Thanks for leading the effort there and for the update! 🙏

Tooling update: new version of the nimlangserver and the vscode extension

a simple matter, yes, but one that has been haunting all choosenim + nimsuggest users since 2019 the problem is proxyexe.nim not proxying enough

Tooling update: new version of the nimlangserver and the vscode extension

It's a simple matter of killing the process group and not just the proxies -

Tooling update: new version of the nimlangserver and the vscode extension

Couldn’t choosenim on windows just create a junction to the folder containing the selected nim version binaries instead of using those problematic proxy executables?

Tooling update: new version of the nimlangserver and the vscode extension

all the issues I had with vscode went away by removing choosenim just let nimlangserver call nimsuggest directly and not via the proxy exe generated by choosenim

Tooling update: new version of the nimlangserver and the vscode extension

Works like a bliss on Ubuntu 23.10. Thanks @jmgomez VScode: Version: 1.87.0 Electron: 27.3.2 ElectronBuildId: 26836302 Chromium: 118.0.5993.159 Node.js: 18.17.1 V8: 11.8.172.18-electron.0 OS: Linux x64 6.5.0-21-generic snap Run

Tooling update: new version of the nimlangserver and the vscode extension

Im glad it works fine for you, some people seem to still have issues with it but it seems we are getting there. But we should also thank @nickysn as he is doing an amazing work and the whole community, especially those that bother enough to report issues :)

Tooling update: new version of the nimlangserver and the vscode extension

This page needs an update now: > ## What about editor support? > Visual Studio Code: > Extension written in Nim https://marketplace.visualstudio.com/items?itemName=nimsaem.nimvscode > Original Extension written in TypeScript https://marke

Tooling update: new version of the nimlangserver and the vscode extension

Wow, I just pulled up some test code and saw the new type inlays! Shout out to the guys working on the tooling. It just magically appeared.

Tooling update: new version of the nimlangserver and the vscode extension

I upgraded to Nim 2.0.2 and added the files to "nim.project" in $PROJECT/.vscode/settings.json and now it works. And it includes multiple symbols for procs with same name and different signature. This is a big improvement over the other extension I used before. Thank you so much. I'll probably

Tooling update: new version of the nimlangserver and the vscode extension

thx. I'll try to reproduce it in a clean installation with only this extension and report it if I can.

Tooling update: new version of the nimlangserver and the vscode extension

wait a second is it [nim.project](https://github.com/search?q=repo%3Anim-lang%2Fvscode-nim%20nim.project&type=code) or [not](https://github.com/search?q=repo%3Anim-lang%2Flangserver%20nim.project&type=code)? nimlanggserver project doesn't contain `nim.project`, but `vscode-nim` does. Could yo

Tooling update: new version of the nimlangserver and the vscode extension

@gcao, Ctrl-Shift-O works for me under Linux. I doesn't say "No editor symbols". Instead it shows a list of symbols. So, it's supposed to work. Please report an issue with detailed steps on how to reproduce: In the bug report, please provide a

Tooling update: new version of the nimlangserver and the vscode extension

hi I've tried to use the official extension a few times but was having issue get symbols to work. Means when I press Cmd-Shift-O to open symbols view, it just says "No editor symbols". The other two Nim language server extension works at least partially (when there are multiple procs with same n

Tooling update: new version of the nimlangserver and the vscode extension

@BLeAmz, that depends on your "nim.projectMapping" configuration setting. See: How does yours look like?

Tooling update: new version of the nimlangserver and the vscode extension

sure! Thanks, as suggested, I've prepared a new issue here

Tooling update: new version of the nimlangserver and the vscode extension

It happens that there're nimsuggest processes for each Nim file I open, even though I've set nim.project to only one file, such as: ["src/main.nim"], is it the expected behavior?

Tooling update: new version of the nimlangserver and the vscode extension

Hi, @giaco. Can you check that your nimlangserver is the new version (running "nimlangserver -v" from the command line should print the version, if it's the new version), and that it's the only nimlangserver binary and it's in the PATH? If you're sure it's the new version, please file a bug repo

Tooling update: new version of the nimlangserver and the vscode extension

upgraded but same problem as before. For example I have project with 2 targets: JS frontend (karax) and C backend, using this `.vscode/settings.json` { "nim.project": [ "src/back/back.nim", "src/front/front.nim" ], } Run When

Tooling update: new version of the nimlangserver and the vscode extension

Thanks to all the devs and sponsors behind this effort I've been a pro on triggering this so far `fixed issues with remaining nimsuggest and nimlangserver processes after improper shutdown from the LSP client` Hope this release will stop my process killing spree

Tooling update: new version of the nimlangserver and the vscode extension

Congrats on the release. Now I can abandon Konstantin Zaitsev's vscode extension, because after this round of improvements to the official extension, it works perfectly even when opening a random .nim file, without the need to open a folder.

Tooling update: new version of the nimlangserver and the vscode extension

CodeLLDB is the recommended one. Probably we will end up making it a dependency of our extension. Notice there is an option to define the default target (`lldb`) called `nim.debug.type` so you can use another extension if you want. type of debugger to use when using Nim: Debug sele

Tooling update: new version of the nimlangserver and the vscode extension

When I try to use the debug the current nim file command it tells me that I need to install an LLDB extension first. Is there one that is recommended? I see one called "LLDB VScode" and another called "CodeLLDB"...

Tooling update: new version of the nimlangserver and the vscode extension

We are pleased to share that a new version of the nimlangserver and the nim-lang.org vscode extension have been released. The focus of the releases have been bug fixing and making a foundation to build upon. We are quite excited about resuming the work on the vscode-extension and there are a f