quil

genmeblog 2020-05-12T11:49:42.027700Z

Just to give you ready to use setup: 1. Install Cygwin Xwin 2. On Cygwin terminal run: Xwin :0 -multiwindow -nowgl -ac -clipboard -listen tcp 3. On WSL1: export DISPLAY=:0 4. On WSL2: export DISPLAY=<windows IP>:0

neilyio 2020-05-12T15:10:47.030200Z

Over in #cider they explained to me that many Quil errors are being printed out in the repl because they're running on a background thread. That makes sense, I feel a little closer to having something else to Google now. Does anyone here have strategies for dealing with these background thread errors, or at least making them more prominent in your environment?

RollACaster 2020-05-12T17:25:07.031Z

I'm using https://cljdoc.org/d/quil/quil/3.1.0/api/quil.middlewares.pause-on-error so that errors get printed on the canvas

RollACaster 2020-05-12T17:28:37.031200Z

How did you bind the key to q/redraw? Since redraw requires bindings I get a NullPointer when trying to execute it on the repl

neilyio 2020-05-12T18:50:01.034100Z

Thanks @thsojka, I started with pause-on-error as well. My two major problems with it were 1. Sometimes I couldn't get it to restart after fixing an error, and I had to restart the whole applet. 2. I have the problem described in https://github.com/quil/quil/issues/232, where the error message is cut off in the applet. There didn't seem to be a resolution in the issue.

neilyio 2020-05-12T18:51:27.035Z

I'll try out safe-fns and see it I have any more luck. I'd love to hear about more setups that people are using!

neilyio 2020-05-12T20:35:00.036200Z

...I couldn't figure out safe-fns... The documentation isn't super clear on what exactly it does. How's it been helping you?