shader

Yes, changing it suddenly would certainly break a lot of things. Surely it would be possible to mark the API as 'deprecated', change it to an alias for the new...

How hard would it be to make it so that older plugins can be built against a specific version of the plugin API? That would help, even if whoever is...

I think implementing something like that would require alternative neighborhood or tag views, that render nodes as a list or grid. The usual org html rendering can be used to...

I'm having the same problem; maybe a recent windows update that blocks it? It used to work.

Mine started working again after another update I think, though not reliably. Sometimes it doesn't work, but now a reboot can fix it.

No reason I can't show you my code; just pushed it to https://github.com/shader/precedence The instability bug appears in test_protocol_dead_end, and the tseitin issue appeared in test_protocol_unsafe when I changed consistent()...

I just re-cloned it myself and ran the tests successfully with `make parser` followed by `tox`; . I will note that my system python is 3.4.3. Also, I just pushed...

I have just observed this issue myself, and can consistently reproduce it by triggering a popup dialog (such as a "Save as..." popup) while the app is in a frame...

Well, I just spent an hour or two but couldn't get a truly minimal config working (couldn't get a minimal exwm config to work on my system for some reason)....

> What happens if you remove the `&`? I tried it; no difference. Good catch though.