mirror of
https://github.com/wez/wezterm.git
synced 2025-01-07 06:26:51 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
6a2e356156
* Validate scrollback_lines to avoid crashes I started using wezterm today, and I immediately tried to configure it to use "infinite scrollback", as I use in iTerm2. From the configuration I couldn't tell if there was a way to do this, so I just set it to a really large number, hoping that would work. Interestingly this works for very large numbers when the config is just being reloaded while the terminal is running, but if you then try to restart the application it crashes (tried to allocate like 100PB or something). I then came across #1342 and thought "that's seems a bit too involved", and decided that I probably don't need infinite scrollback, but just kind of a large number. Through fair dice roll I determined `one billion - 1` will probably suffice. Now, this might not be the best solution, so I'm happy to get some feedback. I was also thinking that it would be nice if one could just set it to `0`, and then the applicatio determines a suitably large number for the amount of RAM available, but a) I wasn't sure how this would be best implemented in the confines of the current architecture, and b) I wasn't sure if it would be well received. Long story short, happy to hear your feedback. * simplify slightly --------- Co-authored-by: Wez Furlong <wez@wezfurlong.org> |
||
|---|---|---|
| .cargo | ||
| .copr | ||
| .github | ||
| assets | ||
| async_ossl | ||
| base91 | ||
| bidi | ||
| bintree | ||
| ci | ||
| codec | ||
| color-types | ||
| config | ||
| deps | ||
| docs | ||
| env-bootstrap | ||
| filedescriptor | ||
| frecency | ||
| lfucache | ||
| licenses | ||
| lua-api-crates | ||
| luahelper | ||
| mux | ||
| nix | ||
| procinfo | ||
| promise | ||
| pty | ||
| rangeset | ||
| ratelim | ||
| strip-ansi-escapes | ||
| sync-color-schemes | ||
| tabout | ||
| term | ||
| termwiz | ||
| test-data | ||
| umask | ||
| vtparse | ||
| wezterm | ||
| wezterm-blob-leases | ||
| wezterm-client | ||
| wezterm-dynamic | ||
| wezterm-font | ||
| wezterm-gui | ||
| wezterm-gui-subcommands | ||
| wezterm-input-types | ||
| wezterm-mux-server | ||
| wezterm-mux-server-impl | ||
| wezterm-open-url | ||
| wezterm-ssh | ||
| wezterm-toast-notification | ||
| wezterm-uds | ||
| wezterm-version | ||
| window | ||
| .cirrus.yml | ||
| .dockerignore | ||
| .gitignore | ||
| .gitmodules | ||
| .mailmap | ||
| .rustfmt.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| deny.toml | ||
| get-deps | ||
| LICENSE.md | ||
| Makefile | ||
| mkdocs_macros.py | ||
| PRIVACY.md | ||
| README-DISTRO-MAINTAINER.md | ||
| README.md | ||
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
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!
