upvote
btw I used iterm2 for years as well and sometimes tried others.

I now use ghostty it’s faster definitely. Yes it has some quirks which is hard to overcome as a iterm2 user. But I could live with it. I think ghostty is basically also the only alternative to iterm2

reply
While I'm not a hard core terminal emulator expert or tweaker, it was a bit of a learning curve to get into Ghostty after iTerm2. I hope this latest release makes it easier to edit the splits, haven't tested yet.

But the biggest thing that made me stay on Ghostty was that there's a freaking config file. With iTerm you had to export the profile and keybindings, and then import them on a new system which was clumsy, and easy to forget. Now ghostty.config is just one of my dotfiles, with a clear understandable git history, I love it.

reply
There's ~/Library/Preferences/com.googlecode.iterm2.plist and it's always been there
reply
Yup I switched to WezTerm from iTerm2 and being able to version control the settings is one of the biggest benefits (especially because WezTerm allows more complicated Lua scripts)
reply
Why put up with quirks when you have something that works for you? How much faster ghostty is in practical terms?
reply
I used iTerm and iTerm 2 for almost 20 years before switching to Ghostty full time in 2024 with minimal fuss besides the muscle memory of "cmd+space ite" switching to "cmd+space gho" to launch it!

Do you have specific examples of usability issues?

reply
My main issues with ghostty: the global shortcut for quick window suddenly stops working and works again only if I focus ghostty. (On a mac)

The other one is quick window goes out of the monitor if i have disconnected and connected the laptop from minitor.

Another: sometimes autocomplete suggestions are shown incorrectly in some weird location (like middle of the screen, not at the cursor), again occasionally.

reply
I actually fixed one cause of this, which is released in 1.4.0.

https://github.com/ghostty-org/ghostty/pull/12714

The only other cause I've encountered is if a secure input (password) field is focused, since macOS won't give apps global keyboard events for obvious reasons. If you focus a normal text input, it should start working again.

I have noticed where macOS doesn't properly release its reference to a Secure Input properly. I've documented how to determine if this is the cause here: https://github.com/ghostty-org/ghostty/issues/11883#issuecom...

reply
Aha, this explains why I've never seen this kind of thing: I don't use quick window!
reply
I'm happy with ghostty now too, but until a couple months ago it didn't have search. Which made me uncertain how people use terminals without built-in search. It really surprised me that it apparently was so low on the must-haves list that it took over a year to have it. I think I search terminals multiple times a day when I'm operating production systems.
reply
AFAICT, the bug from 1.3.1 where you cannot paste into the search field is still present in 1.4. I guess agents doing all the grepping these days?
reply