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
{{ message }}
Repository navigation
question: can I use r.sessionWatcher for non-vscode editors? #1470
The reusable R-side integration now lives in the bundled sess package. #1764 establishes explicit endpoint/discovery metadata and stable session IDs, so another editor could implement a client for that protocol and use sess::connect(endpoint = ...).
That still requires an editor-side implementation of the session handshake, JSON-RPC handlers, and the viewer/editor requests it intends to support. Installing sess or languageserver alone does not provide a ready-made Neovim/coc integration.
This answers the architectural part of the question; I have not verified a supported non-VS Code client.
Activity
renkun-ken commentedon Oct 6, 2026
The reusable R-side integration now lives in the bundled sess package. #1764 establishes explicit endpoint/discovery metadata and stable session IDs, so another editor could implement a client for that protocol and use
sess::connect(endpoint = ...).That still requires an editor-side implementation of the session handshake, JSON-RPC handlers, and the viewer/editor requests it intends to support. Installing
sessorlanguageserveralone does not provide a ready-made Neovim/coc integration.This answers the architectural part of the question; I have not verified a supported non-VS Code client.