9 Commits

Author	SHA1	Message	Date
Přemysl Eric Janouch	632ac992ab	xC/xP: only send buffer stats in the initial sync ... The client and frontends track these separately, there is no need for hard synchronization.	2022-09-10 17:38:33 +02:00
Přemysl Eric Janouch	8c3ee80b21	xC/xP: finalize and implement Event.PING	2022-09-08 02:45:37 +02:00
Přemysl Eric Janouch	3a165a595b	xC: use the relay protocol's RPC for pings	2022-09-08 01:48:46 +02:00
Přemysl Eric Janouch	4ba28c6ed3	xC/xP: mark highlights and buffer activity ... And more or less finalize out the protocol for this use case.	2022-09-08 01:28:51 +02:00
Přemysl Eric Janouch	2341228efd	xP: implement buffer line leakage ... Rather than on redisplay, these get cleared on reconnect.	2022-09-07 15:34:52 +02:00
Přemysl Eric Janouch	8cd94b30f6	xP: implement tab completion ... Currently it only goes for the longest common prefix. Refactor WebSocket handling into an abstraction for our protocol. The Go code generater finally needed fixing.	2022-09-06 19:41:05 +02:00
Přemysl Eric Janouch	31e9c6d2d5	xC/xP: pass timestamps with millisecond precision ... Future-proofing the protocol.	2022-09-06 14:39:01 +02:00
Přemysl Eric Janouch	d7b0b447b7	xC/xP: turn the action asterisk into a rendition	2022-09-05 23:22:09 +02:00
Přemysl Eric Janouch	1639235a48	Start X11 and web frontends for xC ... For this, we needed a wire protocol. After surveying available options, it was decided to implement an XDR-like protocol code generator in portable AWK. It now has two backends, per each of: - xF, the X11 frontend, is in C, and is meant to be the primary user interface in the future. - xP, the web frontend, relies on a protocol proxy written in Go, and is meant for use on-the-go (no pun intended). They are very much work-in-progress proofs of concept right now, and the relay protocol is certain to change.	2022-09-05 14:26:00 +02:00