mirror of
https://github.com/wez/wezterm.git
synced 2024-11-14 03:16:09 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
8f1f1a65ea
With this commit, we now survive a reinstall or upgrade of the nvidia drivers on my Windows sytem without crashing. This commit allows notifying the application of the context loss so the application can either try to reinit opengl or open a new window as a replacement and init opengl there. I've not had success at reinitializing opengl after a driver upgrade; it seems to be persistently stuck in a state where it fails to allocate a vertex buffer. SO, the state we have now is that we try to reinit opengl on a new window, and if that fails, leave it set to the software renderer. This isn't a perfect UX, but it is better than terminating! refs: https://github.com/wez/wezterm/issues/156 |
||
|---|---|---|
| .cargo | ||
| .github | ||
| assets | ||
| base91 | ||
| ci | ||
| deps | ||
| docs | ||
| filedescriptor | ||
| promise | ||
| pty | ||
| rangeset | ||
| src | ||
| tabout | ||
| term | ||
| termwiz | ||
| vtparse | ||
| window | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| get-deps | ||
| install.sh | ||
| 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 which is bridged to the Matrix/Riot.im for (potentially!) real time discussions
The Gitter/Matrix 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.