mirror of
https://github.com/wez/wezterm.git
synced 2024-11-27 02:25:28 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
9ff9bf15fd
The goal at the window layer is to preserve enough useful information for other layers. In this specific circumstance on macos we'd like to be able know both that eg: ALT-1 was pressed and that ALT-1 composes to a different unmodified sequence and then allow the user's key binding assignment to potentially match on both. We sort of allowed for this, but didn't separate out the modifier keys. This commit adds a `raw_modifiers` concept to the underlying event struct so that we can carry both the raw key and modifier information as well as the composed key and modifier information. In the scenario above, we want the raw key/modifier tuple to be ALT-1 but the composed key/modifier to be eg: unmodified `¡` in my english keymap. refs: https://github.com/wez/wezterm/issues/158 |
||
|---|---|---|
| .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.