mirror of
https://github.com/wez/wezterm.git
synced 2024-12-24 13:52:55 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
ee5206db50
In #2177 we found that one of the examples that tries to use the default initialization was failing. The root cause is that we were constructing a value like: `{ExtendSelectionToMouseCursor=nil}` which is effectively the same as: `{}` but that has no information on the enum variant name. This commit avoids mapping DynValue::Null to LuaValue::Nil and instead uses a light user data nullptr value. That allows the structure to round trip correctly. refs: #2177 |
||
|---|---|---|
| .cargo | ||
| .github | ||
| assets | ||
| async_ossl | ||
| base91 | ||
| bidi | ||
| bintree | ||
| ci | ||
| codec | ||
| color-types | ||
| config | ||
| deps | ||
| docs | ||
| env-bootstrap | ||
| filedescriptor | ||
| licenses | ||
| lua-api-crates | ||
| luahelper | ||
| mux | ||
| procinfo | ||
| promise | ||
| pty | ||
| rangeset | ||
| ratelim | ||
| strip-ansi-escapes | ||
| tabout | ||
| term | ||
| termwiz | ||
| test-data | ||
| umask | ||
| vtparse | ||
| wezterm | ||
| wezterm-client | ||
| wezterm-dynamic | ||
| wezterm-font | ||
| wezterm-gui | ||
| wezterm-gui-subcommands | ||
| wezterm-input-types | ||
| wezterm-mux-server | ||
| wezterm-mux-server-impl | ||
| wezterm-ssh | ||
| wezterm-toast-notification | ||
| window | ||
| .cirrus.yml | ||
| .gitignore | ||
| .gitmodules | ||
| .rustfmt.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CONTRIBUTING.md | ||
| get-deps | ||
| 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 docs and guide 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 a couple of 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.
- Start or join a thread in our GitHub Discussions; if you have general questions or want to chat with other wezterm users, you're welcome here!
- There is a Matrix room via Element.io for (potentially!) real time discussions.
The GitHub Discussions and Element/Gitter rooms are better suited for questions than bug reports, but don't be afraid to use whichever you are most comfortable using and we'll work it out.
Supporting the Project
If you use and like WezTerm, please consider sponsoring it: your support helps to cover the fees required to maintain the project and to validate the time spent working on it!
