71–80 of 123 posts
Too bad it doesn’t handle Unicode. Also it’s a shame that it doesn’t have tabs or any hot keys for increasing productivity. It’s really a good shell if you don’t have work to do.
Author of the GitHub issue here. I was surprised to see this title, because I thought "holy cow, finally someone else appreciates low input latency" and then I realized it was my issue haha. By the way, wsltty 3.x also has excellent input latency now too. I've been using it for quite a while now with terminal Vim in WSL and it's about 90% as good as xterm on native Linux in terms of latency. wsltty also has no issues…
Author of the GitHub issue here. I was surprised to see this title, because I thought "holy cow, finally someone else appreciates low input latency" and then I realized it was my issue haha. By the way, wsltty 3.x also has excellent input latency now too. I've been using it for quite a while now with terminal Vim in WSL and it's about 90% as good as xterm on native Linux in terms of latency. wsltty also has no issues…
It’s tempting to create a YouTube channel dedicated to showing input latencies for common tasks. Question is: how do you make sure no one is cheating?
It's funny, because I quit using WSL because of high latency. I can't say input latency is a big deal to me. I can always wait 100ms for the buffer to catch up with my typing. But when most commands have 500ms of overhead that is another story. My Xfce4 terminal running in a Hyper V VM is so much faster. If only there were seamless copy-paste. (Incidentally, I tried using Virtualbox but the latency there is more like…
Then you can launch GUI apps through your Hyper-V based VM (or any hypervisor).
It has seamless clipboard sharing that works out of the box once you enable the option.
I even went as far as running i3wm through VcXsrv for a while but ultimately gave that up since multi-monitor support didn't really work, but if you have 1 monitor it was actually quite usable.
Author of the GitHub issue here. I was surprised to see this title, because I thought "holy cow, finally someone else appreciates low input latency" and then I realized it was my issue haha. By the way, wsltty 3.x also has excellent input latency now too. I've been using it for quite a while now with terminal Vim in WSL and it's about 90% as good as xterm on native Linux in terms of latency. wsltty also has no issues…
If you're using WSL on a regular basis, I highly recommend it. Its a huge quality-of-life improvement.
I mean it may be great that the WSL terminal feels good, but if my program takes 2-5x slower in WSL for testing, I'm still going to opt for a hypervisor.
> Of course this also means that we have trade offs. We don't support fully international text like pretty much every other application will. RTL? No go zone right now. Surrogate pairs and emoji? We're getting there but not there yet. Indic scripts? Nope. I find it interesting that Even though I don’t care about any of the above features, I still pay for them working with text in other applications. They are a consta…
Author of the GitHub issue here. I was surprised to see this title, because I thought "holy cow, finally someone else appreciates low input latency" and then I realized it was my issue haha. By the way, wsltty 3.x also has excellent input latency now too. I've been using it for quite a while now with terminal Vim in WSL and it's about 90% as good as xterm on native Linux in terms of latency. wsltty also has no issues…
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.