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 }}
This repository has been archived by the owner on Apr 29, 2024. It is now read-only.
The initial implementation I tried many commits ago tried to use the socket path directly, but I was constantly failing. The reason was that I was missing the protocol, which, back then, was not documented / hard to find.
Yeah, it should probably be documented somewhere? I don’t see myself implementing this issue right away; I think we should benchmark to see whether using kak -p starts being a bottleneck, vs. directly writing to the socket.
The initial implementation I tried many commits ago tried to use the socket path directly, but I was constantly failing. The reason was that I was missing the protocol, which, back then, was not documented / hard to find.
Looks like it’s now doable. Context here.
The text was updated successfully, but these errors were encountered: