On Wed, Apr 8, 2020 at 10:58 AM gar <[email protected]> wrote: Well strange to hear it from you. > Actually Leo panes are vim's buffers. And all of them can be directly > mapped one to another. Like some IDE plugins for vim do. >
Yes, I understand that. Let me try to explain what I *think *the problem is. Suppose we had a bridge between neovim and Leo. That bridge would be a neovim plugin, presumably written in python. Actually, the details don't matter. Well, what would the bridge do? My guess is that Leo would intercept keystrokes (in Leo's body) and send them across the link to neovim, which would then update vim's buffer and send (somehow) the results back to Leo, which would then update Leo's body pane. That's a *lot* of work to do on each key stroke! Furthermore, Leo's environment is a lot more complex than neovim's. So some keystrokes can't be sent to neovim, because they mean something to Leo. > So I do continue to use Leo GUI which is hard to configure, slow and need > to be restarted for every little tweak. > I suspect that the bridge scheme described above will be slower. I have to use very outdated syntax highlight schemes for most languages I > use! pygments are claimed to be supported but works with python only. > Updating Leo's syntax coloring probably is a separate issue. > Also there are many vim enthusiasts which like to make plugins for 3rd > party goodies. But for leo it's not possible for now since it is too closed. > The "Won'tDo" label means that *I* won't do it. Any Leo user is welcome to create their own plugin. > The same with emacs I believe. > Leo already supports the pymacs bridge <http://leoeditor.com/emacs.html#controlling-leo-from-emacs-using-pymacs>. Any emacs guru is welcome to create another kind of emacs bridge. Again, *I* am not going to do that, but I would welcome contributions. > I could write more arguments but stop here cause english is not my > native language and I am tired :-) But hope I told enough to be my voice taken > into account. > You have explained yourself very well. If you have ideas for a vim bridge I would be glad to study them. The main point I am trying to make is that all bridges between Leo and another editor should be done by those who actually use the other environment. If you would like to create a bridge between Leo and neovim I would be happy to help in any way I can. Edward -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS18dRY5DANzfsyUPgHSWAB9%2BN--fcaM7hvmOM4NRZwJKA%40mail.gmail.com.
