Juan M Gómez

@arnetheduck > nimsuggest crashes on a lot of things it shouldn't crash on So let's hunt those down :) >but it would be nice if it also didn't give false...

ah, yes, probably I have a deps issue. Im just running nimsuggest waku.nim --v4 --stdin on it. But regardless the case (i.e. current version of chronos dont taking into account...

Should we treat it as a some sort of "special" package? As far as I can tell is defined as: ```json { "name": "compiler", "alias": "nim" }, ``` Without knowing...

> it would be nice if I could depend on compiler and not have to perform any "special" tricks like $nim/... What about adding a `path` option to the package...

I mean, right now `compiler` is defined as: ```json { "name": "compiler", "alias": "nim" }, ``` Im referring to expand the nimble functionality so when defined like so: ```json {...

Even if we should change the dep, I dont know the reason of the fork. This is in reality a `nimble` issue. If you can still repro it, please, submit...

Is this still an issue?

For the record, I removed it by mistake. But I do see the pain on downloading it every time, so my vote is to keep it as is for the...

Added it back. It seems I need to learn more about Nimble. I just wanted to update some deps, turned out it somewhat dumped my global Nimble folder when doing...

@miguelmartin75 we have a few ideas to approach the debugging situations but we dont know yet how we are going to tackle as the initial focus is in the nimlangserver/vscode...