qtdomterm doesn't work with WSL about domterm HOT 4 CLOSED

There is also an extremely limited set of support for emojis. Rather than using a full color font fallback I see a small set (eg, 🙂 works but fire 🔥 does not). This looks to be some deep issues with QtWebEngine on X11 so I'm going to look into getting WSL working via Electron in Windows instead as this Qt route anyway won't end well.

from domterm.

"There is also an extremely limited set of support for emojis."

This depends on the font selected. This can be changed - see here

I did some experimentation recently, and noticed that some fonts had better Emoji support than others, without coming to a real conclusion about which is best. I noticed that Firefox seems to do a better job using colors for Emoji than Chrome-based browsers. I'm hoping the Firefox site-specific browser prototype soon becomes something we can use.

from domterm.

"the initial domterm creates a "domterm" (not qtdomterm) process which the second qtdomterm somehow makes use of."

Yes, it's slightly confusing. The qtdomterm application really only does the browser part of domterm. As a convenience, if you invoke qtdomterm OPTIONS (where OPTIONS does not include --connect) it basically just execs domterm --qt OPTIONS. The latter starts a server (if needed) and then opens a window with qtdomterm --connect URL (where URL points back to the server).

from domterm.

Closing this issue as won't be looking into the Qt version anyway anymore. Feel free to reopen if you want to track it!

from domterm.