To be honest, I don't "get" ghostty. I am not really seeing how this is so much better than the GNOME terminal that ships with my Linux distro. A lot of people are claiming that ghostty is "faster." I watched the lightning talk where the author claims that catting files and binaries is faster. I tried this against ghostty itself after building with zig build -Doptimize=ReleaseFast, using: time cat ghostty. In GNOME t…
Ghostty 1.0
701–710 of 719 posts
Re: Ghostty 1.0
#702Re: Ghostty 1.0
#703Earlier quoted context omitted.
I'm using ctrl+` : keybind = global:ctrl+grave_accent=toggle_quick_terminal It was the first thing I made sure ghostty supported it before trying it. Setting the initial height of the quick terminal is under development: https://github.com/ghostty-org/ghostty/issues/2384 Lack of tab support in the quick terminal is a bummer, but it should come eventually: https://github.com/ghostty-org/ghostty/issues/2329#issuecomm..…
Note, if someone is trying this, that you need to grant accessibility permissions for it to work when Ghostty isn't focused.
Re: Ghostty 1.0
#704Earlier quoted context omitted.
That’s a problem with lazydocker, not ghostty. Maybe contribute to https://github.com/jesseduffield/lazydocker/issues/610 ?
Do you have anything to back up this claim? Because it only crashes in Ghostty, and no other terminal emu I tried it in. Anyway, not my problem, I will just wait until it's fixed and if not, then I'll use one of the gazillion other ones that work 100%.
Re: Ghostty 1.0
#705Earlier quoted context omitted.
Try binding the tmux leader key to '`' (grave accent). This changed my life!
jj or qq can also be used. As I once started with GNU Screen ages ago, I like prefix to ctrl+a but it interferes with going to front of command in bash mode. For that, I use vi keybind mode in my shell (fish or bash) which feel very natural to me. For zellij, I use default prefix so that it does not interfere with remote (yes I am aware remote requires double prefix; I prefer using tmux remotely and zellij locally).
The obvious `set -g prefix jj` throws an error that the key j is a bad key. Various experimenting with bind and unbind have not resulted in success, and I can't seem to find an example .tmux.conf with that config to copy.
Re: Ghostty 1.0
#706Ghostty got a lot of hype (I cover this in my reflection below), but I want to make sure I call out that there is a good group of EXCELLENT terminals out there, and I'm not claiming Ghostty is strictly better than any of them. Ghostty has different design goals and tradeoffs and if it's right for you great, but if not, you have so many good choices. Shout out to Kitty, WezTerm, Foot in particular. iTerm2 gets some ha…
Re: Ghostty 1.0
#707Is there a bounty for zero days?
Re: Ghostty 1.0
#708Earlier quoted context omitted.
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
Off topic but what Helix theme are you using here?
Re: Ghostty 1.0
#709Earlier quoted context omitted.
This gets brought up a lot, so I wrote about it here https://gpanders.com/blog/ghostty-is-native-so-what/
> This also means that native features like pressing Shift+⌘+\ open the tab overview, just as in other applications. Ah, so this is a macos thing and not just Safari. Can anyone help me select a tab using a keyboard? I use the shortcut, type in the search box and...have to use the mouse :(
Re: Ghostty 1.0
#710Earlier quoted context omitted.
+1, no idea. But maybe to add a little bit of context, "damage tracking" means for example, that if there is any ongoing animation (like a spinner), then only a small part of the screen will be re-rendered (with proper vertex-time scissors, so only relevant pixels will be computed). I am not sure if it makes sense in the context of a terminal emulator, but it's certainly a big issue for any non-toy GUI toolkits. GPUs…
No, damage tracking is important as it about reporting that you only updated that spinner, which means that your display server also knows to only redraw and repaint that area, and in turn that your GPU knows during scanout that only that area changed. Without, even if you only redrew your spinner, your display server ends up having to redraw what might be a full screen 4k window, as well as every intersecting window…