[meatcar]

I just want to emphasize that wsltty is the only well-behaving terminal currently available for WSL. It's the only one that supports mouse interaction in a terminal like scrolling/resizing panes in tmux/vim, unlike any Microsoft solution.

If you're using WSL on a regular basis, I highly recommend it. Its a huge quality-of-life improvement.

[DHowett]

I am fairly certain that the inbox console host supports mouse interaction (with WSL and anything else that uses VT mouse mode). As the engineering lead for the console and terminal projects, though, I’d love to know how else we can improve!

[nickjj]

I noticed the same issues with tmux and the new MS terminal. The events got completely absorbed.

Also there were a bunch of "crazy" display issues, such as when minimizing the window about ~30% of the time the tmux status bar would become hidden.

Or after I exit tmux or even Vim sometimes without tmux, the terminal's background color would turn yellow (but not the entire terminal's background, just the characters where input / output would be legally able to be placed).

All of these things were discovered within about 2 minutes of using it, so these aren't edge cases. They happened very frequently, and things like the mouse just didn't work all the time.

Edit:

I just put together a 10min video showing a few of these display issues with the new MS terminal at: https://www.dropbox.com/s/puzbfs6ws4p8v7a/ms-terminal.mp4?dl...

The yellow screen issue never happened on video, maybe they fixed that but within 1 minute of using the terminal I found 2 new display bugs that weren't there when I tried it months ago.

Also sorry about the quality of the video. Drop box re-encodes videos at 720p (I recorded it at 1080p) and it looks like they are really strict with bitrates too. It looks slightly better than a potato, but you can still make out the display issues.

[zamadatix]

I'm not a terminal wizard but there is one bug that constantly happens in my workflow I'm not sure how to report: if I start a powershell session then ssh into a network switch and then access the serial TTY of a kvm guest running on the switch it sets the terminal size to particular dimensions (as expected). If I exit the serial connection then sometimes the terminal is never restored to normal size, even if I exit ssh back to the original powershell session.

Like I said very easy for me to reproduce but probably hard for you guys and I'm not sure what is breaking or how to capture the session to submit a bug.

.

Also it'd be amazing if profiles could include panes. I find myself almost in need of making an autohotkey script to break the terminal into 4 panes and launch particular ssh commands.

[andrewmackrodt]

wsltty loaded via ConEmu is the only acceptable terminal combination I've found for Windows, with support for mouse events, scrollwheel and remote terminal resize detection, e.g. ssh into another box and run a program like htop. I last tried microsoft/terminal about 6 months ago and found it incredibly broken.