wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-09-20 19:27:22 +03:00
Code Issues Projects Releases Wiki Activity
2facc465ef
wezterm/mux/Cargo.toml

51 lines
1.3 KiB
TOML
Raw Normal View History

move mux to its own crate
2020-10-03 03:42:49 +03:00
[package]
name = "mux"
version = "0.1.0"
authors = ["Wez Furlong <wez@wezfurlong.org>"]
edition = "2018"
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
anyhow = "1.0"
async-trait = "0.1"
deps: misc updates
2020-12-29 20:21:50 +03:00
base64 = "0.13"
move mux to its own crate
2020-10-03 03:42:49 +03:00
bintree = { path = "../bintree" }
config = { path = "../config" }
deps: misc updates
2020-12-29 20:21:50 +03:00
crossbeam = "0.8"
move mux to its own crate
2020-10-03 03:42:49 +03:00
downcast-rs = "1.0"
filedescriptor: remove anyhow from public interface Use thiserror instead
2021-05-24 00:24:01 +03:00
filedescriptor = { version="0.8", path = "../filedescriptor" }
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
lazy_static = "1.4"
fixup build for macos
2020-10-05 19:11:17 +03:00
libc = "0.2"
move mux to its own crate
2020-10-03 03:42:49 +03:00
log = "0.4"
lua: add GuiWin and PaneObject proxies for use in script This commit adds very basic first passes at representing the Pane and GuiWindow types in lua script. The `open-uri` event from 9397f2a2dbdb47b43e18e5efdabf3ef8a0b18936 has been redefined to receive `(window, pane, uri)` parameters instead of its prior very basic `uri` parameter. A new key assignment `wezterm.action{EmitEvent="event-name"}` is now available that allows a key binding assignment to emit an arbitrary event, which in turn allows for triggering an arbitrary lua callback in response to a key or mouse click. `EmitEvent` passes the `(window, pane)` from the triggering window and pane as parameters. Here's a brief example: ```lua local wezterm = require 'wezterm'; wezterm.on("my-thingy", function(window, pane) local dims = pane:get_dimensions(); wezterm.log_error("did my thingy with window " .. window:window_id() .. " pane " .. pane:pane_id() .. " " .. dims.cols .. "x" .. dims.viewport_rows); window:perform_action("IncreaseFontSize", pane); end) return { keys = { {key="E", mods="CTRL", action=wezterm.action{EmitEvent="my-thingy"}}, } } ``` refs: #223 refs: #225
2020-10-09 23:45:34 +03:00
luahelper = { path = "../luahelper" }
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
metrics = { version="0.17", features=["std"]}
move mux to its own crate
2020-10-03 03:42:49 +03:00
portable-pty = { path = "../pty", features = ["serde_support"]}
promise = { path = "../promise" }
rangeset = { path = "../rangeset" }
ratelim= { path = "../ratelim" }
regex = "1"
serde = {version="1.0", features = ["rc", "derive"]}
RemoteSshDomain now uses wezterm-ssh crate There are a few notable changes as a result: * A number of `.ssh/config` options are now respected; host matching and aliasing and identity file are the main things * The authentication prompt is inline in the window, rather than popping up a separate authentication window Refs: https://github.com/wez/wezterm/issues/457
2021-03-28 03:49:30 +03:00
smol = "1.2"
tmux: attach control mode parser to terminal This causes `tmux -CC attach` to enter control mode and patch into the terminal, printing out parsed event messages. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 19:33:01 +03:00
terminfo = "0.7"
move mux to its own crate
2020-10-03 03:42:49 +03:00
termwiz = { path = "../termwiz" }
cargo update
2021-06-07 18:32:05 +03:00
textwrap = "0.14"
move mux to its own crate
2020-10-03 03:42:49 +03:00
thiserror = "1.0"
tmux: attach control mode parser to terminal This causes `tmux -CC attach` to enter control mode and patch into the terminal, printing out parsed event messages. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 19:33:01 +03:00
tmux-cc = { path = "../tmux-cc" }
wezterm: improve shaping of emoji This is one of those massive time sinks that I almost regret... As part of recent changes to dust-off the allsorts shaper, I noticed that the harfbuzz shaper wasn't shaping as well as the allsorts one. This commit: * Adds emoji-test.txt, a text file you can `cat` to see how well the emoji are shaped and rendered. * Fixes (or at least, improves) the column width calculation for combining sequences such as "deaf man" which was previously calculated at 3 cells in width when it should have just been 2 cells wide, which resulted in a weird "prismatic" effect during rendering where the glyph would be rendered with an extra RHS portion of the glyph across 3 cells. * Improved/simplified the clustering logic used to compute fallbacks. Previously we could end up with some wonky/disjoint sequence of undefined glyphs which wouldn't be successfully resolved from a fallback font. We now make a better effort to consolidate runs of undefined glyphs for fallback. * For sequences such as "woman with veil: dark skin tone" that occupy a single cell, the shaper may return 3 clusters with 3 glyphs in the case that the font doesn't fully support this grapheme. At render time we'd just take the last glyph from that sequence and render it, resulting in eg: a female symbol in this particular case. It is generally a bit more useful to show the first glyph in the sequence (eg: person with veil) rather than the gender or skin tone, so the renderer now checks for this kind of overlapping sequence and renders only the first glyph from the sequence.
2020-11-24 00:45:38 +03:00
unicode-segmentation = "1.7"
move mux to its own crate
2020-10-03 03:42:49 +03:00
url = "2"
RemoteSshDomain now uses wezterm-ssh crate There are a few notable changes as a result: * A number of `.ssh/config` options are now respected; host matching and aliasing and identity file are the main things * The authentication prompt is inline in the window, rather than popping up a separate authentication window Refs: https://github.com/wez/wezterm/issues/457
2021-03-28 03:49:30 +03:00
wezterm-ssh = { path = "../wezterm-ssh" }
move mux to its own crate
2020-10-03 03:42:49 +03:00
wezterm-term = { path = "../term", features=["use_serde"] }
maybe fix build on freebsd
2021-03-23 08:14:55 +03:00
conditionally include process divination for quit-confirm check on any win/linux/osx instead of all
2021-04-23 06:28:46 +03:00
[target.'cfg(any(windows, target_os="linux", target_os="macos"))'.dependencies]
maybe fix build on freebsd
2021-03-23 08:14:55 +03:00
sysinfo = "0.16"
add Pane::get_logical_lines refs: https://github.com/wez/wezterm/issues/527 refs: https://github.com/wez/wezterm/issues/408
2021-03-26 23:18:44 +03:00
windows: fix lingering cmd.exe panes Since removing the regular periodic background tasks, we're now prone to not noticing child processes exiting. This commit explicictly schedules a thread to do that on Windows so that we can close a tab as soon as it exits.
2021-05-29 01:08:21 +03:00
[target."cfg(windows)".dependencies]
winapi = { version = "0.3", features = [
"handleapi",
restructure async waiting Expand on the changes in 3f6ff534d3ad3df8bcf93dd02e1dd6dc3da1d7c2, this makes them more general and so that they can be used on unix systems. That in turn helps to tackle https://github.com/wez/wezterm/issues/839, wherein `sleep 300 & disown ; exit` would linger until EOF is detected, rather than triggering as soon as the child process terminated. For whatever reason, that would only manifest on linux (and not macos).
2021-06-01 08:28:14 +03:00
"processthreadsapi"
windows: fix lingering cmd.exe panes Since removing the regular periodic background tasks, we're now prone to not noticing child processes exiting. This commit explicictly schedules a thread to do that on Windows so that we can close a tab as soon as it exits.
2021-05-29 01:08:21 +03:00
]}
add Pane::get_logical_lines refs: https://github.com/wez/wezterm/issues/527 refs: https://github.com/wez/wezterm/issues/408
2021-03-26 23:18:44 +03:00
[dev-dependencies]
k9 = "0.11"
Reference in New Issue Copy Permalink