zlacker

>>segfau+(OP)
I remind you, again, that vi, gcc, as, ld, and make have no telemetry, launch few (if any) processes, do not need GB of RAM, and work well.

>>dmitry+Jc
I am a die hard VIM user. VIM is a text editor, not an IDE. You can I many D tools into it's E, but it remains a text editor with disparate tools.

>>dotanc+3h
What is there in an IDE today, that is missing from (n)vim? With the advent of DAP and LSP servers, I can't find anything that I would use a "proper" IDE for.

>>63stac+Ji
- debuggers

- popup context windows for docs (kind of there, but having to respect the default character grid makes them much less capable and usually they don't allow further interaction)

- contextual buttons on a line of code (sure, custom commands exist, but they're not discoverable)

- "minimap"

>>virapt+Vj
Don't IDEs use DAP as well? That would mean neovim has 1:1 feature parity with IDEs when it comes to debugging. I understand the UI/UX might need some customization, but it's not like the defaults in whatever IDE fit everyone either.

Popup context windows for docs are super good in neovim, I would make a bet that they are actually better than what you find in IDEs, because they can use treesitter for automatic syntax highlighting of example code. Not sure what you mean with further interaction.

Contextual buttons are named code actions, and are available, and there are like 4 minimap plugins to choose from.

>>63stac+Zp
> That would mean neovim has 1:1 feature parity with IDEs when it comes to debugging.

How do I get a memory graph with custom event markers overlayed on it then? That's the default for VS for example.

>>virapt+xB
Sorry I don't know enough about VS to answer this, but if the debugger in question is using DAP then there is a more than fair chance it's available in neovim as well.