Axel Wagner

Okay, you are correct, I misattributed the problem; I ran into issues and tried to reproduce them on known-good output but didn't know it's not known-good :) There still is...

In general, no. The nbd driver has a fixed number of devices and pre-allocates the nodes in `/dev`. In general, they shouldn't be touched. When I say "destroy the device",...

Hm, while reusing code is certainly sensible (especially when looking at the complexity of i3-dmenu-desktop), this would make this feature of shellex only usable with i3 (or at least some...

That is a know consequence of 16eb076, the fix for #16. I am undecided on what the most annoying side-effect is. Another solution would to regrab the input focus after...

For a USB-connection, this would probably help. For a wifi-connection, AFAICT, the network becomes the bottle-neck without compression (and the CPU or context-switches or something becomes the bottleneck *with*). (edit:...

> reading the pen input buffering the events every say 1/10s and calculating the bounding rectangle of the coordinates of the event; This isn't really enough. The frame even occasionally...

I'm going to re-open this - not to say I'm actually going to do it myself, but because there's some useful new information to keep at hand for reference. Recently...

I'm not sure, I can only provide educated guesses: 1. A surprisingly large part of it is copying the framebuffer. I'm not sure why, but it takes a while to...

Thanks for the feedback :) It is to be expected that there is some background CPU usage even if the screen doesn't update. The reason is that as of now,...

- I don't like having to copy the file separately. It should really be embedded. - There's also no need to use `io.WriteString` - use `w.Write` directly. It saves an...