mirror of
https://github.com/wez/wezterm.git
synced 2024-12-25 14:22:37 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
ea401e1f58
This was a bit of a pain to track down because this behavior isn't specified anywhere or called out explicitly. The issue is that if you use a true color escape sequence such as ```bash printf "\x1b[38;2;255;100;0mTRUECOLOR\n" ``` the active color would remain active when switching between the primary and the alt screen until something (eg: `ls --color`) changed it again. I hadn't run into this because in my prompt, many many years ago, I had it set to perform an SGR reset (`\x1b[0m`) as the first thing to ensure that the shell is in a saner state. For users that don't do this they end up with a weird looking color bleed effect. refs: https://github.com/wez/wezterm/issues/169 |
||
|---|---|---|
| .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.