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.
Typing inside of the default WSL terminal feels amazing (2018)
51–60 of 123 posts
Re: Typing inside of the default WSL terminal feels amazing (2018)
#52> 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. You could say that a longer version of that answer is "Text Rendering Hates You": https://gankra.github.io/blah/text-hates-you/
[deleted]
Re: Typing inside of the default WSL terminal feels amazing (2018)
#53I'm curious how alacritty compares to it. The alacritty devs basically consider another terminal app rendering faster than them to be a bug on their part ;-) But it does sound like it would be a good challenge.
Alacritty has kind of a lot of input latency, it's noticeably worse than wsltty and the default WSL terminal -- at least back when I checked it a year ago. I think some work has been done to improve it, but at this point IMO if you're on Windows then wsltty is as good as it gets for a general purpose terminal. If you're on Linux, xterm is top notch.
What's top notch on Wayland?
Re: Typing inside of the default WSL terminal feels amazing (2018)
#54I'm a heavy WSL user, ever since I switched to Windows last year (after using MacOS for 6 years, and Linux before that). I must agree that typing is pretty responsive compared to other windows applications, but still nothing near the native experience. I also run clear linux natively on my laptop, and typing in that terminal is just faster.
[deleted]
Re: Typing inside of the default WSL terminal feels amazing (2018)
#55> 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 constant tax on latency. It would be great if applications had a “ascii” mode and a “full” mode. You can take the performance or the features, but you can’t have both.
Re: Typing inside of the default WSL terminal feels amazing (2018)
#56Re: Typing inside of the default WSL terminal feels amazing (2018)
#57 I was excited about WSL when I first heard about it. But that excitement quickly faded when I realized most real apps, such as gcc, don't work under it. The best way to get a Linux prompt on Windows is to use Docker. Use the -v option to share your drive.
Re: Typing inside of the default WSL terminal feels amazing (2018)
#58Earlier quoted context omitted.
Alacritty has kind of a lot of input latency, it's noticeably worse than wsltty and the default WSL terminal -- at least back when I checked it a year ago. I think some work has been done to improve it, but at this point IMO if you're on Windows then wsltty is as good as it gets for a general purpose terminal. If you're on Linux, xterm is top notch.
What's top notch on Wayland?
I never used Wayland, sorry.
Re: Typing inside of the default WSL terminal feels amazing (2018)
#59Too 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.
Yeah, that's why I switched to wsltty many many months ago. It has comparable input latency, good hotkey support, clickable URLs, unicode support, etc..
Re: Typing inside of the default WSL terminal feels amazing (2018)
#60I was excited about WSL when I first heard about it. But that excitement quickly faded when I realized most real apps, such as gcc, don't work under it. The best way to get a Linux prompt on Windows is to use Docker. Use the -v option to share your drive.
Most of those issues should be fixed with WSL2 given that it now uses a VM instead of syscall translation/emulation.