mirror of
https://github.com/wez/wezterm.git
synced 2024-11-10 06:34:17 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
1b99690990
I've expanded the number of bits from 16->32 without impacting
the overall struct sizes and reserved 2 bits for super/subscript.
I refer to these as vertical alignment properties for conceptual
consistency with css.
SGR 73, 74, 75 are used to set super, sub and normal vertical alignment.
These are compatible with mintty.
However, mintty just added support for setting both attributes to render in
small caps in
|
||
|---|---|---|
| .cargo | ||
| .github | ||
| assets | ||
| async_ossl | ||
| base91 | ||
| bidi | ||
| bintree | ||
| ci | ||
| codec | ||
| color-types | ||
| config | ||
| deps | ||
| docs | ||
| env-bootstrap | ||
| filedescriptor | ||
| frecency | ||
| licenses | ||
| lua-api-crates | ||
| luahelper | ||
| mux | ||
| procinfo | ||
| promise | ||
| pty | ||
| rangeset | ||
| ratelim | ||
| strip-ansi-escapes | ||
| sync-color-schemes | ||
| 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-DISTRO-MAINTAINER.md | ||
| README.md | ||
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!
