bfredl

> I think that we are agree, my main concern was some logical separation of libnvim and TUI. Sure, but it will be easier to discuss this as part of...

Eventually we might add some notion of a "default" server session, so one could just do `nvim --attach` to attach a TUI to it. To complement this there should also...

We need some documentation of the new features. The new _user facing_ feature is mainly `--connect` which should be mentioned in `starting.txt` just below `--listen` and also in `usage()` in...

Or maybe `nvim_ui_set_terminfo()` should just be merged into `nvim_ui_set_option()`. We can use options with a prefix, like `term_name`, `term_colors`, and `term_background`.

Regarding `FUNC_API_REDRAW`, we should probably change it to the reverse `FUNC_API_CLIENT_IMPL` with the same meaning of the old `FUNC_API_BRIDGE_IMPL`. A client wrapper will be auto-generated _unless_ - `FUNC_API_REMOTE_ONLY` is specified....

It will for 0.6

I'm working on rebasing this. Getting this fully merged will done for the 0.8 cycle (focus for 0.7 will be now be to stabilize already merged features, which are a-plenty),...

probably `buftype=prompt,nofile` should be allowed. Perhaps it can be suggested upstream?

`nvim_set_hl_ns` was renamed to `nvim__set_hl_ns` to indicate the API is not yet stable (it is going to change after 0.5.0, #13457 )

Tree-sitter was bumped from 0.18 to 0.19. This breaks ABI compatibility with tree-sitter parsers compiled for 0.18. https://github.com/nvim-treesitter/nvim-treesitter/pull/1000 will be needed to stay compatible. if you use tree-sitter both neovim...