4 ms·
It runs the X server in the VM.
by eptcyka 4y ago
It runs the X server in the VM.
- Vogtinator 4y agoNot in this demo. It probably could though.
- csdvrx 4y agoThere's a X with sixel support: https://github.com/saitoha/xserver-sixel https://github.com/saitoha/xserver-sixel I played with this before, and I could use X11 within a mlterm terminal. I should try to recompile it with cosmopolitan to have a single X server binary both for Windows and Linux
- trenchgun 4y agoThat's amazing!
- csdvrx 4y agoAnd this is why I'm so interested in Sixel support for the Windows Terminal (https://github.com/microsoft/Terminal/issues/448 https://github.com/microsoft/Terminal/issues/448) With that and a X server using sixels, there would no longer be a need for something as complex as wslg for most apps: you could just export DISPLAY in your .bashrc, then use one Windows Terminal tab to start X apps, and the other one to display/interact with them.
- chrismorgan 4y agoIf the X server were running in the VM, how would it display things, or get keyboard and mouse input? You’d need to provide emulated hardware devices, which could be something like /dev/fb0 for output and /dev/input/ devices for keyboard and mouse. All that is a very much larger undertaking, and probably a good deal less useful in general. The likes of X are a much more suitable abstraction. The change here is implementing sendmsg and recvmsg: socket communications, implying communicating with something outside the VM, which in the context of GUI stuff almost certainly means an X server from outside.