> Implementing the emoji support took me years and that doesn't even count the rendering of them, just the ability to shuttle them through the internals and back. Tabs as well required quite a bit of work behind the scenes, there was an entire blog series written on the work that led up to tabs being possible.
I'm not trying to knock your efforts but wouldn't you say being able to use the mouse takes priority over things like this? Especially since your target audience is Windows users.
I could be totally wrong but every time I try out the MS terminal I get the impression that no one on the dev team uses it in their day to day because there's no way it could ship multiple times for years without mouse support otherwise.
I would say that emoji support takes precedence, because emoji support implies support for UTF-16 surrogate pairs. Originally the console could only support UCS-2 which could not represent all CJK characters. Adding surrogate pair support brought better functionality to a significant portion of the world's population. Emojis were only a (very visible) part of that feature.
Besides, the console does support the mouse. It's my understanding that mouse input events have been available for decades. I'm not sure where you're seeing problems with them.
I can guarantee that everyone on the dev team dogfoods their product.
> It's my understanding that mouse input events have been available for decades. I'm not sure where you're seeing problems with them.
Here's a narrated few minute video that shows how mouse events don't get passed through to the terminal (with or without tmux), and how they do get passed through using WSLtty using the same exact tmux and Vim configs for both environments.
> if you use tmux and have Vim open and try to click into Vim or any tmux window, nothing happens.
This means one of three things:
* tmux doesn't know to enable mouse reports, which will be almost certainly a TERM and terminfo configuration issue.
* The terminal emulator does not recognize the control sequences that turn on the various kinds of mouse reporting (DEC Locator, X10, Unicode rxvt, and ECMA-48-conformant XTerm).
* The terminal does not pass on mouse input events as mouse reports.
I shouldn't play the "mouse input events have been around for decades" card here, if I were you. DEC Locator reports precede anything relating to Win32, dating back to the VT220 in 1983. People could quite justifiably play the "Windows Terminal is not as good as a terminal from 1983" card in response. (-:
... and zamadatix did point to the known open issue on this. It's both the second and third items.
I'm not trying to knock your efforts but wouldn't you say being able to use the mouse takes priority over things like this? Especially since your target audience is Windows users.
I could be totally wrong but every time I try out the MS terminal I get the impression that no one on the dev team uses it in their day to day because there's no way it could ship multiple times for years without mouse support otherwise.