Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ghostty 1.0

ghostty.org

Post reply on HN
Print view View original

511–520 of 719 posts

Re: Ghostty 1.0

#511

Post by Filligree »

mitchellh wrote: post #145
imron wrote: post #140

Earlier quoted context omitted.

> kills performance And battery. I gave up on alacritty because it was always using the dedicated graphics card of my MacBook and there was no reasonably way to use the integrated graphics card because it was “low performance”.

- Ghostty does vsync by default and supports variable refresh rates (DisplayLink). If you're on battery and macOS wants to slow Ghostty down, it can and we respect it. - Ghostty picks your integrated GPU over dedicated/external - Ghostty sets non-focused rendering threads as QoS background to go onto E-cores - Ghostty slows down rendering significantly if the window is obscured completely (not visible) No idea if Ala…

> - Ghostty slows down rendering significantly if the window is obscured completely (not visible)

About this. For whatever reason, I often end up with foreground windows (e.g. Chrome) covering the background window entirely, except for a sliver a few pixels wide.

Would Ghostty handle this case? I don't believe there's any point in full-speed rendering if less than a single line of text is shown, but the window isn't technically obscured completely.

Re: Ghostty 1.0

#512

Post by __float »

jFriedensreich wrote: post #505

Am I the only person wondering why we need 100 terminal emulators when there are only 2 or 3 solutions to using command line tools more like a REPL? (to some degree warp, some bash support in hydrogen, advanced edit mode of powershell) I don't care for using "fancy" TUIs all i want is better tooling to interact with these that does not feel like 1970 and more like the chrome console.

> I saw tradeoffs that I didn't like. I saw features that I wanted. I saw performance that I could improve. I saw stagnation. There are many fantastic terminals out there and you should use them if they work for you. But I wanted something different and thought maybe others did too.

This motivation is pretty clearly stated in the article.

Some people use "fancy TUIs" (the famous editors vim and emacs surely count) and if you don't, feel free to ignore this new option.

Re: Ghostty 1.0

#513

Post by fn-mote »

sionisrecur wrote: post #188
jbergstroem wrote: post #62

Earlier quoted context omitted.

I've been a beta tester from very early on. I came for the performance but stayed for the stability. I've only had a rare few crashes and all but one was a duplicate in the bug tracker. I thought I needed search but as Mitchell put it, not a 1.0 feature. Ripgrep was always the answer. Very happy to share the ghostty experience with the world!

Search was the first thing I noticed it was lacking. I hope it can be added at some point, sometimes you can't just run a command again to grep it.

The kitty method of piping the scroll back buffer to a pager is more general - it also seems like a quick fix to achieve this desired feature.

Re: Ghostty 1.0

#515

Post by dismalaf »

hysan wrote: post #363
dismalaf wrote: post #357

Earlier quoted context omitted.

Suse has had Gnome as the only supported DE for 5ish years now. They don't even support KDE at all. Talking Suse as in the commercial distros. OpenSuse has choice of DEs like most.

Gotcha. So you really meant enterprise only. Not a tongue in cheek answer (which I thought was a way of just grouping all suse-related distros). To me, that’s not the context for a user oriented product. Any reasonable person looking at a developer tool and listening to that pitch isn’t thinking pure enterprise. So I think that’s not a good interpretation of what I find disagreeable with calling a GTK4-only app “Linu…

It means what people actually develop, support and use in the real world. KDE has no real support. Suse, Red Hat/IBM and Canonical all develop and support Gnome which is largely what has made it so polished.

Also, I'd wager Gnome is absolutely used by 90% or more of Linux users.

> Also, I thought opensuse (or whatever new name they’re using) was KDE default but with a choice (like Debian)? At least that’s what DE I got last time distro hopped to it.

Depends "which" openSuse. OpenSuse Leap is going away since Suse (the corporation) is doing away with non-immutable distros. Whether it keeps KDE remains to be seen as MicroOS has lots of issues with KDE. Tumbleweed has KDE as the first choice still, but it's basically hobbyist-only from this point since there's no equivalent Suse distro. Aeon is Gnome-only.

Re: Ghostty 1.0

#516

Post by favadi »

theanirudh wrote: post #391
favadi wrote: post #387

For some reasons, the font looks thinner compare to Kitty on macOS. Not sure if it is a bug or intentional.

Yes, it is. Try setting font-thicken = true https://ghostty.org/docs/config/reference#font-thicken

Thanks, that's exactly what I am used to!

Re: Ghostty 1.0

#517

Post by vrnvu »

rauanm wrote: post #502

I tried to install and play around with it, it's really nice. Took a bit of tinkering to set a theme and my favourite Pragmata Pro, but what ultimately annoys me is the lack of 'turnkey' selecting for text. When I run `Cmd + A`, I want my terminal to make a full text selection of an entered command, not of the screen content. Or when I run `Option + Shift + Arrow left/right`, I want to select words from an entered co…

Cmd+A to select the entered command isn't standard.

You could try:

- Ctrl+A: Move to the beginning of the line.

- Ctrl+E: Move to the end of the line.

- Ctrl+K: Cut the command from the cursor position to the end.

- Ctrl+U: Cut the command from the cursor to the beginning of the line.

- Ctrl+Y: Paste the text back.

This should work in all terminals.

Re: Ghostty 1.0

#518

Post by xoa »

dcre wrote: post #338
herpdyderp wrote: post #228

Earlier quoted context omitted.

What CLI programs? I have yet to run into any issues after using the built in terminal for its entire lifespan.

As an example, here is the Helix editor (neovim looks just as bad) in Terminal.app vs. ghostty (would look just as good in any other modern terminal). https://imgur.com/a/terminal-app-left-vs-truecolor-tddRL0C

I appreciate you making an effort to visually display things, but FWIW I don't think that (or sibling) really gets to the root issue, which is less of capability then practical convenience and compatibility. Mac native Terminal perfectly well supports 256 colors (or arbitrary 16 colors with themes), which I've used, so you could absolutely make both sides look identical there. Unless someone is regularly viewing photos inside their terminal (which some do support and can actually sometimes be handy!) then it might not be immediately clear what 24-bit would bring to the table over 8-bit, regardless of editor or shell themes.

But in practice 24-bit was an easy lift for terminals under active development ages ago, and in turn made it trivial to have everyone across any platform specify exact colors more easily without any end user customization or arguments about "not quite what I wanted" in an 8-bit palette or whatever. Thus a lot of the ecosystem now makes use of it. Being able to replicate anything yourself, or get close enough, in a smaller colorspace is still extra grunt work for no particularly valuable reason, and could actually add up to be fairly significant work if one has a lot of more complex code coloring themes and such.

Re: Ghostty 1.0

#519

Post by Filligree »

computerfriend wrote: post #408
shpx wrote: post #392

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.

Aren't plaintext configuration files standard? It's how I configure most applications (and how I like it, because it makes the configuration shareable). As a DSL, it's key-value pairs. It doesn't get much simpler than that.

That could have been acceptable. The problem is it's empty; it should instead contain the default configuration.

Re: Ghostty 1.0

#520

Post by tuananh »

manmal wrote: post #480
tuananh wrote: post #477

- xterm still feel faster to me. - some visual artifacts with the gtk menu - sometimes prompt got clear when openning 2nd / 3rd windows - cant get keybinding quick toggle to work

In case you mean the quick terminal (ctrl+`): keybind = global:ctrl+grave_accent=toggle_quick_terminal

doesn't work for me. i'm using i3.

olps, it's macOS only feature.

Post reply on HN