mirror of
https://github.com/wez/wezterm.git
synced 2024-12-24 05:42:03 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
0e568ea161
On a Fedora 31 system running Wayland I noticed that wezterm and the compositor were running pretty hot on their respective CPU cores. It turned out that we had a lot of [Refresh](https://docs.rs/smithay-client-toolkit/0.6.4/smithay_client_toolkit/window/enum.Event.html#variant.Refresh) events being generated and consumed. We were treating this as needing a full paint so we'd be effectively continually running the opengl paint cycle over and over. The docs for that event say that it is intended to refresh the client decorations so let's focus it towards that instead. This does bring the CPU usage back down to intended levels. I believe this hot CPU usage to be compositor-dependent: this is the first I've seen of it out of 4 different Wayland environments! |
||
|---|---|---|
| .cargo | ||
| .github/workflows | ||
| assets | ||
| base91 | ||
| ci | ||
| deps | ||
| docs | ||
| promise | ||
| pty | ||
| src | ||
| tabout | ||
| term | ||
| termwiz | ||
| vtparse | ||
| window | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| 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.