nvim-navic VS neo-tree-diagnostics.nvim

This can be done using a statusline plugin like nvim-navic

Zero-depency, yes, this is not another extension of navic. It does not even depends on nvim-treesitter or nvim-lspconfig, nor do you need to register an 'on_attach' function. as long as treesitter parsers or language servers are intalled correctly, the winbar should start working out of the box

nvim-navic. This option is particularly nice because it also enables using nvim-navbuddy which I have found incredibly useful for navigating large files.

Kudos for writing your first plugin! However, that's a rather poor name choice. There's already a neovim plugin called navi (https://github.com/mattiasbonte/navi.nvim), as well as an old unmaintained vim one (https://github.com/alexvoss/navi), not to mention slight variations like https://github.com/SmiteshP/nvim-navic or https://github.com/taohexxx/navim (the latter again looking unmaintained, but the former being relatively popular).

Just like this? If yes, you can try lspsaga.nvim, nvim-navic, or barbecue.nvim.

I also use ]m, but it’s not a very good way to choose and move to functions quickly and with intention. Options include aerial.nvim, symbols-outline.nvim, and the new nvim-navbuddy, from the developer who made nvim-navic.

Paired with my other plugin nvim-navic this completes the breadcrumbs experience that you would typically find in an IDEs like VScode. I hope you all like it :)

I use global status line (3) and winbar. I use Nvim-navic so that the winbar shows me my current file name highlighted also shows the path and the context.

Could also be https://github.com/SmiteshP/nvim-navic

I was trying to activate some optional plugin and found out that it couldn't be enabled using the mentioned config. I checked the github repository and saw that, for example, `SmiteshP/nvim-navic` is not present there. (link to core plugins list in repo).

One clarification: Neo-tree has been out for longer than a couple of weeks. 1.0 was released on Jan 1. It's neo-tree-diagnostics.nvim that has been out for a couple of weeks.

The excellent neo-tree.nvim recently added support for external sources, and, conveniently enough, I was working on a source for diagnostics around the same time. I've spent a bit of time polishing it, but I think I'm confident enough now to share it with you guys. Here's a link.

What native LSP gives you is an entire ecosystem of plugins that integrate with that built in LSP but would not work with CoC. I created a plugin called Neo-tree that includes a file browser that will show LSP diagnostic symbols next to files. There is also a brand new external source to show a diagnostic error list which is pretty nice: https://github.com/mrbjarksen/neo-tree-diagnostics.nvim