You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The pyzo_in_leo plugin (or a new plugin) could inject code a full two-way comm bridge into pyzo, communicating with similar code in Leo. This would allow pyzo and Leo to run separately, but linked.
The comm bridge would provide Leonine commands for many pyzo functions.
The comm bridge would tell Leo what files are open in pyzo, and perhaps other data.
Simulating the minibuffer
To execute Leo commands, users would likely use pyzo Logger tool as a minibuffer.
Import leo somehow.
Add a convenience method (in pyzo) that would execute Leo commands by name.
Implementation
The comm bridge would likely use yoton, pyzo's ipc system.
The comm bridge might use MessagePack, the JSON-like tool used by neovim.
The text was updated successfully, but these errors were encountered:
This is a bad idea. The bridge would not be useful even if it existed.
See #1409 for notes common to all comm bridges.
The pyzo_in_leo plugin (or a new plugin) could inject code a full two-way comm bridge into pyzo, communicating with similar code in Leo. This would allow pyzo and Leo to run separately, but linked.
Simulating the minibuffer
To execute Leo commands, users would likely use pyzo Logger tool as a minibuffer.
Implementation
The text was updated successfully, but these errors were encountered: