bfredl

> Non-blocking work must be done in a separate (python, in this case) thread. I don't think @cosven meant non-blocking as non-blocking when doing intensive CPU-work. Rather that it should...

Here is a stripped down example: ``` python import vim from threading import Thread from time import sleep import greenlet sleeping = None def wake_up(message): handler = sleeping handler.parent =...

With the latest changes we could change replace_termcodes to always return `bytes`

This repo is not really active developed. Maybe https://github.com/rliang/nvim-pygtk3 works better?

This is definitely doable, just someone needs to put in the work to either refactor the python-gui to a widget + a command line interface to accept the socket id...

IIRC @tarruda :s plan was to implement part of the event processing and what now is `screen.py` as a reusable c library (also used by the builtin TUI), so that...

Seems for a UI-side hover/balloon, core nvim would just need an API function which takes `(grid, row, col)` and gives back `(winid, rownr, colnr)`. This function already exists internally and...

> It's not clear how to clear 'msg_history_show' though, I'd assume it's 'msg_clear' but in the docs it says that it clears only messages shown by 'msg_show'. Currently nvim delegates...

Though `:set guifont=*` is already forwarded as-is by nvim core, i e `option_set["guifont", "*"]`, so a GUI could handle it like gvim if it wants to.

As it happens, we are planning to add nvim core support for this. Because with https://github.com/neovim/neovim/pull/10071 even TUI will use the "remote UI" protocol. Probably we will allow `nvim --embed`...