It's interesting that none of the programs commonly known as "terminal emulators" actually emulate a terminal.. we can do that now though. https://zork.net/~st/jottings/Real-VT102-emulation-with-MAME... I would avoid doing the PTY thing and instead do this (works on WSL if MAME is the windows version): $ sudo socat TCP-LISTEN:1234,reuseaddr,fork EXEC:"/sbin/agetty -L - 9600 vt102",pty,setsid,ctty,stderr $ mame -nomou…
State of Terminal Emulators in 2025: The Errant Champions
151–160 of 283 posts
Re: State of Terminal Emulators in 2025: The Errant Champions
#152The terminal that comes with macOS version ends on the 29th place in the results.
Yeah… Apple hasn't done much with Terminal.app since they inherited it from NeXT back in the late '90s. FWIW, it did get Powerline support and 24-bit color in macOS 26.
Re: State of Terminal Emulators in 2025: The Errant Champions
#153Terminal emulators are caught between emulating terminals and teletypes of the past and implementing new features and unicode is one of the struggles. The way most terminals and wcwidth handle the width of characters sometimes is not correct but preserving behavior is important for compatibility. It is possible that its just not worth trying to handle all unicode perfectly in a terminal. Its pretty good for legacy st…
Re: State of Terminal Emulators in 2025: The Errant Champions
#154Work had me using the Windows Terminal for the first time ever after a life of developing on Linux. I got immediately hooked on the smart Ctrl+C and Ctrl+V (without needing to use Shift like on Linux!) For those not knowing, Windows Terminal uses Ctrl+C to abort the current process (as we'd expect) when nothing is selected , but copies when there is a selection. Similarly, Ctrl+V just pastes. So convenient!
Mac terminals yield a similar benefit, with the systemwide copy/paste Cmd+C/V not overlapping with Ctrl+C/V. Being used to that, Linux terminals become rather annoying. Yes there's other ways under Linux, but they don't have 25+ years of muscle memory associated with them, and so when the key shortcuts don't work as expected it's like nails on a chalkboard.
However, for most all other applications in Mac, I dislike the Mac command key. Especially in IDEs like vscode, etc.
And I really hate that the actual Ctrl key on a Mac is in the wrong place, having swapped places with Fn. It's like the first thing I have to remember to do on each Mac setup, swap those two keys.
Because I'm toggling between mac/windows/linux all day long, my poor muscle memory is always confused. And it would be nice if this could be unified. Unfortunately, I'm guessing it would have to be solved more by Apple than by Microsoft or Linux.
Re: State of Terminal Emulators in 2025: The Errant Champions
#155Work had me using the Windows Terminal for the first time ever after a life of developing on Linux. I got immediately hooked on the smart Ctrl+C and Ctrl+V (without needing to use Shift like on Linux!) For those not knowing, Windows Terminal uses Ctrl+C to abort the current process (as we'd expect) when nothing is selected , but copies when there is a selection. Similarly, Ctrl+V just pastes. So convenient!
> I got immediately hooked on the smart Ctrl+C and Ctrl+V (without needing to use Shift like on Linux!) You, uh, never tried middle clicking?
Re: State of Terminal Emulators in 2025: The Errant Champions
#156Earlier quoted context omitted.
Heh, shortcut muscle memory is the reason I returned my Mac mini one week after trying it. I sure am not gonna remap my brain for apple after 20 years of Linux and windows.
It's easy and reasonably quick to set up key remapping (via Karabiner).
So yes keyboard remapping is an option. But there's just differences you can't remap because of the extra meta keys on Mac (and I guess on Windows too, with the Copilot or Start keys in play).
Re: State of Terminal Emulators in 2025: The Errant Champions
#157Work had me using the Windows Terminal for the first time ever after a life of developing on Linux. I got immediately hooked on the smart Ctrl+C and Ctrl+V (without needing to use Shift like on Linux!) For those not knowing, Windows Terminal uses Ctrl+C to abort the current process (as we'd expect) when nothing is selected , but copies when there is a selection. Similarly, Ctrl+V just pastes. So convenient!
Are there any legitimate reasons to send Ctrl-C except to abort, that this could interfer with?
Re: State of Terminal Emulators in 2025: The Errant Champions
#158Work had me using the Windows Terminal for the first time ever after a life of developing on Linux. I got immediately hooked on the smart Ctrl+C and Ctrl+V (without needing to use Shift like on Linux!) For those not knowing, Windows Terminal uses Ctrl+C to abort the current process (as we'd expect) when nothing is selected , but copies when there is a selection. Similarly, Ctrl+V just pastes. So convenient!
In Linux (Wayland) you can copy text from the terminal without pressing Ctrl+C at all. Just select the text. To paste it in another Window, press the middle mouse button. This is called the Primary Selection and is separate from the Clipboard (Ctrl+C/Ctrl+V). IMO the Primary Selection is more convenient than the Clipboard.
Re: State of Terminal Emulators in 2025: The Errant Champions
#159Re: State of Terminal Emulators in 2025: The Errant Champions
#160Work had me using the Windows Terminal for the first time ever after a life of developing on Linux. I got immediately hooked on the smart Ctrl+C and Ctrl+V (without needing to use Shift like on Linux!) For those not knowing, Windows Terminal uses Ctrl+C to abort the current process (as we'd expect) when nothing is selected , but copies when there is a selection. Similarly, Ctrl+V just pastes. So convenient!
Not sure if this was available from the beginning, but Ghostty has the ability to do exactly that with what they call "performable" keybindings https://ghostty.org/docs/config/keybind#performable: >