c207142bcf
I noticed that things were feeling laggy in general and when I added some debugging prints I noticed that we were getting a continuous stream of CursorMoved events with the same coordinates while the window had focus. This diff short circuits mouse processing in that situation and makes things feel a bit more snappy. |
||
---|---|---|
.cargo | ||
assets | ||
base91 | ||
ci | ||
deps | ||
promise | ||
screenshots | ||
src | ||
term | ||
termwiz | ||
varbincode | ||
.gitignore | ||
.gitmodules | ||
.rustfmt.toml | ||
.travis.yml | ||
appveyor.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 terminal emulator implemented in Rust, using OpenGL for rendering.
Screenshot of wezterm on X11, running vim
Installing a package
- macOS and Windows packages are available from the Releases page
- Bleeding edge Windows package available from Appveyor
Installing from source
- Install
rustup
to get therust
compiler installed on your system. https://www.rust-lang.org/en-US/install.html - Build in release mode:
cargo build --release
- Run it via either
cargo run --release
ortarget/release/wezterm
You will need a collection of support libraries; the get-deps
script will
attempt to install them for you. If it doesn't know about your system,
please contribute instructions!
$ curl https://sh.rustup.rs -sSf | sh -s
$ git clone --depth=1 --branch=master --recursive https://github.com/wez/wezterm.git
$ cd wezterm
$ git submodule update --init
$ sudo ./get-deps
$ cargo build --release
$ cargo run --release -- start
What?
Here's what I'm shooting for:
- A terminal escape sequence parser
- A model of a terminal screen + scrollback that is OS independent
- Textual and GUI rendering of the model
- A differential protocol for the model
This would manifest as a common core that could run as both a textual terminal multiplexer and a gui terminal emulator, where the GUI part could automatically provide a native UI around the remotely multiplexed terminal session.
Status / Features - Beta Quality
There may be bugs that cause the terminal to panic. I'd recommend using
tmux
or screen
to keep your session alive if you are working on something important!
Despite the warning above, I've been using wezterm
as my daily driver since
the middle of Feb 2018. The following features are done:
- Runs on
- Linux under X (requires OpenGL ES 3)
- macOS
- Windows 10 with ConPty
- True Color support
- Ligatures, Color Emoji and font fallback
- Hyperlinks per: https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda
- Scrollback (use mouse wheel and Shift Page{Up|Down})
- xterm style selection of text with mouse; paste selection via Shift-Insert (bracketed paste is supported!)
- SGR style mouse reporting (works in vim and tmux)
- Render underline, double-underline, italic, bold, strikethrough
- Configuration file to specify fonts and colors
- Multiple Windows (Hotkey:
Super-N
) - Tabs (Hotkey:
Super-T
, next/prev:Super-[
andSuper-]
, go-to:Super-[0-9]
)
There's a good number of terminal escape sequences that are not yet implemented and that will get fleshed out as the applications I use uncover them, or as folks report them here and raise the priority. Similarly for key mappings. Please don't be shy about contributing support for missing things!
Things that I'd like to see happen and that have no immediate priority; contributions to get closer to these are welcomed!
- Sixel / iTerm2 graphics protocol support
- Textual renderer. Think
tmux
orscreen
. - Run on Linux with Wayland (use XWayland for now; See https://github.com/tomaka/winit/issues/306 for upstream blockers)
Configuration
wezterm
will look for a TOML configuration file in $HOME/.config/wezterm/wezterm.toml
,
and then in $HOME/.wezterm.toml
.
Configuration is currently very simple and the format is considered unstable and subject
to change. The code for configuration can be found in src/config.rs
.
I use the following in my ~/.wezterm.toml
:
font_size = 10
font = { font = [{family = "Operator Mono SSm Lig Medium"}] }
# How many lines of scrollback to retain
scrollback_lines = 3500
[[font_rules]]
italic = true
font = { font = [{family = "Operator Mono SSm Lig Medium", italic=true}]}
[[font_rules]]
italic = true
intensity = "Bold"
font = { font = [{family = "Operator Mono SSm Lig", italic=true, bold=true}]}
[[font_rules]]
intensity = "Bold"
[font_rules.font]
font = [{family = "Operator Mono SSm", bold=true}]
# if you liked xterm's `boldColor` setting, this is how you do it in wezterm,
# but you can apply it to any set of matching attributes!
foreground = "tomato"
[[font_rules]]
intensity = "Half"
font = { font=[{family = "Operator Mono SSm Lig Light" }]}
The default configuration will attempt to use whichever font is returned from
fontconfig when monospace
is requested.
Colors
You can configure colors with a section like this. In addition to specifying
SVG/CSS3 color names, you can use #RRGGBB
to specify a color code using the
usual hex notation; eg: #000000
is equivalent to black
:
[colors]
foreground = "silver"
background = "black"
cursor_bg = "springgreen"
ansi = ["black", "maroon", "green", "olive", "navy", "purple", "teal", "silver"]
brights = ["grey", "red", "lime", "yellow", "blue", "fuchsia", "aqua", "white"]
Performance
While ultimate speed is not the main goal, performance is important! Using the GPU to render the terminal contents helps keep CPU usage down and the output feeling snappy.
If you want the absolute fastest terminal emulator, alacritty is currently king of the crop.
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.