tty7/README.md at 0ee126a7fd577befec860d9d09cf44b0443b70a1

mirror of https://github.com/l0ng-ai/tty7.git synced 2026-09-22 00:02:23 +00:00

Files

T

l0ng-ai 0ee126a7fd docs(readme): restructure around Why/Features, cut prose and boilerplate (#48 )

* feat(view): explain a dead Ctrl+R instead of failing silently (#46)

When shell integration never engages in a pane — typically because a
figterm-style PTY shim (kiro-cli-term, qterm) exec'd over the shell and
swallowed its OSC 133 reports — the whole command-editor overlay is
absent by design, and Ctrl+R used to fall through to the raw PTY with no
hint of why the history menu didn't appear.

Now that raw-path Ctrl+R raises a one-shot, per-pane notice (floating
bottom-right) saying integration hasn't engaged, refined off-thread with
the daemon's foreground-process name when it matches a known shim: the
wrapper is the culprit worth naming, since "install integration" advice
would mislead — the hooks are installed, something between the shell and
tty7 is eating their output. The chord still reaches the PTY, so the
shell's own reverse-i-search keeps working as the fallback.

Guards keep it honest: silent inside an 8s startup grace window (slow rc
files legitimately haven't reported yet), on the alt screen, or once
integration has engaged (a running foreground command is then the
obvious reason); retracted if a slow shell engages late; dismissed by
the next keystroke or a 15s timeout.

* docs(readme): restructure around Why/Features, cut prose and boilerplate

Replace the prose About section with a four-point Why tty7 list, split
Features into prompt vs window groups written as one-line benefit
bullets, drop emoji section headers, fold acknowledgements/contributing/
license into a one-line footer, and keep zh-CN in sync throughout.

2026-07-11 10:22:54 +08:00

4.9 KiB

Raw Blame History

tty7

A GPU-rendered terminal in pure Rust.

_{GPU rendering on Zed's gpui · VT core from Alacritty}

Why tty7 · Install · Features · Benchmarks · Keybindings

_{English · 简体中文}

Why tty7

Fast — about 2× the throughput of Alacritty, Ghostty, or Kitty on the same hardware (benchmarks)
A modern prompt — completion, syntax highlighting, and history search built in; no plugins to assemble
Sessions that survive — close the window or quit the app, your shells keep running; no tmux
Zero config — zsh, bash, fish, and PowerShell work out of the box

Native builds for macOS, Windows, and Linux ship with every release.

Install

Download the build for your platform from Releases:

macOS — tty7-<version>-macos-arm64.dmg (Apple Silicon) or …-x86_64.dmg (Intel); open it and drag tty7.app into Applications.
Windows — …-windows-x86_64-setup.exe (installer: Start Menu shortcut + uninstall entry), or …-windows-x86_64.zip (portable: unzip and run tty7.exe).
Linux — …-linux-x86_64.tar.gz; extract and run ./tty7 (needs the usual x11/wayland runtime libraries).

Features

At the prompt

Ghost suggestions — your history completes the whole line as you type; → to accept
Tab completion that explains — every flag and subcommand with its description, for ~100 common commands
Syntax highlighting — as you type, nothing to install
Fuzzy history search — ⌃ R shows what you ran, where, and whether it failed
History from day one — your existing shell history just works, and carries across sessions
Real line editing — selection, word motion, undo

In the window

Tabs & splits — always open in the current directory
Command palette ⌘ P · scrollback search ⌘ F
⌘-click links · desktop notifications
Eight themes · CJK / IME input

Benchmarks

All four terminals measured back-to-back on the same machine, same day, same 155×40 grid — Apple M1 Pro, macOS 26.3.1, five-run averages (2026-07-04):

	tty7	Alacritty	Ghostty	Kitty
Plaintext IO — 11 MB `cat` _{(lower = better)}	95 ms	239 ms	179 ms	185 ms
DOOM-fire frame rate _{(higher = better)}	888 fps	485 fps	552 fps	617 fps
Cold-launch memory	116 MB¹	105 MB	128 MB	130 MB

_{¹ GUI 105 MB + the persistent daemon 11 MB.}

Where the speed comes from:

The PTY is read at device speed and parsed in large batches, off the render path
Hot paths are lock-free — a big cat never waits on drawing
The daemon buffers up to 16 MiB ahead of the window before backpressure applies

Methodology (how each terminal is driven, grid fairness, known pitfalls) and one-command reproduction live in scripts/bench/ — run it yourself.

Keybindings

Keys are shown in macOS notation — on Windows and Linux, read ⌘ as Ctrl. Open Settings with ⌘ , to browse or remap them all. The essentials:


`⌘ T` · `⌘ W` · `⌘ ⇧ T`	new tab · close tab · reopen closed tab
`⌘ D` · `⌘ ⇧ D`	split right · split down
`⌘ ]` · `⌘ [`	next pane · previous pane
`⌘ ⏎` · `⌘ ⇧ ⏎`	toggle fullscreen · maximize / restore the pane
`⌘ K`	clear the screen and scrollback
`⌘ P`	command palette
`⌘ F`	search the scrollback
`⌃ R`	fuzzy-search shell history
`⌘ +` · `⌘ −` · `⌘ 0`	font size up · down · reset

The full list — and any overrides — lives in Settings → Keybindings.

_{Built on gpui and alacritty_terminal · Apache-2.0 · Discord · Changelog}

4.9 KiB Raw Blame History Unescape Escape