671–680 of 719 posts
I’ve been using Ghostty for a day now and it simply works. Smooth, seamless and perfectly integrated to the point where this should just be the default terminal in macOS.
P.S.: If you want to port your iterm color scheme, set:
window-colorspace = display-p3
for the colors to match.
(And bold-is-bright = true if you set this option in iterm)
Many people here seem impressed about speed/performance. I have been using all sorts of terminals / emulators over the past 20 years and it never occurred to me a terminal can be slow. When I type a command, I just get the result instantaneously, for any terminal. What are the use cases that can make a terminal be slow?
A commenter in this thread mentioned sifting through log / debug output… but why wouldn‘t you pipe it to a file instead?
This feels like the Vagrant moment [1] again. Cant believe 15 years have passed already. Together with Bun I believe that is two high profile open source software made with Zig. [1] https://news.ycombinator.com/item?id=1175901
Earlier quoted context omitted.
That's a great approach. Not sure on the current state of Alacritty, but a few years back the suggested solution for users interested in battery performance was to switch to a different terminal emulator: https://github.com/alacritty/alacritty/issues/3473#issuecomm...
I, a person who don't care about battery performance one iota (because my computer has no battery), love this answer and approach. Not every software is for everyone, and authors drawing a line in the sand like that works out better for everyone in the long-term, instead of software that kind of works OK for everything.
Cherry on top is me being a former user of a MBP 2010 who'd crash when using discrete GPU (it was _the_ reason Apple went with AMD later on). And some apps insisted on using it, even when I disabled it.
I like Rust applications but I don't like this response. The dev sounds worn out; whereas the dev of Ghostty seems to be a pleasure to deal with.
Earlier quoted context omitted.
Alacritty on macOS and Linux user here (Windows Terminal on Windows due to easily different shells available, formerly used iTerm2 on macOS). I make up for lack of tabs with zellij locally (tmux remotely). Also allows me to relog or close/update Alacritty. I will give Ghostty a whirl but why no shout out to Alacritty? Which features am I missing out on?
Ghostty's community is much nicer compared to Alacritty :)
Thus far I have not been able to get my italic bold font (Cartograph CF) working on Ghostty, but this is a minor issue.
Many people here seem impressed about speed/performance. I have been using all sorts of terminals / emulators over the past 20 years and it never occurred to me a terminal can be slow. When I type a command, I just get the result instantaneously, for any terminal. What are the use cases that can make a terminal be slow?
Earlier quoted context omitted.
Ghostty's community is much nicer compared to Alacritty :)
Thanks. I'm interested in seeing examples (of Alacritty community not being nice). I'm aware of one now [1] but I have not been involved with the Alacritty community much. I read/write a few bug reports when the project was born; after that it has served me very well (compared to iTerm2 and Terminal.app). IIRC there was something with ligatures but I don't remember. Thus far I have not been able to get my italic bold…
And then another where one of their maintainers had a meltdown and his fellow dev jumped in to protect him from... a bug report on the color green https://github.com/alacritty/alacritty/issues/1561
This was a few years ago so maybe they grew up since then.
Many people here seem impressed about speed/performance. I have been using all sorts of terminals / emulators over the past 20 years and it never occurred to me a terminal can be slow. When I type a command, I just get the result instantaneously, for any terminal. What are the use cases that can make a terminal be slow?
I think this mostly plays a role when using modal text editors like vim in your terminal. Speed matters so very much then! Give it a try if you want ;)
Earlier quoted context omitted.
I uninstalled the app when I saw that Cmd+, opens an empty text file called config. I'm not going to learn more configuration languages or type 30 characters (or paste them from the browser) to toggle a binary setting.
kitty has a nicely formatted config which lists all settings along with their default values and a very detailed description of each one. It's pretty much the same as having a GUI. Maybe Ghostty can adopt this?
mkdir -p ~/.config/ghostty
ghostty +show-config --default --docs >> ~/.config/ghostty/configA few things that keep me from switching to it full time:
- Missing search scrollback (cmd+f). This appears to be coming soon: https://github.com/ghostty-org/ghostty/issues/189
- More of a nitpick than anything, but the only way to disable cursor blinking is to disable shell integration. Unfortunately, this means taking away things like native scrolling and likely some other things I don't know about. I see there is a discussion here to possibly address this: https://github.com/ghostty-org/ghostty/discussions/2812
I feel like this would be a no-brainer switch for me once the above are addressed.