Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Investigate asynchrous updates instead of RPC #18

wuub opened this Issue May 15, 2012 · 5 comments


None yet
2 participants

wuub commented May 15, 2012

Right now supervisor pokes each process every 0.2 seconds and also after sending any input event.
It would great if console_server.py just let console_client.py know when something changed on screen.


guillermooo commented May 16, 2012

I seem to remember you mentioned something about ZMQ. Any luck with that?


wuub commented May 16, 2012

I wanted to use zmq as a reliable and low latency channel for keypresses and screen upades. After some tinkering I was able to load zmq extension into sublime and create both Context and Socket, but once anything connected to this socket sublime crashed hard.


guillermooo commented May 17, 2012

I've been looking around and I can't find any "official" releases for Python 2.6. Were you using a driver for a different Python version perhaps?


wuub commented May 17, 2012

IIRC I tried both win32 and amd64 2.6 binaries from here https://github.com/zeromq/pyzmq/downloads (obviously with 32 and 64bit st2). I suspect that boost python might not be playing so well with C extensions compiled for standard cpython and/or st2 didn't like zmq's background IO thread.


guillermooo commented May 17, 2012

Shame. ZMQ looked like a good option and would make SublimePTY awesomer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment