mirror of
https://github.com/wez/wezterm.git
synced 2024-11-23 15:04:36 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
e6a858664f
This is a bit of a switch-up, see this comment for more background: refs: https://github.com/wez/wezterm/issues/265#issuecomment-701882933 This commit: * Adds a pre-compiled mesa3d opengl32.dll replacement * The mesa dll is deployed to `<appdir>/mesa/opengl32.dll` which by default is ignored. * When the frontend is set to `Software` then the `mesa` directory is added to the dll search path, causing the llvmpipe renderer to be enabled. * The old software renderer implementation is available using the `OldSoftware` frontend name I'm not a huge fan of the subdirectory for the opengl32.dll, but I couldn't get it to work under a different dll name; the code thought that everything was initialized, but the window just rendered a white rectangle. |
||
|---|---|---|
| .cargo | ||
| .github | ||
| assets | ||
| base91 | ||
| bintree | ||
| ci | ||
| deps | ||
| docs | ||
| filedescriptor | ||
| promise | ||
| pty | ||
| rangeset | ||
| src | ||
| tabout | ||
| term | ||
| termwiz | ||
| vtparse | ||
| window | ||
| .cirrus.yml | ||
| .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 Matrix/Riot.im room for (potentially!) real time discussions; that is bridged from the original Gitter room.
The Matrix/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.