mirror of
https://github.com/wez/wezterm.git
synced 2024-12-29 16:42:13 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
23b4876d75
I've noticed this off and on for a while, and thought it was something
fishy with my shell dotfiles.
Tracing through I found that the final byte in the "Face with head
bandage" emoji 🤕 U+1F915 was being interpreted as the MW control
code and causing the vt parser to jump out of the OSC state.
The solution for this is to hook up proper UTF-8 processing in the
same way that it is applied in the ground state.
Since we don't have enough bits to introduce new state values (we're
pretty tightly packed in the 16 bits available), I've introduced a
memory of the state to which the utf8 parser needs to return once
a complete sequence is detected.
|
||
|---|---|---|
| .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.