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
6069eabc9b
If we've failed to initialize EGL, try setting `LIBGL_ALWAYS_SOFTWARE=true` in the environment and make another pass at initialization in the hope that it brings up something usable. This commit only impacts linux systems at the time of writing. I've made the line that logs the GL implementation information have `error` level again, because it is more convenient for me even if it isn't technically an error. refs: https://github.com/wez/wezterm/issues/272 (but isn't the true fix; this is just trying to make the consequences of that problem less. I would like to get that fixed correctly) refs: https://github.com/wez/wezterm/issues/265#issuecomment-701882933 (which discusses what I think the end state should be) |
||
|---|---|---|
| .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.