wezterm/promise/Cargo.toml

[package]
authors = ["Wez Furlong <wez@wezfurlong.org>"]
name = "promise"
version = "0.2.0"
edition = "2018"

[dependencies]
async-task = "4.0"
async-executor = "1.4"
async-io = "1.10"
anyhow = "1.0"
thiserror = "1.0"
lazy_static = "1.4"
flume = "0.10"
move promise to its own crate 2019-03-04 18:38:56 +03:00			`[package]`
			`authors = ["Wez Furlong <wez@wezfurlong.org>"]`
			`name = "promise"`
failure -> anyhow + thiserror 2019-12-15 08:43:05 +03:00			`version = "0.2.0"`
move promise to its own crate 2019-03-04 18:38:56 +03:00			`edition = "2018"`

			`[dependencies]`
upgrade misc deps, notably, async-task 2020-10-05 10:06:01 +03:00			`async-task = "4.0"`
wezterm-gui start now prefers to run via existing gui instance Using the new publish/discovery stuff from the past couple of commits, if we can find a matching socket path for a running gui, and the configuration is likely a match, then use the mux protocol to talk to the already running gui and ask it to spawn the equivalent program into the same process. refs: https://github.com/wez/wezterm/discussions/1486 2022-01-07 21:39:37 +03:00			`async-executor = "1.4"`
deps: remove async-std dep We were only using block_on from it, which we can call from the underlying async_io crate. Notably, removing async_std from the deps avoids async-global-executor being pulled in and spawning nproc threads that are never used by wezterm. 2022-11-01 17:05:33 +03:00			`async-io = "1.10"`
failure -> anyhow + thiserror 2019-12-15 08:43:05 +03:00			`anyhow = "1.0"`
			`thiserror = "1.0"`
deps: normalize the lazy-static version 2020-11-13 18:57:09 +03:00			`lazy_static = "1.4"`
deps: misc updates 2020-12-29 20:21:50 +03:00			`flume = "0.10"`