mirror of
https://github.com/wez/wezterm.git
synced 2024-12-18 10:52:16 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
fe89082764
This is unfortunately a bit of a muddy commit and I'm too lazy to split it up. * Removed `Position::NoChange`; use `Position::Relative(0)` instead * Added missing cursor positioning cases in the terminfo renderer * Taught line editor about the cursor position when the line spans multiple physical lines * Taught the Windows input layer to process escape sequences for eg: the arrow keys when running with virtual terminal enabled. * Removed the hack that under-reported the terminal width; the hack was present to make some aspects of rendering with the native windows console logic easier, but it was getting in the way of the line editor. This may well break something, but it fixed up the line editor :-/ cc: @markbt |
||
---|---|---|
.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.