While this may be important towards the physical integration of the Qt pane that will be the gui frontend for the Neovim core, this doesn't need to be finished to start working on the "plumbing" that will need set up between Leo and the neovim core, e.g., nvim.exe.
The "plumbing" is msgpack calls to the neovim core and some msgpack calls from neovim to a as yet unwritten interface in Leo. For experiments you can just have Leo talk to a separately running instance of the stock Qt fronted Neovim. I think my first experiments with this were with juypyter notebooks, I was translating that work to leo files, not such what state that is in, but I'll attach those files. Tom -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
neovim_remote-api.leo
Description: Binary data
