coc-ccls VS tree-sitter

I just did a fresh reinstall of CoC, on a newer version of Neovim. I'm now seeing something I hadn't seen before, which CoC calls "inlay hints". They look like this:

As recommended by michaelsbradley below, I installed https://github.com/nim-lang/langserver. I'm using coc.nvim (https://github.com/neoclide/coc.nvim) so I followed the instructions here from nim langserver https://github.com/nim-lang/langserver#vimneovim and seems to be working well!

Actually, I'm maintaining coc-perl (https://github.com/bmeneg/coc-perl), which enables the use of Perl LSP extension for vcode on vim/neovim using the CoC (https://github.com/neoclide/coc.nvim) backend. But it's completely on top of Perl::LanguageServer.

For vim specifically, I've been using coc.nvim, which works pretty well for my needs, and I know its quite popular. Another fairly popular one is YouCompleteMe, which I had taken a look at for some other languages; but ended up just using coc as I can't justify using YCM once a year (if that) -- too much "headache" for not a lot of use, you know?

Plug 'https://github.com/neoclide/coc.nvim' " Auto Completion

I do think VSCode is a great tool and I recommend it frequently to people, but I still want to set the record straight here. Yes, vim is obviously limited in the sense that as a CLI app it doesn't draw it's own PDF or HTML windows, that's fair. But it can remote control your favorite PDF viewer or browser for roughly the same functionality. I'm currently writing my thesis using vimtex and it's quite smooth. And all the other stuff you mention is implemented quite competently by various plugins like vim-fugitive, coc.nvim, vimspector and copilot.vim.

Sounds like you want vim-which-key and coc.nvim.

Another option is to just download https://github.com/neoclide/coc.nvim Which is basically a one stop shop for completion, and it's pretty fast, it just uses nodejs instead of built in nvim lua functions.

coc.nvim

dont over copy and paste example .vimrc, keep it simple and grow tooling as you use. for linting and code completion : https://github.com/neoclide/coc.nvim (easy to add languages)

Paste this into the Playground (try it here). You’ll get something like:

This code sets up a parser for Python code. The tree-sitter-python package provides a precompiled grammar, so no manual compilation is needed. If you’re targeting another language, check for its grammar package on Tree-Sitter Wiki.

The API is defined in tree_sitter/api.h (available on GitHub). It revolves around a few key concepts: parsers, trees, nodes, and queries. Let’s dive into the essentials.

Tree-sitter is a parser generator tool and an incremental parsing library, it is available in Rust 🦀 - GitHub. CocoIndex has built-in Rust integration with Tree-sitter to efficiently parse code and extract syntax trees for various programming languages.

I think the main problem is that highligthing framework used by tree-sitter (https://github.com/tree-sitter/tree-sitter/tree/master/highl...) is not easily pluggable into emacs font-lock-mode.

Although I am not certain if tree-sitter allows matching on comments, but https://github.com/tree-sitter/tree-sitter/issues/1138 seems to imply that it does

Hard agree. Even without going deep on a "serious language" there's a universe of DSLs that's mostly unexplored.

Debuggers are the outlier in your group but there's not exactly a void for those other wishes. As just one slice, building a tree-sitter [1] grammar gives the basis for good editor integration [2], formatters [3], structural diff [4] and other dev tools. Similarly if you're expressing some form of program, mapping to LLVM IR connects your creation with a fairly extensive compiler toolchain.

Language agnostic tooling exists, but there still needs to be some abstraction layer.

[1]: https://tree-sitter.github.io/

[2]: https://zed.dev/blog/syntax-aware-editing

[3]: https://topiary.tweag.io

[4]: https://difftastic.wilfred.me.uk

For those that want to explore the grammars listed at https://github.com/tree-sitter/tree-sitter/wiki/List-of-pars... in a more friendly railroad diagram format I made https://mingodad.github.io/plgh/json2ebnf.html that reads the "src/grammar.json" and try it's best to generate an EBNF understood by (IPV6) https://www.bottlecaps.de/rr/ui or (IPV4) https://rr.red-dove.com/ui where we get a nice navigable railroad diagram (see https://github.com/GuntherRademacher/rr for offline usage).

https://github.com/pragtical/plugins/commit/54096a6461f5c034... makes me long for The One Grammar To Rule Them ™

I thought for a while that TextMate bundles[1] were that, especially since JetBrains[2], Linguist[3] and VSCode[4] honor them. However, in the spirit of "the good thing about standards ..." highlight.js does[5] almost the same thing that Pragtical does which makes me feel even worse

I had high hopes for Tree-Sitter since it seems to have really won mindshare, but the idea of having an executable grammar spec[6] is ... well, no wonder it hasn't caught on outside of that specific ecosystem

1: https://github.com/rspec/rspec.tmbundle/blob/1.1.12/Syntaxes...

2: https://github.com/JetBrains/intellij-community/blob/idea/24...

3: https://github.com/github-linguist/linguist/blob/v7.30.0/lib...

4: https://github.com/microsoft/vscode-textmate

5: https://github.com/highlightjs/highlight.js/blob/11.10.0/src...

6: https://github.com/tree-sitter/tree-sitter/blob/v0.22.6/test...

If you like to see some examples of C bindings:

https://github.com/tree-sitter/tree-sitter/blob/25c718918084...