mirror of
https://github.com/wez/wezterm.git
synced 2024-12-25 14:22:37 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
751dd460da
This commit causes lines to be "compressed" (really, just translated to the new clustered line storage variant) as they move into scrollback. The memory savings are significant for large scrollback: `wezterm -n --config scrollback_lines=1000000` `time cat enwiki8.wiki` before: ~9s, Resident: 2.1G after: ~15s, Resident: 620K (!) The performance impact is non-trivial, and I will dig into that next. refs: https://github.com/wez/wezterm/issues/1626 |
||
|---|---|---|
| .cargo | ||
| .github | ||
| assets | ||
| async_ossl | ||
| base91 | ||
| bidi | ||
| bintree | ||
| ci | ||
| codec | ||
| color-types | ||
| config | ||
| deps | ||
| docs | ||
| env-bootstrap | ||
| filedescriptor | ||
| licenses | ||
| lua-api-crates | ||
| luahelper | ||
| mux | ||
| procinfo | ||
| promise | ||
| pty | ||
| rangeset | ||
| ratelim | ||
| strip-ansi-escapes | ||
| sync-color-schemes | ||
| tabout | ||
| term | ||
| termwiz | ||
| test-data | ||
| umask | ||
| vtparse | ||
| wezterm | ||
| wezterm-client | ||
| wezterm-dynamic | ||
| wezterm-font | ||
| wezterm-gui | ||
| wezterm-gui-subcommands | ||
| wezterm-input-types | ||
| wezterm-mux-server | ||
| wezterm-mux-server-impl | ||
| wezterm-ssh | ||
| wezterm-toast-notification | ||
| window | ||
| .cirrus.yml | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| get-deps | ||
| LICENSE.md | ||
| README-DISTRO-MAINTAINER.md | ||
| README.md | ||
| wt-record | ||
| wt-replay | ||
Wez's Terminal
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
User facing docs and guide at: https://wezfurlong.org/wezterm/
Screenshot of wezterm on macOS, running vim
Installation
https://wezfurlong.org/wezterm/installation.html
Getting help
This is a spare time project, so please bear with me. There are a couple of channels for support:
- You can use the GitHub issue tracker to see if someone else has a similar issue, or to file a new one.
- Start or join a thread in our GitHub Discussions; if you have general questions or want to chat with other wezterm users, you're welcome here!
- There is a Matrix room via Element.io for (potentially!) real time discussions.
The GitHub Discussions and Element/Gitter rooms are better suited for questions than bug reports, but don't be afraid to use whichever you are most comfortable using and we'll work it out.
Supporting the Project
If you use and like WezTerm, please consider sponsoring it: your support helps to cover the fees required to maintain the project and to validate the time spent working on it!
