1
1
mirror of https://github.com/wez/wezterm.git synced 2024-10-28 09:22:19 +03:00
A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust
Go to file
Wez Furlong dc3f2f0572 add launcher overlay
This is accessible by right-clicking on the `+` button in the tab bar
and switches to an overlay offering options to spawn tabs and attach
domains.

The intent is to allow the configuration file to expand this list of
options, and on Windows, to auto-populate with the various combinations
of `cmd`, `powershell`, `elevated` and available `wsl` instances, but
for the moment the main value of this feature is the ability to attach
domains that were not set to connect automatically at startup.

This makes things more convenient when launching wezterm via the
gui: it is awkward to have to set up shortcuts that run
`wezterm connect foo`, or to type in the full path to `wezterm` when
you might want to run that manually.

Now you can double-click the icon and right-click the `+` and attach
the domain. (cc: @rjwalsh)

The launcher is a good candidate for being implemented on top of
native context menus where available... but we don't have any
such API plumbed through the `window` crate, so all platforms
get the wonderful terminal based overlay menu right now.

refs: https://github.com/wez/wezterm/issues/159
2020-03-02 09:12:58 -08:00
.cargo build static on windows for static openssl linkage 2020-02-02 13:03:07 -08:00
.github remove build problem section from the bug report template 2020-02-15 20:24:01 -08:00
assets First pass at building an AppImage (#125) 2020-01-20 23:11:38 -08:00
base91 dyn everywhere 2019-06-08 21:28:11 -07:00
ci ci: point to a version that has node_modules 2020-02-14 15:53:32 -08:00
deps try to target older macos releases 2020-01-27 00:12:47 -08:00
docs add launcher overlay 2020-03-02 09:12:58 -08:00
filedescriptor filedescriptor: macos: mem::uninitialized -> MaybeUninit 2020-01-26 19:07:19 -08:00
promise promise: add tokio_spawn helper 2020-01-20 07:55:51 -08:00
pty ssh2: update to 0.8 2020-02-22 08:50:13 -08:00
rangeset mux: reintroduce server side state to gate pushes 2020-01-10 08:56:27 -08:00
src add launcher overlay 2020-03-02 09:12:58 -08:00
tabout tabout: correctly handle unicode width 2020-01-05 14:37:17 -08:00
term fixup term tests for set_title cleanup 2020-01-26 10:02:07 -08:00
termwiz mux: fix poll interval. show update indicator 2020-02-23 09:08:04 -08:00
vtparse vtparse: bump version for publish 2020-02-22 07:32:52 -08:00
window wayland: remove a debug print 2020-02-26 23:21:59 -08:00
.gitignore First pass at building an AppImage (#125) 2020-01-20 23:11:38 -08:00
.gitmodules fix CI: savannah is down, use a github mirror for freetype 2019-11-24 13:28:02 -08:00
.rustfmt.toml Make rustfmt happy about "async move" 2020-01-20 13:58:21 -08:00
build.rs CI: target older macos versions 2020-01-24 16:24:45 -08:00
Cargo.lock lua: give a nice error message when using an invalid field name 2020-03-01 09:39:14 -08:00
Cargo.toml lua: give a nice error message when using an invalid field name 2020-03-01 09:39:14 -08:00
CONTRIBUTING.md Add get-deps script for installing dependencies 2018-02-25 09:24:56 -08:00
get-deps CI: build rpms for centos 7 2020-02-12 08:30:41 -08:00
install.sh refine deploy scripts/config 2019-03-24 00:26:53 -07:00
LICENSE.md flesh out some details prior to pushing to github 2018-02-06 21:32:40 -08:00
README.md ci: remove old badges from readme 2020-02-12 13:21:57 -08:00
wt-record update record/play scripts for macos 2019-03-22 20:41:50 -07:00
wt-replay update record/play scripts for macos 2019-03-22 20:41:50 -07:00

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

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:

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.