mirror of
https://github.com/wez/wezterm.git
synced 2024-11-24 07:46:59 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
bb04d91101
The sync_channel was originally added as a brake to avoid swamping the event loop, but we've subsequently grown a more formal rate limiting config for this. The rate limiter is superior because it allows making forward progress over time, whereas the bounded channel is a hard blocking limit. When making a large paste the app on the other end will typically emit a lot of output. If our reader is blocked on the sync channel the output of the pty can be blocked, and that in turn will block our attempt to write to the pty. We cannot simply set the pty to non-blocking mode because non-blocking ptys are not a thing on windows, and in the interest of not silently breaking windows, I prefer to make the unix side of things match that architecture. anyway: TL;DR is that we don't need the bounded channel now that we have rate control to manage swamping the event loop, so we can simplify this code. |
||
|---|---|---|
| .cargo | ||
| assets | ||
| base91 | ||
| ci | ||
| deps | ||
| docs | ||
| promise | ||
| pty | ||
| src | ||
| tabout | ||
| term | ||
| termwiz | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| appveyor.yml | ||
| azure-pipelines.yml | ||
| build.rs | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| get-deps | ||
| install.sh | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE.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 home page 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 two 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: https://github.com/wez/wezterm/issues
- There is a gitter room for (potentially!) real time discussions: https://gitter.im/wezterm/Lobby
The gitter room is probably better suited to questions than it is to bug reports, but don't be afraid to use whichever you are most comfortable using and we'll work it out.