

-
ghostty
👻 Ghostty is a fast, feature-rich, and cross-platform terminal emulator that uses platform-native UI and GPU acceleration.
I took this for a spin today. Coming from a long-time iTerm2 user, the first thing I noticed was how snappy everything feels, especially when resizing the window. The straight-forward configuration was extremely nice as well and can be stored in my dotfiles now (iTerm was a giant dump of XML).
A 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.
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
You should also check out Wezterm too and see which one you like more. I ported my tmux keybinds to Wezterm - including vim-tmux-navigator style ctrl+{h,j,k,l} for navigating between nvim splits and Wezterm splits, ctrl-a as tmux leader. Getting tmux out of the way between terminal and nvim noticably improved scroll feeling in nvim and just in shell scrollback too.
I styled Wezterm's tabs to look just like my tmux tab bar too, there's no visual difference for me between a Wezterm window with Wezterm tabs, and a Wezterm window with tmux tabs. If you're more of a terminal native than a Mac native, I think you'd enjoy it.
My wezterm config: https://github.com/justjake/Dotfiles/blob/new/config/wezterm...
-
2024/12/28 09:04:42 An error occurred! Please create an issue at https://github.com/jesseduffield/lazydocker/issues
*exec.ExitError exit status 1
-
I'm very excited to have this because it's the first bit of open source quality software to hit the streets in a while.
I like where we're headed with tools like this and Ladybird[0] for hope of a subscriptionless future.
Thank you, Mitchell!
[0] https://ladybird.org/
-
Hmm any way for this to work in kde plasma wayland?
In yakuake they have to register the Open/Retract shortcut with KGlobalAccel [1] and I don't think global shortcuts are implemented otherwise
[1] https://github.com/KDE/yakuake/blob/164d24b8bad1175199260c62...
-
-
alacritty
Discontinued A cross-platform, OpenGL terminal emulator. [Moved to: https://github.com/alacritty/alacritty] (by jwilm)
-
Nutrient
Nutrient - The #1 PDF SDK Library. Bad PDFs = bad UX. Slow load times, broken annotations, clunky UX frustrates users. Nutrient’s PDF SDKs gives seamless document experiences, fast rendering, annotations, real-time collaboration, 100+ features. Used by 10K+ devs, serving ~half a billion users worldwide. Explore the SDK for free.
-
-
hyper
Discontinued A terminal built on web technologies [Moved to: https://github.com/vercel/hyper] (by zeit)
-
-
-
-
wezterm
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
-
-
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 a different terminal emulator: https://github.com/alacritty/alacritty/issues/3473#issuecomm...
-
you can use glsl shaders with Ghostty including this CRT one to mimic what cool retro does
https://github.com/m-ahdal/ghostty-shaders/blob/main/crt.gls...
-
nixGL is also likely required on non-NixOS Linux distros.
https://github.com/nix-community/nixGL
-
-
-
This. To add some words why this is important:
Given the remote-first container-based world we're heading towards, decoupling UI (terminal emulator) from its state (tmux, code-server) is a great design decision, which I think will ultimately define what the "next generation" of terminal emulators is. Imagine being able to open tabs directly on remote host, reconnect without losing state, etc, all while using native UI (so Cmd+T to open new tab, Cmd+F to search, etc). Productivity game changer, which currently only the iTerm2 users can fully enjoy.
Ptyxis (putting its state in running containers), WezTerm (native handling of ssh sessions) and VSCode's terminal (starting a proprietary code-server binary and connecting to its TCP port) have reached some of this functionality, but in their design they need some out-of-band mechanisms to do their magic, ultimately limiting the scenarios they can handle.
Meanwhile tmux -CC [0] and ht [1] are sending both their control channel and data channel over the opened terminal itself (in-band), making them flexible enough to support any configuration. Something complex like `ssh jumpbox -- ssh prod -- podman exec -it prod /bin/bash -- tmux -CC` should just work.
[0] https://github.com/tmux/tmux/wiki/Control-Mode
[1] https://github.com/andyk/ht
-
ht
headless terminal - wrap any binary with a terminal interface for easy programmatic access. (by andyk)
This. To add some words why this is important:
Given the remote-first container-based world we're heading towards, decoupling UI (terminal emulator) from its state (tmux, code-server) is a great design decision, which I think will ultimately define what the "next generation" of terminal emulators is. Imagine being able to open tabs directly on remote host, reconnect without losing state, etc, all while using native UI (so Cmd+T to open new tab, Cmd+F to search, etc). Productivity game changer, which currently only the iTerm2 users can fully enjoy.
Ptyxis (putting its state in running containers), WezTerm (native handling of ssh sessions) and VSCode's terminal (starting a proprietary code-server binary and connecting to its TCP port) have reached some of this functionality, but in their design they need some out-of-band mechanisms to do their magic, ultimately limiting the scenarios they can handle.
Meanwhile tmux -CC [0] and ht [1] are sending both their control channel and data channel over the opened terminal itself (in-band), making them flexible enough to support any configuration. Something complex like `ssh jumpbox -- ssh prod -- podman exec -it prod /bin/bash -- tmux -CC` should just work.
[0] https://github.com/tmux/tmux/wiki/Control-Mode
[1] https://github.com/andyk/ht
-
wslg
Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
Related issues:
https://github.com/microsoft/wslg/issues/1008
-
The parent is probably referring to this benchmark: https://github.com/const-void/DOOM-fire-zig/
-
Donno, the benchmarks don't look all that great: https://github.com/moktavizen/terminal-benchmark
-
Some small tweaks on the built-in theme ayu_evolve.
https://github.com/david-crespo/dotfiles/blob/30917c16a703e9...
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives