ssh://git@git.notashelf.dev:33/notashelf/beer.gitRecent commits
log- docs: document `BEER_CONFIG` and repeatable `--config` in manpages
Signed-off-by: NotAShelf <raf@notashelf.dev>
unverifiedfe175a7c5133 - beer/config: support loading multiple files
Signed-off-by: NotAShelf <raf@notashelf.dev>
unverifiede86728c33699 - build: tag 0.5.4
Signed-off-by: NotAShelf <raf@notashelf.dev>
unverifiedcadefd387baa
Files
15 entries- .clippy.toml14 B4w ago
- .deny.toml372 B4w ago
- .envrc11 B4w ago
- .gitignore37 B3w ago
- .rustfmt.toml33 B4w ago
- Cargo.lock28342 B3w ago
- Cargo.toml1430 B3w ago
- README.md1933 B3w ago
- crates 2w ago
- doc 2w ago
- flake.lock567 B4w ago
- flake.nix541 B4w ago
- nix 3w ago
- scripts 3w ago
- terminfo 4w ago
🍺 beer
A terminal worth pouring time into.
A small, fast, Wayland-native terminal emulator written in Rust drawn entirely on the CPU, with no GPU pipeline, no tabs, no ligatures, and no async runtime to get in the way.
Why another terminal?
Most terminals reach for the GPU and a stack of abstractions before they draw a
single glyph. beer goes the other way. It takes its cues from foot keep the
moving parts few, render with the CPU through wl_shm, talk to a real PTY, and
stay out of the way. The result is a terminal that starts instantly, sits
quietly in the background, and spends its cycles on your shell rather than on
itself. It is the kind of tool you forget is running which, for a terminal, is
the highest compliment. Pour one, get to work.
Project status
beer is pre-1.0 but already comfortable as your daily single-window terminal
on Wayland. It’s made clear in documentation about what it does and does not do
yet, and it would rather do a smaller set of things well than a larger set
half-heartedly. Feature requests are welcome, but not everything will be
implemented.
What’s in here
This is a Cargo workspace with two crates:
crates/beer- the terminal application itself. Start here for the feature list, installation, configuration, and day-to-day use.crates/beer-protocols- the reusable, self-documenting building blocks the terminal is made of, and a readable reference for the escape sequences and protocolsbeerspeaks.
If you just want to run it, head to the application README. If you are curious how a terminal actually talks to the programs inside it, the protocols README is a friendly tour.