wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-12-18 02:42:05 +03:00
Code Issues Projects Releases Wiki Activity
546b456f0d
wezterm/Cargo.lock

5440 lines
123 KiB
Plaintext
Raw Normal View History

Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
# This file is automatically @generated by Cargo.
# It is not intended for manual editing.
update k9 to 0.11.0 to make it work with rustc@1.51.0 1.51.0 no longer takes non string literals in `panic()`. k9@0.11.0 fixes that
2021-03-25 20:32:31 +03:00
version = 3
cargo update
2020-05-26 08:25:39 +03:00
[[package]]
name = "addr2line"
cargo update
2021-11-03 16:41:06 +03:00
version = "0.17.0"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-11-03 16:41:06 +03:00
checksum = "b9ecd88a8c8378ca913a680cd98f0f13ac67383d35993f86c90a70e3f137816b"
cargo update
2020-05-26 08:25:39 +03:00
dependencies = [
"gimli",
]
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "adler"
cargo update
2021-03-01 20:02:05 +03:00
version = "1.0.2"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-01 20:02:05 +03:00
checksum = "f26201604c87b1e01bd3d98f8d5d9a8fcbb815e8cedb41ffccbeb4bf593a35fe"
cargo update
2020-06-30 03:52:14 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "adler32"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.2.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "aae1277d39aeec15cb388266ecc24b11c80469deae6067e17a1a7aa9e5c1f234"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
[[package]]
name = "ahash"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
version = "0.7.6"
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
checksum = "fcb51a0695d8f838b1ee009b3fbf66bda078cd64590202a864a8f3e8c4315c47"
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
dependencies = [
cargo update
2022-04-04 04:26:59 +03:00
"getrandom 0.2.6",
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
"once_cell",
"version_check",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "aho-corasick"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.7.18"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "1e37cfd5e7657ada45f742d6e99ca5788580b5c529dc78faf11ece6dc702656f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"memchr",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2021-12-06 05:07:49 +03:00
[[package]]
name = "ansi_term"
version = "0.12.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d52a9bb7ec0cf484c551830a7ce27bd20d67eac647e1befb56b0be4ee39a55d2"
dependencies = [
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "anyhow"
deps: cargo update
2022-04-25 02:41:29 +03:00
version = "1.0.57"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-25 02:41:29 +03:00
checksum = "08f9b8508dccb7687a1d6c4ce66b2b0ecef467c94667de27d8d7fe1f8d2a9cdc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
zeno -> tiny_skia Mostly so that we can turn off anti-aliasing for smaller sizes, but it also happens to be more complete anyway.
2021-06-26 08:55:42 +03:00
[[package]]
name = "arrayref"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a4c527152e37cf757a3f78aae5a06fbeefdb07ccc535c980a3208ee3060dd544"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "arrayvec"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.5.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "23b62fc65de8e4e7f52534fb52b0f3ed04746ae267519eef2a83941e8085068b"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "assert_fs"
cargo update
2022-01-17 04:46:30 +03:00
version = "1.0.7"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "cf09bb72e00da477c2596865e8873227e2196d263cca35414048875dbbeea1be"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
dependencies = [
"doc-comment",
"globwalk",
"predicates",
"predicates-core",
"predicates-tree",
"tempfile",
]
cargo update
2022-05-16 05:44:27 +03:00
[[package]]
name = "async-attributes"
version = "1.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a3203e79f4dd9bdda415ed03cf14dae5a2bf775c683a00f94e9cd1faf0f596e5"
dependencies = [
"quote",
"syn",
]
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
[[package]]
name = "async-broadcast"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.4.0"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "1bbd92a9bd0e9c1298118ecf8a2f825e86b12c3ec9e411573e34aaf3a0c03cdd"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
dependencies = [
"easy-parallel",
"event-listener",
"futures-core",
cargo update
2022-05-02 07:21:14 +03:00
"parking_lot 0.11.2",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "async-channel"
cargo update
2021-02-22 11:09:01 +03:00
version = "1.6.1"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-22 11:09:01 +03:00
checksum = "2114d64672151c0c5eaa5e131ec84a74f06e1e559830dabba01ca30605d66319"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"concurrent-queue",
"event-listener",
"futures-core",
]
[[package]]
name = "async-executor"
cargo update
2021-04-26 18:34:45 +03:00
version = "1.4.1"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "871f9bb5e0a22eeb7e8cf16641feb87c9dc67032ccf8ff49e772eb9941d3a965"
cargo update
2020-10-02 17:16:20 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
cargo update
2020-10-02 17:16:20 +03:00
"concurrent-queue",
"fastrand",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-10-02 17:16:20 +03:00
"once_cell",
cargo update
2021-04-26 18:34:45 +03:00
"slab",
cargo update
2020-10-02 17:16:20 +03:00
]
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
[[package]]
name = "async-fs"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.5.0"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "8b3ca4f8ff117c37c278a2f7415ce9be55560b846b5bc4412aaa5d29c1c3dae2"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"async-lock",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"blocking",
"futures-lite",
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "async-global-executor"
cargo update
2022-04-04 04:26:59 +03:00
version = "2.0.4"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "c290043c9a95b05d45e952fb6383c67bcb61471f60cfa21e890dba6654234f43"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
cargo update
2021-01-18 10:38:11 +03:00
"async-channel",
cargo update
2020-10-02 17:16:20 +03:00
"async-executor",
cargo update
2020-09-09 19:31:37 +03:00
"async-io",
cargo update
2021-01-18 10:38:11 +03:00
"async-mutex",
"blocking",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-10-02 17:16:20 +03:00
"num_cpus",
"once_cell",
cargo update
2020-09-09 19:31:37 +03:00
]
[[package]]
name = "async-io"
cargo update
2021-07-07 23:27:08 +03:00
version = "1.6.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-07-07 23:27:08 +03:00
checksum = "a811e6a479f2439f0c04038796b5cfb3d2ad56c230e0f2d3f7b04d68cfee607b"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"concurrent-queue",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"libc",
cargo update
2020-10-02 17:16:20 +03:00
"log",
cargo update
2020-09-09 19:31:37 +03:00
"once_cell",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"parking",
cargo update
2020-09-09 19:31:37 +03:00
"polling",
cargo update
2021-04-26 18:34:45 +03:00
"slab",
cargo update
2021-04-19 19:23:33 +03:00
"socket2",
cargo update
2020-10-02 17:16:20 +03:00
"waker-fn",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"winapi 0.3.9",
cargo update
2020-09-09 19:31:37 +03:00
]
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
[[package]]
name = "async-lock"
cargo update
2022-02-22 05:44:27 +03:00
version = "2.5.0"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-22 05:44:27 +03:00
checksum = "e97a171d191782fba31bb902b14ad94e24a68145032b7eedf871ab0bc0d077b6"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"event-listener",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "async-mutex"
cargo update
2020-10-02 17:16:20 +03:00
version = "1.4.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-10-02 17:16:20 +03:00
checksum = "479db852db25d9dbf6204e6cb6253698f175c15726470f78af0d918e99d6156e"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"event-listener",
]
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
[[package]]
name = "async-net"
cargo update
2021-07-07 23:27:08 +03:00
version = "1.6.1"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-07-07 23:27:08 +03:00
checksum = "5373304df79b9b4395068fb080369ec7178608827306ce4d081cba51cac551df"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
"async-io",
"blocking",
"futures-lite",
]
[[package]]
name = "async-process"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.4.0"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "cf2c06e30a24e8c78a3987d07f0930edf76ef35e027e7bdb063fccafdad1f60c"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
"async-io",
"blocking",
cargo update
2021-02-08 09:51:28 +03:00
"cfg-if 1.0.0",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"event-listener",
"futures-lite",
cargo update
2021-04-26 18:34:45 +03:00
"libc",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"once_cell",
deps: update
2021-12-20 18:15:56 +03:00
"signal-hook 0.3.13",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"winapi 0.3.9",
]
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
[[package]]
name = "async-recursion"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d7d78656ba01f1b93024b7c3a0467f1608e4be67d725749fdcd7d2c7678fd7a2"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "async-std"
deps: cargo update
2022-03-28 05:47:26 +03:00
version = "1.11.0"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-28 05:47:26 +03:00
checksum = "52580991739c5cdb36cde8b2a516371c0a3b70dda36d916cc08b82372916808c"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
dependencies = [
cargo update
2022-05-16 05:44:27 +03:00
"async-attributes",
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
"async-channel",
cargo update
2020-10-02 17:16:20 +03:00
"async-global-executor",
cargo update
2020-09-09 19:31:37 +03:00
"async-io",
cargo update
2021-01-18 10:38:11 +03:00
"async-lock",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
cargo update
2020-05-26 08:25:39 +03:00
"futures-channel",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"futures-core",
"futures-io",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-10-02 17:16:20 +03:00
"gloo-timers",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"kv-log-macro",
"log",
"memchr",
"num_cpus",
"once_cell",
cargo update
2020-12-20 03:44:27 +03:00
"pin-project-lite",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"pin-utils",
"slab",
cargo update
2020-05-26 08:25:39 +03:00
"wasm-bindgen-futures",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "async-task"
cargo update
2022-03-09 17:31:53 +03:00
version = "4.2.0"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-03-09 17:31:53 +03:00
checksum = "30696a84d817107fc028e049980e09d5e140e8da8f1caeb17e8e950658a3cea9"
cargo update
2020-10-02 17:16:20 +03:00
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
[[package]]
name = "async-trait"
deps: cargo update
2022-03-28 05:47:26 +03:00
version = "0.1.53"
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-28 05:47:26 +03:00
checksum = "ed6aa3524a2dfcf9fe180c51eae2b58738348d819517ceadf95789c51fff7600"
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
]
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
[[package]]
name = "async_ossl"
version = "0.1.0"
dependencies = [
"openssl",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "atomic-waker"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "065374052e7df7ee4047b1160cca5e1467a12351a40b3da123c870ba0b8eda2a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "atty"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.2.14"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hermit-abi",
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
bump some versions
2020-01-10 09:39:34 +03:00
[[package]]
name = "autocfg"
cargo update
2022-02-14 06:31:40 +03:00
version = "1.1.0"
bump some versions
2020-01-10 09:39:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-14 06:31:40 +03:00
checksum = "d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa"
bump some versions
2020-01-10 09:39:34 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "backtrace"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "0.3.65"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "11a17d453482a265fd5f8479f2a3f405566e6ca627837aaddb85af8b1ab8ef61"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-05-26 08:25:39 +03:00
"addr2line",
cargo update
2021-05-01 19:42:46 +03:00
"cc",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
deps: cargo update
2022-04-19 06:51:19 +03:00
"miniz_oxide 0.5.1",
cargo update
2020-05-26 08:25:39 +03:00
"object",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rustc-demangle",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
[[package]]
name = "base64"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.13.0"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "904dfeac50f3cdaba28fc6f57fdcddb75f49ed61346676a78c4ffe55877802fd"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "base91"
version = "0.1.0"
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
[[package]]
name = "battery"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"luahelper",
"starship-battery",
"wezterm-dynamic",
]
benchmarking shaping `cargo test --release -p wezterm-gui -- --nocapture bench_shaping`: ``` running 1 test 100: 139.82µs 1000: 385.333µs 10000: 3.144203ms test shapecache::test::bench_shaping ... ok ```
2021-04-28 07:48:15 +03:00
[[package]]
name = "benchmarking"
cargo update
2022-03-09 17:31:53 +03:00
version = "0.4.11"
benchmarking shaping `cargo test --release -p wezterm-gui -- --nocapture bench_shaping`: ``` running 1 test 100: 139.82µs 1000: 385.333µs 10000: 3.144203ms test shapecache::test::bench_shaping ... ok ```
2021-04-28 07:48:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-03-09 17:31:53 +03:00
checksum = "3937429ef059161c005a608ae02451b64e5e98d26d2038f43674f506b571bad6"
benchmarking shaping `cargo test --release -p wezterm-gui -- --nocapture bench_shaping`: ``` running 1 test 100: 139.82µs 1000: 385.333µs 10000: 3.144203ms test shapecache::test::bench_shaping ... ok ```
2021-04-28 07:48:15 +03:00
bintree: introduce a binary tree + zipper impl The intent is for this to help manage panes, but it is reasonably general purpose so it is broken out separately.
2020-07-01 06:21:27 +03:00
[[package]]
name = "bintree"
version = "0.1.0"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "bit_field"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dcb6dd1c2376d2e096796e234a70e17e94cc2d5d54ff8ce42b28cef1d0d359a4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "bitflags"
cargo update
2021-08-23 17:33:44 +03:00
version = "1.3.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-23 17:33:44 +03:00
checksum = "bef38d45163c2f1dde094a7dfd33ccf595c92905c8f8f4fdc18d06fb1037718a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "block"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "0d8c1fef690941d3e7788d328517591fecc684c084084702d6ff1641e993699a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "block-buffer"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0940dc441f31689269e10ac70eb1002a3a1d3ad1390e030043662eb7fe4688b"
dependencies = [
"block-padding",
"byte-tools",
"byteorder",
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
"generic-array 0.12.4",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "block-buffer"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4152116fd6e9dadb291ae18fc1ec3575ed6d84c29642d97890f4b4a3417297e4"
dependencies = [
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
"generic-array 0.14.5",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
]
[[package]]
name = "block-padding"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa79dedbb091f449f1f39e53edf88d5dbe95f895dae6135a8d7b881fb5af73f5"
dependencies = [
"byte-tools",
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "blocking"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "1.2.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "c6ccb65d468978a086b69884437ded69a90faab3bbe6e67f242173ea728acccc"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"async-channel",
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
cargo update
2020-09-09 19:31:37 +03:00
"atomic-waker",
cargo update
2020-10-02 17:16:20 +03:00
"fastrand",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-06-30 03:52:14 +03:00
"once_cell",
]
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
[[package]]
name = "bstr"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "59604ece62a407dc9164732e5adea02467898954c3a5811fd2dc140af14ef15b"
dependencies = [
"lazy_static",
"memchr",
"regex-automata",
]
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
[[package]]
name = "bstr"
deps: cargo update
2021-10-04 08:10:01 +03:00
version = "0.2.17"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2021-10-04 08:10:01 +03:00
checksum = "ba3569f383e8f1598449f1a423e72e99569137b47740b1da11ef19af3d5c3223"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
dependencies = [
lua: add serde-powered to_lua_value function This will help in implementing lua helper functions for various config and other structures.
2020-03-01 08:46:59 +03:00
"lazy_static",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
"memchr",
lua: add serde-powered to_lua_value function This will help in implementing lua helper functions for various config and other structures.
2020-03-01 08:46:59 +03:00
"regex-automata",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "bumpalo"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "3.9.1"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "a4a45a46ab1f2412e53d3a0ade76ffad2025804294569aae387231a0cd6e0899"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "byte-tools"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e3b5ca7a04898ad4bcd41c90c5285445ff5b791899bb1b0abdd2a2aa791211d7"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "bytemuck"
cargo update
2022-04-04 04:26:59 +03:00
version = "1.9.1"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "cdead85bdec19c194affaeeb670c0e41fe23de31459efd1c174d049269cf02cc"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "byteorder"
cargo update
2021-03-15 16:32:14 +03:00
version = "1.4.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-15 16:32:14 +03:00
checksum = "14c189c53d098945499cdfa7ecc63567cf3886b3332b312a5b4585d8d3a6a610"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
window: add xsettings support on X11 systems This allows reading xsettings which contain information about both the active theme as well as the DPI. refs: #947
2021-07-18 22:52:20 +03:00
[[package]]
name = "bytes"
cargo update
2021-08-25 20:00:33 +03:00
version = "1.1.0"
window: add xsettings support on X11 systems This allows reading xsettings which contain information about both the active theme as well as the DPI. refs: #947
2021-07-18 22:52:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-25 20:00:33 +03:00
checksum = "c4872d67bab6358e59559027aa3b9157c53d9358c51423c17554809a8858e0f8"
window: add xsettings support on X11 systems This allows reading xsettings which contain information about both the active theme as well as the DPI. refs: #947
2021-07-18 22:52:20 +03:00
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "cache-padded"
deps: update
2021-12-20 18:15:56 +03:00
version = "1.2.0"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update
2021-12-20 18:15:56 +03:00
checksum = "c1db59621ec70f09c5e9b597b220c7a2b43611f4710dc03ceb8748637775692c"
promise: add tokio_spawn helper This starts up the tokio runtime on a secondary thread and spawns a future into it.
2020-01-19 20:59:30 +03:00
Switch to camino::{Utf8PathBuf, Utf8Path}
2021-10-04 04:36:30 +03:00
[[package]]
name = "camino"
cargo update
2022-05-16 05:44:27 +03:00
version = "1.0.8"
Switch to camino::{Utf8PathBuf, Utf8Path}
2021-10-04 04:36:30 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "07fd178c5af4d59e83498ef15cf3f154e1a6f9d091270cb86283c65ef44e9ef0"
Switch to camino::{Utf8PathBuf, Utf8Path}
2021-10-04 04:36:30 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "cassowary"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "df8670b8c7b9dae1793364eafadf7239c40d669904660c5960d74cfd80b46a53"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "cc"
cargo update
2022-02-22 05:44:27 +03:00
version = "1.0.73"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-22 05:44:27 +03:00
checksum = "2fff2a6927b3bb87f9595d67196a70493f627687a71d87a0d692242c33f58c11"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"jobserver",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "cfg-if"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "cgl"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "0ced0551234e87afee12411d535648dd89d2e7f34c78b753395567aff3d447ff"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "chrono"
cargo update
2020-10-02 17:16:20 +03:00
version = "0.4.19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-10-02 17:16:20 +03:00
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-10-02 17:16:20 +03:00
"libc",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"num-integer",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
"pure-rust-locales",
mux: track list of clients Define a way to compute a client ID and pass that through to the mux server when verifying version compatibility. Once associated, the session handler will keep some metadata updated in the mux. A new cli subcommand exposes the info: ``` ; ./target/debug/wezterm cli list-clients USER HOST PID CONNECTED IDLE WORKSPACE wez mba.localdomain 52979 30.009225s 1.009225s ``` refs: #1531
2022-01-12 08:39:19 +03:00
"serde",
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
"time 0.1.43",
cargo update
2020-10-02 17:16:20 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "clap"
cargo update
2021-12-06 05:07:49 +03:00
version = "2.34.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-12-06 05:07:49 +03:00
checksum = "a0610544180c38b88101fecf2dd634b174a62eef6946f84dfc6a7127512b381c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: replace pretty_assertions dep with k9
2022-05-05 04:51:51 +03:00
"ansi_term",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"atty",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
lua: give a nice error message when using an invalid field name Make a reasonable suggestion to the user based on similarity with possible field names, but don't error out. This facilitates evolving the configuration over time, and makes the config more forgiving of typos.
2020-03-01 20:39:14 +03:00
"strsim 0.8.0",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"textwrap 0.11.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-width",
"vec_map",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
name = "clipboard-win"
version = "2.2.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
checksum = "e3a093d6fed558e5fe24c3dfc85a68bb68f1c824f440d3ba5aca189e2998786b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
name = "clipboard_macos"
version = "0.1.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
checksum = "145a7f9e9b89453bc0a5e32d166456405d389cea5b578f57f1274b1397588a95"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
"objc",
"objc-foundation",
"objc_id",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "cocoa"
cargo update
2020-06-30 03:52:14 +03:00
version = "0.20.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "0c49e86fc36d5704151f5996b7b3795385f50ce09e3be0f47a0cfde869681cf8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"block",
"core-foundation 0.7.0",
cargo update
2020-06-30 03:52:14 +03:00
"core-graphics 0.19.2",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
"objc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
move codec into is own crate
2020-10-03 08:39:15 +03:00
[[package]]
name = "codec"
version = "0.1.0"
dependencies = [
"anyhow",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"base91",
move codec into is own crate
2020-10-03 08:39:15 +03:00
"config",
"leb128",
"log",
"metrics",
"mux",
"portable-pty",
"rangeset",
"serde",
codec: add async read/write methods
2020-10-03 19:15:47 +03:00
"smol",
move codec into is own crate
2020-10-03 08:39:15 +03:00
"termwiz",
mux: try to detect invalid data on stdout during connection Use some heuristics to verify the data that is about to be parsed; this can help to detect eg: data being output to stdout prior to us sending any encoded data to the remote mux. In addition, add a timeout to help avoid waiting forever in the case that we didn't detect a problem. refs: https://github.com/wez/wezterm/issues/1860
2022-04-12 07:08:57 +03:00
"thiserror",
move codec into is own crate
2020-10-03 08:39:15 +03:00
"varbincode",
"wezterm-term",
"zstd",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "color_quant"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.1.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "3d7b894f5411737b7867f4827955924d7c254fc9f4d91a6aad6b097804b1018b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "colored"
version = "1.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4ffc801dacf156c5854b9df4f425a626539c3a6ef7893cc0c5084a23f0b6c59"
dependencies = [
"atty",
"lazy_static",
"winapi 0.3.9",
]
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
[[package]]
name = "colorgrad"
deps: colorgrad -> 0.5
2021-09-06 09:27:01 +03:00
version = "0.5.0"
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: colorgrad -> 0.5
2021-09-06 09:27:01 +03:00
checksum = "62c834d2dcb442c0fdf4775e72707db38c5a358a6da74f3041f93563d02ce306"
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
dependencies = [
"csscolorparser",
]
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "concurrent-queue"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.2.2"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "30ed07550be01594c6026cff2a1d7fe9c8f683caa798e12b68694ac9e88286a3"
cargo update
2020-06-30 03:52:14 +03:00
dependencies = [
"cache-padded",
]
move config into its own crate
2020-10-02 21:50:50 +03:00
[[package]]
name = "config"
version = "0.1.0"
dependencies = [
"anyhow",
introduce freetype_load_flags and freetype_load_target config In the earlier times wezterm supported different font rasterizers, and the configuration was a bit vague and generic to accomodate differences in how the rasterizers worked. Since then, we've standardized on freetype. One of the things that's been bothering me for a while is that we have some fiddly logic to transform from the config to the freetype flags. This commit does away with the transformation and simply exposes the two sets of freetype options. The main thing that I expect people to play with is `freetype_load_target` which can have one of the following values: ``` pub enum FreeTypeLoadTarget { /// This corresponds to the default hinting algorithm, optimized for standard gray-level rendering. Normal, /// A lighter hinting algorithm for non-monochrome modes. Many generated glyphs are more fuzzy but better resemble its original shape. A bit like rendering on Mac OS X. This target implies FT_LOAD_FORCE_AUTOHINT. Light, /// Strong hinting algorithm that should only be used for monochrome output. The result is probably unpleasant if the glyph is rendered in non-monochrome modes. Mono, /// A variant of Normal optimized for horizontally decimated LCD displays. HorizontalLcd, /// A variant of Normal optimized for vertically decimated LCD displays. VerticalLcd, } ``` I expect most people will want to set this to one of `Normal`, `Light` or `HorizontalLcd`. `HorizontalLcd` is what `font_antialias=Subpixel` used to select. refs: #491
2021-02-21 00:54:56 +03:00
"bitflags",
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
"chrono",
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
"colorgrad",
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
"dirs-next",
Allow matching font weight and font width in `wezterm.font` refs: https://github.com/wez/wezterm/issues/655
2021-04-09 01:41:07 +03:00
"enum-display-derive",
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
clean up mux server startup kindof a lot going on in this commit, unintentionally: * Need the lua context set to be moved into the config crate otherwise configs cannot be parsed by the server and we end up with the default configs * Make the server use smol for async io * Drop the use of the daemonize crate, which I had forked anyway. Just inline our own tighter daemonize module * Improve daemon spawning synchronization, however, it still needs work for windows to avoid blocking forever where we don't do daemonizing.
2020-10-04 19:39:28 +03:00
"hostname",
move config into its own crate
2020-10-02 21:50:50 +03:00
"lazy_static",
move running_under_wsl to config crate
2020-10-03 06:51:50 +03:00
"libc",
move config into its own crate
2020-10-02 21:50:50 +03:00
"log",
"luahelper",
"mlua",
"notify",
FEATURE: Allow ScrollByPage f64 values `ScrollByPage` can accept non-integer values in the configuration. This allows fractional page scrolling, such as by half a page. The default remains the same, at 1 page.
2022-01-12 08:49:36 +03:00
"ordered-float",
move config into its own crate
2020-10-02 21:50:50 +03:00
"portable-pty",
wezterm: allow overriding the default open-uri event This builds on the new lua event handler plumbing added in ccea650a93c4f8ce29703ba2e1c0e91ff00d9046 to co-opt the default URI opening action: ```lua wezterm.on("open-uri", function(uri) if uri:find("jira") then wezterm.log_error("do something with jira") wezterm.run_child_process({ "wezterm", "start", "--", "jira", "view", extract_task_from_uri(uri) }) -- prevent the default action from opening in a browser return false else -- log but allow the uri to be opened in the browser wezterm.log_error("clicken " .. uri) end end) ``` This doesn't allow exactly the sketched out option from issue #223 to be implemented, but may be close enough to be useful. refs: #223 refs: #225
2020-10-08 04:19:14 +03:00
"promise",
move config into its own crate
2020-10-02 21:50:50 +03:00
"serde",
introduce quote_dropped_files config option Signed-off-by: Ye Sijun <junnplus@gmail.com>
2022-04-25 09:31:33 +03:00
"shlex",
add wezterm.on(), wezterm.emit() * `wezterm.on("event-name", func)` * `wezterm.emit("event-name", "arg1", "arg2")` `on` allows registering multiple functions. `emit` will call each of the registered functions in turn, passing a copy of the arguments. If a handler returns false, no additional handlers are called and `emit` will return false. Otherwise, once all the handlers have been called, `emit` will return true. `emit` is capable of being called by async code. These functions are available to the config layer, but nothing in wezterm uses them at this time. refs: #225
2020-10-07 08:04:48 +03:00
"smol",
move config into its own crate
2020-10-02 21:50:50 +03:00
"termwiz",
"toml",
Take care to restore the original umask wezterm sets a more restrictive umask (`0o077`) by default so that any files that it creates (eg: unix domain socket, log files) are more secure by default. However, some environments rely on the more general default of (`0o022`) without checking that it is set. This matters because programs spawned by wezterm inherit its more restricted umask. I hadn't noticed this because I've had `umask 022` in my shell RC files since sometime in the 1990's. This commit adds some plumbing to the pty layer to specify an optional umask for the child process, and some more to our umask saver helper so that any thread can determine the saved umask without needing a reference to the saver itself, which may be in a different crate. The logic in the config crate has been adjusted to connect the saved value to the default command builder arguments. The net result of this is that running `wezterm -n start bash -- --norc` and typing `umask` in the resultant window now prints `0022`. refs: #416
2021-01-07 20:14:51 +03:00
"umask",
bidi: tag Line with bidi mode This commit refines bidi property handling: * experimental_bidi has been split into two new configuration settings; `bidi_enabled` (which controls whether the terminal performs implicit bidi processing) and `bidi_direction` which specifies the base direction and whether auto detection is enabled. * The `Line` type can now store those bidi properties (they are actually split across 3 bits representing enabled, auto-detection and direction) * The terminal now has a concept of active bidi properties and default bidi properties * The default properties are pulled from the wezterm configuration * active bidi properties are potentially set via escape sequences, BDSM (which sets bidi_enabled) and SCP (which sets bidi_direction). We don't support the 2501 temporary dec private mode suggested by the BIDI recommendation doc at this time. * When creating new `Line`'s or clearing from the start of a `Line`, the effective bidi properties are computed (from the active props, falling back to default propr) and applied to the `Line`. * When rendering the line, we now look at its bidi properties instead of just the global config. The default bidi properties are `bidi_enabled: false` and `bidi_direction: LeftToRight` which corresponds to the typical bidi-unaware mode of most terminals. It is possible to live reload the config to change the effective defaults, but note that they apply, by design, to new lines being processed through the terminal. That means existing output is left unaffected by a config reload, but subsequently printed lines will respect it. Pressing CTRL-L or otherwise contriving to have the running application refresh its display should cause the refreshed display to update and apply the new bidi mode. refs: #784
2022-01-30 19:22:17 +03:00
"wezterm-bidi",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
"wezterm-input-types",
move config into its own crate
2020-10-02 21:50:50 +03:00
"wezterm-term",
and another speculative diff to fixup windows build
2020-10-05 23:56:11 +03:00
"winapi 0.3.9",
move config into its own crate
2020-10-02 21:50:50 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "core-foundation"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
version = "0.7.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
checksum = "57d24c7a13c43e870e37c1556b74555437870a04514f7685f5b354e090567171"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
"core-foundation-sys 0.7.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "core-foundation"
cargo update
2022-02-14 06:31:40 +03:00
version = "0.9.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-14 06:31:40 +03:00
checksum = "194a7a9e6de53fa55116934067c844d9d749312f75c6f6d0980e8c252f8c2146"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
"core-foundation-sys 0.8.3",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "core-foundation-sys"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
version = "0.7.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
checksum = "b3a71ab494c0b5b860bdc8407ae08978052417070c2ced38573a9157ad75b8ac"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "core-foundation-sys"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
version = "0.8.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
checksum = "5827cebf4670468b8772dd191856768aedcb1b0278a04f989f7766351917b9dc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "core-graphics"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
version = "0.19.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
checksum = "b3889374e6ea6ab25dba90bb5d96202f61108058361f6dc72e8b03e6f8bbe923"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
"core-foundation 0.7.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "core-graphics"
cargo update
2021-11-03 16:41:06 +03:00
version = "0.22.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-11-03 16:41:06 +03:00
checksum = "2581bbab3b8ffc6fcbd550bf46c355135d16e9ff2a6ea032ad6b9bf1d7efe4fb"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update
2022-02-14 06:31:40 +03:00
"core-foundation 0.9.3",
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
"core-graphics-types",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
name = "core-graphics-types"
version = "0.1.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
checksum = "3a68b68b3446082644c91ac778bf50cd4104bfb002b5a6a7c44cca5a2c70788b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update
2022-02-14 06:31:40 +03:00
"core-foundation 0.9.3",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "core-text"
cargo update
2021-02-15 23:14:00 +03:00
version = "19.2.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-15 23:14:00 +03:00
checksum = "99d74ada66e07c1cefa18f8abfba765b486f250de2e4a999e5727fc0dd4b4a25"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2022-02-14 06:31:40 +03:00
"core-foundation 0.9.3",
cargo update
2021-11-03 16:41:06 +03:00
"core-graphics 0.22.3",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
cargo update
2021-05-12 03:03:06 +03:00
name = "cpufeatures"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.2.2"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "59a6001667ab124aebae2a495118e11d30984c3a653e99d86d58971708cf5e4b"
cargo update
2021-05-12 03:03:06 +03:00
dependencies = [
"libc",
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "crc32fast"
cargo update
2022-02-14 06:31:40 +03:00
version = "1.3.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-14 06:31:40 +03:00
checksum = "b540bd8bc810d3885c6ea91e2018302f68baba2129ab3e88f32389ee9370880d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
ssh: use a single window for authenticating a session This makes it so that we preserve context while showing the connection status and authentication prompts.
2020-01-26 00:00:16 +03:00
[[package]]
name = "crossbeam"
cargo update
2021-05-31 09:06:36 +03:00
version = "0.8.1"
ssh: use a single window for authenticating a session This makes it so that we preserve context while showing the connection status and authentication prompts.
2020-01-26 00:00:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-31 09:06:36 +03:00
checksum = "4ae5588f6b3c3cb05239e90bd110f257254aecd01e4635400391aeae07497845"
ssh: use a single window for authenticating a session This makes it so that we preserve context while showing the connection status and authentication prompts.
2020-01-26 00:00:16 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"cfg-if 1.0.0",
"crossbeam-channel",
"crossbeam-deque",
"crossbeam-epoch",
ssh: use a single window for authenticating a session This makes it so that we preserve context while showing the connection status and authentication prompts.
2020-01-26 00:00:16 +03:00
"crossbeam-queue",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "crossbeam-channel"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.5.4"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "5aaa7bd5fb665c6864b5f963dd9097905c54125909c7aa94c9e18507cdbe6c53"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
"cfg-if 1.0.0",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "crossbeam-deque"
cargo update
2021-08-02 04:40:25 +03:00
version = "0.8.1"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-02 04:40:25 +03:00
checksum = "6455c0ca19f0d2fbf751b908d5c55c1f5cbc65e03c4225427254b46890bdde1e"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
"cfg-if 1.0.0",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-epoch",
"crossbeam-utils",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
]
[[package]]
name = "crossbeam-epoch"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.9.8"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "1145cf131a2c6ba0615079ab6a638f7e1973ac9c2634fcbeaaad6114246efe8c"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
deps: cargo update
2022-03-21 17:47:57 +03:00
"autocfg",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"lazy_static",
window+gui: enable dual source blending This replaces the slightly gnarly subpixel enabled blending in the shader with Dual Source Blending, which is a technique where the fragment shader can specify both the primary color (RGBA) as well as an additional per-channel mask that can be used to alpha blend with the destination. This enables artifact-free alpha blending when used together with a transparent window background. refs: https://github.com/wez/wezterm/issues/932
2021-08-10 08:27:44 +03:00
"memoffset",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"scopeguard",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "crossbeam-queue"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.3.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "1f25d8400f4a7a5778f0e4e52384a48cbd9b5c495d110786187fc750075277a2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"cfg-if 1.0.0",
"crossbeam-utils",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "crossbeam-utils"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.8.8"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "0bf124c720b7686e3c2663cf54062ab0f68a88af2fb6a030e87e30bf721fcb38"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
"cfg-if 1.0.0",
"lazy_static",
]
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
[[package]]
name = "csscolorparser"
deps: colorgrad -> 0.5
2021-09-06 09:27:01 +03:00
version = "0.5.0"
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: colorgrad -> 0.5
2021-09-06 09:27:01 +03:00
checksum = "b2fb3bd93ef32553e3d5b9f8020028f41ac64ff8a230033d5d548b8222d21fbe"
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
dependencies = [
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
"phf 0.8.0",
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ctor"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.1.22"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "f877be4f7c9f246b183111634f75baa039715e3f46ce860677d3b19a69fb229c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2021-11-29 05:09:45 +03:00
[[package]]
name = "cty"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b365fabc795046672053e29c954733ec3b05e4be654ab130fe8f1f94d7051f35"
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
[[package]]
name = "deflate"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
version = "1.0.0"
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
checksum = "c86f7e25f518f4b81808a2cf1c50996a61f5c2eb394b2393bd87f2a4780a432f"
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
dependencies = [
"adler32",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "derivative"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fcc3dd5e9e9c0b295d6e1e4d811fb6f157d5ffd784b8d202fc62eac8035a770b"
dependencies = [
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "diff"
version = "0.1.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0e25ea47919b1560c4e3b7fe0aaab9becf5b84a10325ddf7db0f0ba5e1026499"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "difflib"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6184e33543162437515c2e2b48714794e37845ec9851711914eec9d308f6ebe8"
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "digest"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f3d0c8c8752312f9713efd397ff63acb9f85585afbf179282e720e7704954dd5"
dependencies = [
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
"generic-array 0.12.4",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "digest"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3dd60d1080a57a05ab032377049e0591415d2b31afd7028356dbf3cc6dcb066"
dependencies = [
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
"generic-array 0.14.5",
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "dirs"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "13aea89a5c93364a98e9b37b2fa237effbb694d5cfe01c5b70941f7eb087d5e3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"dirs-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
[[package]]
name = "dirs-next"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b98cf8ebf19c3d1b223e151f99a4f9f0690dca41414773390fc824184ac833e1"
dependencies = [
"cfg-if 1.0.0",
"dirs-sys-next",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "dirs-sys"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.3.7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "1b1d1d91c932ef41c0f2663aa8b0ca0342d444d842c06914aa0a7e352d0bada6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2021-04-26 18:34:45 +03:00
"redox_users",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
[[package]]
name = "dirs-sys-next"
cargo update
2021-01-11 19:43:32 +03:00
version = "0.1.2"
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-11 19:43:32 +03:00
checksum = "4ebda144c4fe02d1f7ea1a7d9641b6fc6b580adcfa024ae48797ecdeb6825b4d"
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
dependencies = [
"libc",
cargo update
2021-04-26 18:34:45 +03:00
"redox_users",
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
"winapi 0.3.9",
]
cargo update
2021-03-01 20:02:05 +03:00
[[package]]
name = "dlib"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac1b7517328c04c2aa68422fc60a41b92208182142ed04a25879c26c8f878794"
dependencies = [
cargo update
2022-01-17 04:46:30 +03:00
"libloading 0.7.3",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
refine skip_close_confirmation_for_processes_named to look at proc tree That means that we won't be fooled by a shell with a backgrounded editor. refs: https://github.com/wez/wezterm/issues/562
2021-03-23 07:34:10 +03:00
[[package]]
name = "doc-comment"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fea41bba32d969b513997752735605054bc0dfa92b4c56bf1189f2e174be7a10"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "downcast-rs"
cargo update
2020-06-30 03:52:14 +03:00
version = "1.2.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "9ea835d29036a4087793836fa931b08837ad5e957da9e23886b29586fb9b6650"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "dwrote"
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
version = "0.11.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
checksum = "439a1c2ba5611ad3ed731280541d36d2e9c4ac5e7fb818a27b604bdc5a6aa65b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
"serde",
"serde_derive",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
"wio",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
[[package]]
name = "easy-parallel"
cargo update
2022-01-03 05:48:38 +03:00
version = "3.2.0"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-03 05:48:38 +03:00
checksum = "6907e25393cdcc1f4f3f513d9aac1e840eb1cc341a0fccb01171f7d14d10b946"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "either"
cargo update
2020-10-02 17:16:20 +03:00
version = "1.6.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-10-02 17:16:20 +03:00
checksum = "e78d4f1cc4ae33bbfc157ed5d5a5ef3bc29227303d595861deb238fcec4e9457"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "embed-resource"
cargo update
2022-04-04 04:26:59 +03:00
version = "1.7.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "ecc24ff8d764818e9ab17963b0593c535f077a513f565e75e4352d758bc4d8c0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-02-01 18:54:01 +03:00
"cc",
cargo update
2022-03-09 17:31:53 +03:00
"rustc_version 0.4.0",
"toml",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"vswhom",
pty: pre-fill base env from registry env settings on Windows I think I'd like to make a config option for this, but for the moment, this first pass unconditionally updates the base environment with data from the registry. refs: https://github.com/wez/wezterm/issues/1848
2022-04-19 19:56:23 +03:00
"winreg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
fonts: improve font name decoding freetype can't handle a wide range of encodings for font names and can return strings like `?????` when the family name is only present in the font as a non-unicode encoding, such as Chinese. This commit improves our handling of the font name table and prefers to use results from processing that over the results returned for eg: font family directly from the freetype API. refs: https://github.com/wez/wezterm/issues/1761
2022-03-26 09:27:27 +03:00
[[package]]
name = "encoding_rs"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.8.31"
fonts: improve font name decoding freetype can't handle a wide range of encodings for font names and can return strings like `?????` when the family name is only present in the font as a non-unicode encoding, such as Chinese. This commit improves our handling of the font name table and prefers to use results from processing that over the results returned for eg: font family directly from the freetype API. refs: https://github.com/wez/wezterm/issues/1761
2022-03-26 09:27:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "9852635589dc9f9ea1b6fe9f05b50ef208c85c834a562f0c6abb1c475736ec2b"
fonts: improve font name decoding freetype can't handle a wide range of encodings for font names and can return strings like `?????` when the family name is only present in the font as a non-unicode encoding, such as Chinese. This commit improves our handling of the font name table and prefers to use results from processing that over the results returned for eg: font family directly from the freetype API. refs: https://github.com/wez/wezterm/issues/1761
2022-03-26 09:27:27 +03:00
dependencies = [
"cfg-if 1.0.0",
]
Allow matching font weight and font width in `wezterm.font` refs: https://github.com/wez/wezterm/issues/655
2021-04-09 01:41:07 +03:00
[[package]]
name = "enum-display-derive"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f16ef37b2a9b242295d61a154ee91ae884afff6b8b933b486b12481cc58310ca"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "enumflags2"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.7.5"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "e75d4cd21b95383444831539909fbb14b9dc3fdceb2a6f5d36577329a1f55ccb"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
dependencies = [
"enumflags2_derive",
"serde",
]
[[package]]
name = "enumflags2_derive"
deps: cargo update
2022-03-28 05:47:26 +03:00
version = "0.7.4"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-28 05:47:26 +03:00
checksum = "f58dc3c5e468259f19f2d46304a6b28f1c3d034442e14b322d2b850e36f6d5ae"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
dependencies = [
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
[[package]]
name = "env-bootstrap"
version = "0.1.0"
dependencies = [
capture panic backtrace to log file
2022-04-28 00:47:28 +03:00
"backtrace",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
"battery",
add debug overlay Adds a `ShowDebugOverlay` key assignment that will create a tab overlay that shows a limited number of recently logged events. refs: https://github.com/wez/wezterm/issues/641
2021-05-03 06:50:01 +03:00
"chrono",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
"cocoa",
"config",
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
"dirs-next",
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
"filesystem",
add debug overlay Adds a `ShowDebugOverlay` key assignment that will create a tab overlay that shows a limited number of recently logged events. refs: https://github.com/wez/wezterm/issues/641
2021-05-03 06:50:01 +03:00
"lazy_static",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
"libc",
use $WEZTERM_LOG to configure log levels ad-hoc 80214319aec9d7b72217db3d7a6f8e8575081eac broke the use of RUST_LOG to turn up trace logging. This commit refactors logger initialization into the env-bootstrap crate so that it is centralized, and adopts the use of `WEZTERM_LOG` to override the default logging filters, rather than `RUST_LOG`.
2020-12-23 23:14:01 +03:00
"log",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
"logging",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
"objc",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
"spawn-funcs",
"ssh-funcs",
logging: use our own custom logger I wanted to use the Target::Pipe feature of env_logger so that we could log to a log file as well as stderr, but it just doesn't work (https://github.com/env-logger-rs/env_logger/issues/208). Since we were already composing over the top of the logger in order to capture data for our ringlog, this commit embraces that and makes our logger responsible for both stderr and log file printing. Thankfully, we can use the filter parsing code from env_logger to avoid having to get too crazy with this. Logs are stored in the runtime directory and look something like: /run/user/1000/wezterm/wezterm-gui-log-596324.txt Logs are collected on all platforms. There isn't currently a thing to clean up logs.
2022-04-07 19:51:00 +03:00
"termwiz",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
"termwiz-funcs",
windows: workaround Rust 1.56 bug 88576 Skip initializing pretty logger when running in the windows subsystem. refs: https://github.com/wez/wezterm/issues/1245 refs: https://github.com/rust-lang/rust/issues/88576
2021-10-24 21:44:55 +03:00
"winapi 0.3.9",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
]
Enable timestamps in the logger
2020-02-14 20:46:19 +03:00
[[package]]
name = "env_logger"
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
version = "0.9.0"
Enable timestamps in the logger
2020-02-14 20:46:19 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
checksum = "0b2cf0344971ee6c64c31be0d530793fba457d322dfec2810c453d0ef228f9c3"
Enable timestamps in the logger
2020-02-14 20:46:19 +03:00
dependencies = [
"atty",
"humantime",
"log",
"regex",
"termcolor",
]
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
[[package]]
name = "euclid"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.22.7"
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "b52c2ef4a78da0ba68fbe1fd920627411096d2ac478f7f4c9f3a54ba6705bade"
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
dependencies = [
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "event-listener"
cargo update
2022-01-24 08:19:09 +03:00
version = "2.5.2"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-24 08:19:09 +03:00
checksum = "77f3309417938f28bf8228fcff79a4a37103981e3e186d2ccd19c74b38f4eb71"
cargo update
2020-09-09 19:31:37 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "evmap"
version = "6.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "6fdb60074c9b82c91f8702fa5351b85d22b668dae7f73bf06b44a09bc372380f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hashbrown 0.5.0",
cargo update
2021-01-11 19:43:32 +03:00
"smallvec 0.6.14",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "exr"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "1.4.2"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "14cc0e06fb5f67e5d6beadf3a382fec9baca1aa751c6d5368fdeee7e5932c215"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
dependencies = [
"bit_field",
cargo update
2022-02-14 06:31:40 +03:00
"deflate",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"flume",
"half",
"inflate",
"lebe",
"smallvec 1.8.0",
"threadpool",
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "fake-simd"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e88a8acf291dafb59c2d96e8f59828f3838bb1a70398823ade51a84de6a6deed"
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "fastrand"
cargo update
2022-01-24 08:19:09 +03:00
version = "1.7.0"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-24 08:19:09 +03:00
checksum = "c3fcf0cee53519c866c09b5de1f6c56ff9d647101f81c1964fa632e148896cdf"
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
dependencies = [
"instant",
]
cargo update
2020-06-30 03:52:14 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "filedescriptor"
filedescriptor: bump version for package publish
2022-01-22 03:07:26 +03:00
version = "0.8.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
filedescriptor: remove anyhow from public interface Use thiserror instead
2021-05-24 00:24:01 +03:00
"thiserror",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
[[package]]
name = "filenamegen"
cargo update
2020-04-15 18:23:43 +03:00
version = "0.2.4"
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-04-15 18:23:43 +03:00
checksum = "0b2da6e8ef70499318bc50abd003fd66dbf6d8a46c23f9e90158f388a788976a"
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
dependencies = [
"anyhow",
"bstr 0.1.4",
"regex",
"walkdir",
]
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
[[package]]
name = "filesystem"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"filenamegen",
"luahelper",
"smol",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "filetime"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "0.2.16"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "c0408e2626025178a6a7f7ffc05a25bc47103229f19c113755de7bf63816290c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2022-04-04 04:26:59 +03:00
"redox_syscall 0.2.13",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "flate2"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "1.0.23"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "b39522e96686d38f4bc984b9198e3a0613264abaebaff2c5c918bfa6b6da09af"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"crc32fast",
"libc",
deps: cargo update
2022-04-19 06:51:19 +03:00
"miniz_oxide 0.5.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "float-cmp"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "98de4bbd547a563b716d8dfa9aad1cb19bfab00f4fa09a6a4ed21dbcf44ce9c4"
dependencies = [
"num-traits",
]
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
[[package]]
name = "flume"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.10.12"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "843c03199d0c0ca54bc1ea90ac0d507274c28abcc4f691ae8b4eaa375087c76a"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
dependencies = [
"futures-core",
"futures-sink",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"nanorand",
cargo update
2021-01-06 11:28:11 +03:00
"pin-project",
deps: cargo update
2022-04-19 06:51:19 +03:00
"spin 0.9.3",
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "fnv"
cargo update
2020-05-26 08:25:39 +03:00
version = "1.0.7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-26 08:25:39 +03:00
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "fontconfig"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"pkg-config",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "foreign-types"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types-shared",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "form_urlencoded"
cargo update
2021-02-22 11:09:01 +03:00
version = "1.0.1"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-22 11:09:01 +03:00
checksum = "5fc25a87fa4fd2094bffb06925852034d90a17f0d1e05197d4956d3555752191"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
"matches",
"percent-encoding",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "freetype"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fsevent"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "5ab7d1bd1bd33cc98b0889831b72da23c0aa4df9cec7e0702f46ecea04b35db6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fsevent-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fsevent-sys"
version = "2.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f41b048a94555da0f42f1d632e2e19510084fb8e303b0daa2816e733fb3644a0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fuchsia-cprng"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "fuchsia-zircon"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fuchsia-zircon-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fuchsia-zircon-sys"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "futures"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "f73fe65f54d1e12b726f517d3e2135ca3125a437b6d998caf1962961f7172d9e"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"futures-channel",
"futures-core",
"futures-executor",
"futures-io",
"futures-sink",
"futures-task",
"futures-util",
]
[[package]]
name = "futures-channel"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "c3083ce4b914124575708913bca19bfe887522d6e2e6d0952943f5eac4a74010"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"futures-core",
"futures-sink",
]
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "futures-core"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "0c09fd04b7e4073ac7156a9539b57a484a8ea920f79c7c675d05d289ab6110d3"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "futures-executor"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "9420b90cfa29e327d0429f19be13e7ddb68fa1cccb09d65e5706b8c7a749b8a6"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"futures-core",
"futures-task",
"futures-util",
]
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "futures-io"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "fc4045962a5a5e935ee2fdedaa4e08284547402885ab326734432bed5d12966b"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "futures-lite"
cargo update
2021-06-07 18:32:05 +03:00
version = "1.12.0"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-07 18:32:05 +03:00
checksum = "7694489acd39452c77daa48516b894c153f192c3578d5a839b62c58099fcbf48"
cargo update
2020-10-02 17:16:20 +03:00
dependencies = [
"fastrand",
"futures-core",
"futures-io",
"memchr",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"parking",
cargo update
2020-12-20 03:44:27 +03:00
"pin-project-lite",
cargo update
2020-10-02 17:16:20 +03:00
"waker-fn",
]
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "futures-macro"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "33c1e13800337f4d4d7a316bf45a567dbcb6ffe087f16424852d97e97a91f512"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
]
[[package]]
name = "futures-sink"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "21163e139fa306126e6eedaf49ecdb4588f939600f0b1e770f4205ee4b7fa868"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "futures-task"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "57c66a976bf5909d801bbef33416c41372779507e7a6b3a5e25e4749c58f776a"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
cargo update
2022-05-16 05:44:27 +03:00
[[package]]
name = "futures-timer"
version = "3.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e64b03909df88034c26dc1547e8970b91f98bdb65165d6a4e9110d94263dbb2c"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "futures-util"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.3.21"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "d8b7abd5d659d9b90c8cba917f6ec750a74e2dc23902ef9cd4cc8c8b22e6036a"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"futures-channel",
"futures-core",
"futures-io",
"futures-macro",
"futures-sink",
"futures-task",
"memchr",
cargo update
2021-01-11 19:43:32 +03:00
"pin-project-lite",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
"pin-utils",
"slab",
]
launcher now has fuzzy matching Just start typing text to build up the fuzzy matching term. The list of items updates to match the results. refs: #664 refs: #1485
2022-01-04 18:45:15 +03:00
[[package]]
name = "fuzzy-matcher"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "54614a3312934d066701a80f20f15fa3b56d67ac7722b39eea5b4c9dd1d66c94"
dependencies = [
"thread_local",
]
Add wezterm-bidi crate In order to support RTL/BIDI, wezterm needs a bidi implementation. I don't think a well-conforming rust implementation exists today; what I found were implementations that didn't pass 100% of the conformance tests. So I decided to port "bidiref", the reference implementation of the UBA described in http://unicode.org/reports/tr9/ to Rust. This implementation focuses on conformance: no special measures have been taken to optimize it so far, with my focus having been to ensure that all of the approx 780,000 test cases in the unicode data for unicode 14 pass. Having the tests passing 100% allows for making performance improvements with confidence in the future. The API isn't completely designed/fully baked. Until I get to hooking it up to wezterm's shaper, I'm not 100% sure exactly what I'll need. There's a good discussion on API in https://github.com/open-i18n/rust-unic/issues/273 that suggests omitting "legacy" operations such as reordering. I suspect that wezterm may actually need that function to support monospace text layout in some terminal scenarios, but regardless: reordering is part of the conformance test suite so it remains a part of the API. That said: the API does model the major operations as separate phases, so you should be able to pay for just what you use: * Resolving the embedding levels from a paragraph * Returning paragraph runs of those levels (and their directions) * Returning the whitespace-level-reset runs for a line-slice within the paragraph * Returning the reordered indices + levels for a line-slice within the paragraph. refs: https://github.com/wez/wezterm/issues/784 refs: https://github.com/kas-gui/kas-text/issues/20
2022-01-21 18:42:44 +03:00
[[package]]
name = "generate-bidi"
version = "0.1.0"
dependencies = [
"anyhow",
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "generic-array"
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
version = "0.12.4"
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
checksum = "ffdf9f34f1447443d37393cc6c2b8313aebddcd96906caf34e54c68d8e57d7bd"
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
dependencies = [
"typenum",
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "generic-array"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.14.5"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "fd48d33ec7f05fbfa152300fdad764757cbded343c1aa1cff2fbaf4134851803"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
dependencies = [
"typenum",
"version_check",
]
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
[[package]]
name = "getopts"
version = "0.2.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14dbbfd5c71d70241ecf9e6f13737f7b5ce823821063188d7e46c41d371eebd5"
dependencies = [
"unicode-width",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "getrandom"
cargo update
2021-01-06 11:28:11 +03:00
version = "0.1.16"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-06 11:28:11 +03:00
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"cfg-if 1.0.0",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"libc",
"wasi 0.9.0+wasi-snapshot-preview1",
]
[[package]]
name = "getrandom"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.2.6"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "9be70c98951c83b8d2f8f60d7065fa6d5146873094452a1008da8c2f1e4205ad"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"cfg-if 1.0.0",
"js-sys",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2021-02-01 18:54:01 +03:00
"wasi 0.10.2+wasi-snapshot-preview1",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"wasm-bindgen",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "gif"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
version = "0.11.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
checksum = "c3a7187e78088aead22ceedeee99779455b23fc231fe13ec443f99bb71694e5b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"color_quant",
cargo update
2020-10-02 17:16:20 +03:00
"weezl",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2020-05-26 08:25:39 +03:00
[[package]]
name = "gimli"
cargo update
2021-11-03 16:41:06 +03:00
version = "0.26.1"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-11-03 16:41:06 +03:00
checksum = "78cc372d058dcf6d5ecd98510e7fbc9e5aec4d21de70f65fea8fecebcd881bd4"
cargo update
2020-05-26 08:25:39 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "gl_generator"
version = "0.14.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "1a95dfc23a2b4a9a2f5ab41d194f8bfda3cabec42af4e39f08c339eb2a0c124d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"khronos_api",
"log",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"xml-rs",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "glium"
deps: unpin glium from git, use latest release We were pinned on the revision where I had added dual source blending, because I wanted that feature ahead of the crate being published. Since then a couple of releases have been made so we can unpin. On Windows 11, we had a report of glium complaining about the opengl version. I can't find that error message string in the current version of the code so it's possible that that situation has been resolved. refs: https://github.com/wez/wezterm/issues/1813
2022-04-04 16:49:09 +03:00
version = "0.31.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ab4f09b43d8ee427a700cb9ed3b20e0e858d62a509edded1a98ca5707d68e19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"backtrace",
"fnv",
window: glium and gl_generator version bump
2020-06-15 07:24:54 +03:00
"gl_generator",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
window+gui: enable dual source blending This replaces the slightly gnarly subpixel enabled blending in the shader with Dual Source Blending, which is a technique where the fragment shader can specify both the primary color (RGBA) as well as an additional per-channel mask that can be used to alpha blend with the destination. This enables artifact-free alpha blending when used together with a transparent window background. refs: https://github.com/wez/wezterm/issues/932
2021-08-10 08:27:44 +03:00
"memoffset",
cargo update
2022-01-17 04:46:30 +03:00
"smallvec 1.8.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"takeable-option",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "globset"
version = "0.4.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10463d9ff00a2a068db14231982f5132edebad0d7660cd956a1c30292dbcbfbd"
dependencies = [
"aho-corasick",
ssh: unwrap -> error handling The port number is guaranteed to be set in the config parser, just like for the host and user, so the unwrap is "OK", but it's less brittle to handle the error consistent with the others here.
2021-10-11 01:03:21 +03:00
"bstr 0.2.17",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"fnv",
"log",
"regex",
]
[[package]]
name = "globwalk"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93e3af942408868f6934a7b85134a3230832b9977cf66125df2f9edcfce4ddcc"
dependencies = [
"bitflags",
"ignore",
"walkdir",
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "gloo-timers"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "0.2.4"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "5fb7d06c1c8cc2a29bee7ec961009a0b2caa0793ee4900c2ffb348734ba1c8f9"
cargo update
2020-10-02 17:16:20 +03:00
dependencies = [
"futures-channel",
"futures-core",
"js-sys",
"wasm-bindgen",
]
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
[[package]]
name = "guillotiere"
cargo update
2021-08-16 04:17:02 +03:00
version = "0.6.2"
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-16 04:17:02 +03:00
checksum = "b62d5865c036cb1393e23c50693df631d3f5d7bcca4c04fe4cc0fd592e74a782"
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
dependencies = [
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
"svg_fmt",
]
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "half"
version = "1.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eabb4a44450da02c90444cf74558da904edde8fb4e9035a9a6a4e15445af0bd7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "harfbuzz"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
wezterm-font: remove font-kit dep This wasn't used by anything and the version was getting pretty stale. Upgrading is awkward because newer versions pull in an incompatible freetype library version.
2020-10-25 08:01:00 +03:00
"freetype",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "hashbrown"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "e1de41fb8dba9714efd92241565cdff73f78508c95697dd56787d3cba27e2353"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2021-07-07 23:27:08 +03:00
[[package]]
name = "hashbrown"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ab5ef0d4909ef3724cc8cce6ccc8572c5c817592e9285f5464f8e86f8bd3726e"
cargo update
2021-08-02 04:40:25 +03:00
dependencies = [
remove wgpu from window test deps We don't use this and all it really does it make `cargo test` take longer
2021-11-23 15:39:07 +03:00
"ahash",
cargo update
2021-08-02 04:40:25 +03:00
]
cargo update
2021-07-07 23:27:08 +03:00
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
[[package]]
name = "hdrhistogram"
cargo update
2022-02-14 06:31:40 +03:00
version = "7.5.0"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-14 06:31:40 +03:00
checksum = "31672b7011be2c4f7456c4ddbcb40e7e9a4a9fad8efe49a6ebaf5f307d0109c0"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"byteorder",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-channel",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"flate2",
deps: cargo update
2022-03-21 17:47:57 +03:00
"nom 7.1.1",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "heck"
cargo update
2021-06-07 18:32:05 +03:00
version = "0.3.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-07 18:32:05 +03:00
checksum = "6d621efb26863f0e9924c6ac577e8275e5e6b77455db64ffa6c65c904e9e132c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-segmentation",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "hermit-abi"
deps: cargo update
2021-06-27 05:49:10 +03:00
version = "0.1.19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2021-06-27 05:49:10 +03:00
checksum = "62b467343b94ba476dcb2500d242dadbb39557df889310ac77c5d99100aaac33"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
termwiz: recognize the XTGETTCAP DCS sequence Parse and respond to this sequence docs can be found https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h4-Device-Control-functions:DCS-plus-q-Pt-ST.F95 refs: https://github.com/wez/wezterm/issues/954
2021-07-25 07:02:54 +03:00
[[package]]
name = "hex"
version = "0.4.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f24254aa9a54b5c858eaee2f5bccdb46aaf0e486a595ed5fd8f86ba55232a70"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "hostname"
cargo update
2020-03-14 19:39:38 +03:00
version = "0.3.1"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-03-14 19:39:38 +03:00
checksum = "3c731c3e10504cc8ed35cfe2f1db4c9274c3d35fa486e3b31df46f068ef3e867"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"libc",
"match_cfg",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
]
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "http_req"
cargo update
2021-07-12 06:08:24 +03:00
version = "0.8.1"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-07-12 06:08:24 +03:00
checksum = "9e6cd45a270dff33553602fd84beb02c89460ee32db638715f10d9060389fd6a"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
dependencies = [
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
"native-tls",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
"unicase",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "humantime"
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
version = "2.1.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
checksum = "9a3a5bfb195931eeb336b2a7b4d761daec841b97f947d34394601737a7bba5e4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "idna"
cargo update
2021-04-19 19:23:33 +03:00
version = "0.2.3"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "418a0a6fab821475f634efe3ccc45c013f742efe03d853e8d3355d5cb850ecf8"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"matches",
"unicode-bidi",
"unicode-normalization",
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "ignore"
version = "0.4.18"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "713f1b139373f96a2e0ce3ac931cd01ee973c3c5dd7c40c0c2efe96ad2b6751d"
dependencies = [
"crossbeam-utils",
"globset",
"lazy_static",
"log",
"memchr",
"regex",
"same-file",
"thread_local",
"walkdir",
"winapi-util",
]
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "image"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.24.2"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "28edd9d7bc256be2502e325ac0628bde30b7001b9b52e0abe31a1a9dc2701212"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
dependencies = [
"bytemuck",
"byteorder",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"color_quant",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"exr",
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
"gif",
deps: cargo update
2022-04-19 06:51:19 +03:00
"jpeg-decoder",
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
"num-iter",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"num-rational 0.4.0",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"png",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"scoped_threadpool",
cargo update
2020-06-13 20:21:49 +03:00
"tiff",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "inflate"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1cdb29978cc5797bd8dcc8e5bf7de604891df2a8dc576973d71a281e916db2ff"
dependencies = [
"adler32",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "inotify"
cargo update
2020-06-06 20:08:02 +03:00
version = "0.7.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-06 20:08:02 +03:00
checksum = "4816c66d2c8ae673df83366c18341538f234a26d65a9ecea5c348b453ac1d02f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"inotify-sys",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "inotify-sys"
cargo update
2021-01-18 10:38:11 +03:00
version = "0.1.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-18 10:38:11 +03:00
checksum = "e05c02b5e89bff3b946cedeca278abc628fe811e604f027c45a8aa3cf793d0eb"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
[[package]]
name = "instant"
cargo update
2021-10-25 05:20:45 +03:00
version = "0.1.12"
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-10-25 05:20:45 +03:00
checksum = "7a5bbe824c507c5da5956355e86a746d82e0e1464f65d862cc5e71da70e94b2c"
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ioctl-rs"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f7970510895cee30b3e9128319f2cefd4bde883a39f38baa279567ba3a7eb97d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "iovec"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "b2b3ea6ff95e175473f8ffe6a7eb7c00d054240321b84c57051175fe3c1e075e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "itertools"
cargo update
2021-12-11 01:26:10 +03:00
version = "0.10.3"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-12-11 01:26:10 +03:00
checksum = "a9a9d19fa1e79b6215ff29b9d6880b706147f16e9b1dbb1e4e5947b5b02bc5e3"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
dependencies = [
"either",
]
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "itoa"
cargo update
2022-05-16 05:44:27 +03:00
version = "1.0.2"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "112c678d4050afce233f4f2852bb2eb519230b3cf12f33585275537d7e41578d"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "jobserver"
cargo update
2021-08-23 17:33:44 +03:00
version = "0.1.24"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-23 17:33:44 +03:00
checksum = "af25a77299a7f711a01975c35a6a424eb6862092cc2d6c72c4ed6cbc56dfc1fa"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "jpeg-decoder"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "0.2.6"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "9478aa10f73e7528198d75109c8be5cd7d15fb530238040148d5f9a22d4c5b3b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rayon",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "js-sys"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.3.57"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "671a26f820db17c2a2750743f1dd03bafd15b98c9f30c7c2628c024c05d73397"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"wasm-bindgen",
]
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "k9"
cargo update
2021-08-25 20:00:33 +03:00
version = "0.11.1"
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-25 20:00:33 +03:00
checksum = "611dc69892d72bfa0848a2e6bf55ef2e3fdc7283381c97713a75043326decc5d"
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
dependencies = [
"anyhow",
"colored",
"diff",
"lazy_static",
"libc",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
"regex",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"syn",
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
"term_size",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi 0.2.8",
"winapi-build",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "khronos_api"
version = "3.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "e2db585e1d738fc771bf08a151420d3ed193d9d895a36df7f6f8a9456b911ddc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "kv-log-macro"
cargo update
2020-07-09 09:54:56 +03:00
version = "1.0.7"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-07-09 09:54:56 +03:00
checksum = "0de8b303297635ad57c9f5059fd9cee7a47f8e8daa09df0fcd07dd39fb22977f"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
dependencies = [
"log",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "lazycell"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.3.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "830d08ce1d1d941e6b30645f1a0eb5643013d835ce3779a5fc208261dbe10f55"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "leb128"
cargo update
2021-10-11 05:15:00 +03:00
version = "0.2.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-10-11 05:15:00 +03:00
checksum = "884e2677b40cc8c339eaefcb701c32ef1fd2493d71118dc0ca4b6a736c93bd67"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "lebe"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7efd1d698db0759e6ef11a7cd44407407399a910c774dd804c64c032da7826ff"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "libc"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.2.125"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "5916d2ae698f6de9bfb891ad7a8d65c09d232dc58cc4ac433c7da3b2fd84bc2b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2020-06-06 20:08:02 +03:00
[[package]]
name = "libloading"
cargo update
2021-01-18 10:38:11 +03:00
version = "0.6.7"
cargo update
2020-06-06 20:08:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-18 10:38:11 +03:00
checksum = "351a32417a12d5f7e82c368a66781e307834dae04c6ce0cd4456d52989229883"
cargo update
2020-06-06 20:08:02 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
cargo update
2020-06-06 20:08:02 +03:00
]
cargo update
2021-03-01 20:02:05 +03:00
[[package]]
name = "libloading"
cargo update
2022-01-17 04:46:30 +03:00
version = "0.7.3"
cargo update
2021-03-01 20:02:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "efbc0f03f9a775e9f6aed295c6a1ba2253c5757a9e03d55c6caa46a681abcddd"
cargo update
2021-03-01 20:02:05 +03:00
dependencies = [
"cfg-if 1.0.0",
"winapi 0.3.9",
]
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
[[package]]
name = "libssh-rs"
ssh: prep for crate release
2022-01-31 04:29:59 +03:00
version = "0.1.4"
source = "git+https://github.com/wez/libssh-rs.git#d36e5648274063c187968fd5ce0b1a7aa350a025"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
dependencies = [
"bitflags",
"libssh-rs-sys",
"thiserror",
]
[[package]]
name = "libssh-rs-sys"
ssh: prep for crate release
2022-01-31 04:29:59 +03:00
version = "0.1.3"
source = "git+https://github.com/wez/libssh-rs.git#d36e5648274063c187968fd5ce0b1a7aa350a025"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
dependencies = [
"cc",
"libz-sys",
"openssl-sys",
"pkg-config",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "libssh2-sys"
ssh: my openssl+windows ssh2 patch was published upstream So remove my local patch
2021-10-10 17:29:54 +03:00
version = "0.2.23"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b094a36eb4b8b8c8a7b4b8ae43b2944502be3e59cd87687595cf6b0a71b3f4ca"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
"libz-sys",
"openssl-sys",
"pkg-config",
"vcpkg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "libz-sys"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.1.6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "92e7e15d7610cce1d9752e137625f14e61a28cd45929b6e12e47b50fe154ee2e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
"pkg-config",
"vcpkg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "line_drawing"
cargo update
2021-06-07 18:32:05 +03:00
version = "0.8.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-07 18:32:05 +03:00
checksum = "15cb10f27ad3eac84fdb70f0ea6dfe3bc33f7d6f3aa575f32d1ced3a342049a1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "lock_api"
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
version = "0.3.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
checksum = "c4da24a77a3d8a6d4862d95f72e6fdb9c09a643ecdb402d754004a557f2bec75"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"scopeguard",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
[[package]]
name = "lock_api"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.4.7"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "327fa5b6a6940e4699ec49a9beae1ea4845c6bab9314e4f84ac68742139d8c53"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
dependencies = [
cargo update
2022-04-04 04:26:59 +03:00
"autocfg",
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
"scopeguard",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "log"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "0.4.17"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "abb12e687cfb44aa40f41fc3978ef76448f9b6038cad6aef4259d3c095a2382e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-02-01 18:54:01 +03:00
"cfg-if 1.0.0",
"value-bag",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
[[package]]
name = "logging"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"log",
"luahelper",
]
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
[[package]]
name = "lru"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.7.5"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "32613e41de4c47ab04970c348ca7ae7382cf116625755af070b008a15516a889"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
dependencies = [
cargo update
2021-08-02 04:40:25 +03:00
"hashbrown 0.11.2",
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
]
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
[[package]]
name = "lua-src"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "544.0.1"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "708ba3c844d5e9d38def4a09dd871c17c370f519b3c4b7261fbabe4a613a814c"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
dependencies = [
"cc",
]
move lua helpers into own crate
2020-10-02 20:28:58 +03:00
[[package]]
name = "luahelper"
version = "0.1.0"
dependencies = [
deps: cargo update
2021-10-04 08:10:01 +03:00
"bstr 0.2.17",
move lua helpers into own crate
2020-10-02 20:28:58 +03:00
"log",
"mlua",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
move lua helpers into own crate
2020-10-02 20:28:58 +03:00
]
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
[[package]]
name = "luajit-src"
cargo update
2022-04-11 04:32:03 +03:00
version = "210.3.4+resty073ac54"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "640b09e99575a442b4da0ef406a78188a1a4313bb9ead7b5b20ec12cc480130f"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
dependencies = [
"cc",
]
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
[[package]]
name = "mach"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b823e83b2affd8f40a9ee8c29dbc56404c1e34cd2710921f2801e2cf29527afa"
dependencies = [
"libc",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "malloc_buf"
version = "0.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "62bb907fe88d54d8d9ce32a3cceab4218ed2f6b7d35617cafe9adf84e43919cb"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "maplit"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3e2e65a1a2e43cfcb47a895c4c8b10d1f4a61097f9f254f183aee60cad9c651d"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "match_cfg"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ffbee8634e0d45d258acb448e7eaab3fce7a0a467395d4d9f228e3c1f01fb2e4"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "matches"
cargo update
2021-08-16 04:17:02 +03:00
version = "0.1.9"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-16 04:17:02 +03:00
checksum = "a3e378b66a060d48947b590737b30a1be76706c8dd7b8ba0f2fe3989c68a853f"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "maybe-uninit"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "60302e4db3a61da70c0cb7991976248362f30319e88850c487b9b95bbf059e00"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "memchr"
cargo update
2022-05-02 07:21:14 +03:00
version = "2.5.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "2dffe52ecf27772e601905b7522cb4ef790d2cc203488bbd0e2fe85fcb74566d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
name = "memmap2"
version = "0.2.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
checksum = "723e3ebdcdc5c023db1df315364573789f8857c11b631a2fdfad7c00f5c046b4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
fonts: add custom freetype stream impl The intent is to reveal more context on what's happening in https://github.com/wez/wezterm/issues/671 As a nice side benefit, this avoids the potential inability to open paths that are not utf8 or representable as c-strings on Windows. And on top of that: this enables memory mapped file IO as well, which wasn't enabled previously. This should help to reduce extraneous copies of the font in memory, have fewer open files and minimize the chances of racing with O_CLOEXEC.
2021-04-10 19:23:11 +03:00
[[package]]
name = "memmap2"
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
version = "0.3.1"
fonts: add custom freetype stream impl The intent is to reveal more context on what's happening in https://github.com/wez/wezterm/issues/671 As a nice side benefit, this avoids the potential inability to open paths that are not utf8 or representable as c-strings on Windows. And on top of that: this enables memory mapped file IO as well, which wasn't enabled previously. This should help to reduce extraneous copies of the font in memory, have fewer open files and minimize the chances of racing with O_CLOEXEC.
2021-04-10 19:23:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
checksum = "00b6c2ebff6180198788f5db08d7ce3bc1d0b617176678831a7510825973e357"
fonts: add custom freetype stream impl The intent is to reveal more context on what's happening in https://github.com/wez/wezterm/issues/671 As a nice side benefit, this avoids the potential inability to open paths that are not utf8 or representable as c-strings on Windows. And on top of that: this enables memory mapped file IO as well, which wasn't enabled previously. This should help to reduce extraneous copies of the font in memory, have fewer open files and minimize the chances of racing with O_CLOEXEC.
2021-04-10 19:23:11 +03:00
dependencies = [
"libc",
]
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
[[package]]
name = "memmap2"
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
version = "0.5.3"
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
checksum = "057a3db23999c867821a7a59feb06a578fcb03685e983dff90daf9e7d24ac08f"
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
dependencies = [
"libc",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "memmem"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "a64a92489e2744ce060c349162be1c5f33c6969234104dbd99ddb5feb08b8c15"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "memoffset"
cargo update
2021-12-06 05:07:49 +03:00
version = "0.6.5"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-12-06 05:07:49 +03:00
checksum = "5aa361d4faea93603064a027415f07bd8e1d5c88c9fbf68bf56a285428fd79ce"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
]
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
[[package]]
name = "metrics"
deps: update
2021-12-20 18:15:56 +03:00
version = "0.17.1"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update
2021-12-20 18:15:56 +03:00
checksum = "55586aa936c35f34ba8aa5d97356d554311206e1ce1f9e68fe7b07288e5ad827"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
dependencies = [
remove wgpu from window test deps We don't use this and all it really does it make `cargo test` take longer
2021-11-23 15:39:07 +03:00
"ahash",
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
"metrics-macros",
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
]
[[package]]
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
name = "metrics-macros"
deps: update
2021-12-20 18:15:56 +03:00
version = "0.4.1"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update
2021-12-20 18:15:56 +03:00
checksum = "0daa0ab3a0ae956d0e2c1f42511422850e577d36a255357d1a7d08d45ee3a2f1"
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
dependencies = [
"lazy_static",
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
"regex",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"syn",
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
]
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
cargo update
2021-08-23 17:33:44 +03:00
[[package]]
name = "minimal-lexical"
cargo update
2021-11-08 17:57:40 +03:00
version = "0.2.1"
cargo update
2021-08-23 17:33:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-11-08 17:57:40 +03:00
checksum = "68354c5c6bd36d73ff3feceb05efa59b6acb7626617f4962be322a825e61f79a"
cargo update
2021-08-23 17:33:44 +03:00
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "miniz_oxide"
cargo update
2021-03-01 20:02:05 +03:00
version = "0.4.4"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-01 20:02:05 +03:00
checksum = "a92518e98c078586bc6c934028adcca4c92a53d6a958196de835170a01d84e4b"
cargo update
2020-06-30 03:52:14 +03:00
dependencies = [
"adler",
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update
2020-06-30 03:52:14 +03:00
]
cargo update
2022-02-14 06:31:40 +03:00
[[package]]
name = "miniz_oxide"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d2b29bd4bc3f33391105ebee3589c19197c4271e3e5a9ec9bfe8127eeff8f082"
dependencies = [
"adler",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "mio"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.6.23"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "4afd66f5b91bf2a3bc13fad0e21caedac168ca4c707504e75585648ae80e4cc4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fuchsia-zircon",
"fuchsia-zircon-sys",
"iovec",
"kernel32-sys",
"libc",
"log",
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
"miow",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"net2",
"slab",
"winapi 0.2.8",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
[[package]]
name = "mio"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "0.8.3"
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "713d550d9b44d89174e066b7a6217ae06234c10cb47819a88290d2b353c31799"
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
dependencies = [
"libc",
"log",
"wasi 0.11.0+wasi-snapshot-preview1",
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
"windows-sys",
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "mio-extras"
Update Cargo.lock
2019-12-30 00:43:59 +03:00
version = "2.0.6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "52403fe290012ce777c4626790c8951324a2b9e3316b3143779c72b029742f19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazycell",
"log",
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
"mio 0.6.23",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"slab",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "miow"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.2.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "ebd808424166322d4a38da87083bfddd3ac4c131334ed55856112eb06d46944d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"kernel32-sys",
"net2",
"winapi 0.2.8",
"ws2_32-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
[[package]]
name = "mlua"
Add cycle detection when converting lua values to dynamic
2022-05-18 07:53:36 +03:00
version = "0.8.0-beta.4"
restore pretty printing lua values in repl This time with more correctly working cycle detection
2022-05-18 08:51:33 +03:00
source = "git+https://github.com/khvzak/mlua?branch=master#bcf2cbea3798504471d88345327671bf2da7e8e1"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
dependencies = [
deps: cargo update
2021-10-04 08:10:01 +03:00
"bstr 0.2.17",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
"cc",
Upgrade mlua to 0.4, lua to 5.4
2020-10-07 04:34:29 +03:00
"futures-core",
"futures-task",
"futures-util",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
"lua-src",
"luajit-src",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
Add get_foreground_process_name, expose it and cwd in PaneInformation Add `get_foreground_process_name` to both Pane and the lua wrapper. Add `foreground_process_name` and `current_working_dir` fields to `PaneInformation`. In order for those to be dynamically fetched, switch the lua conversion for `PaneInformation` to be a UserData with field access methods. It's a little more verbose but allows us to lazily compute these two new fields. refs: https://github.com/wez/wezterm/discussions/1421 refs: https://github.com/wez/wezterm/issues/915 refs: https://github.com/wez/wezterm/issues/876
2021-12-24 04:44:12 +03:00
"once_cell",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
"pkg-config",
Add get_foreground_process_name, expose it and cwd in PaneInformation Add `get_foreground_process_name` to both Pane and the lua wrapper. Add `foreground_process_name` and `current_working_dir` fields to `PaneInformation`. In order for those to be dynamically fetched, switch the lua conversion for `PaneInformation` to be a UserData with field access methods. It's a little more verbose but allows us to lazily compute these two new fields. refs: https://github.com/wez/wezterm/discussions/1421 refs: https://github.com/wez/wezterm/issues/915 refs: https://github.com/wez/wezterm/issues/876
2021-12-24 04:44:12 +03:00
"rustc-hash",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
]
move mux to its own crate
2020-10-03 03:42:49 +03:00
[[package]]
name = "mux"
version = "0.1.0"
dependencies = [
"anyhow",
"async-trait",
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"bintree",
mux: track list of clients Define a way to compute a client ID and pass that through to the mux server when verifying version compatibility. Once associated, the session handler will keep some metadata updated in the mux. A new cli subcommand exposes the info: ``` ; ./target/debug/wezterm cli list-clients USER HOST PID CONNECTED IDLE WORKSPACE wez mba.localdomain 52979 30.009225s 1.009225s ``` refs: #1531
2022-01-12 08:39:19 +03:00
"chrono",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"config",
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
"crossbeam",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"downcast-rs",
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
"filedescriptor",
split out tmux commands
2021-08-23 15:48:09 +03:00
"flume",
mux: track list of clients Define a way to compute a client ID and pass that through to the mux server when verifying version compatibility. Once associated, the session handler will keep some metadata updated in the mux. A new cli subcommand exposes the info: ``` ; ./target/debug/wezterm cli list-clients USER HOST PID CONNECTED IDLE WORKSPACE wez mba.localdomain 52979 30.009225s 1.009225s ``` refs: #1531
2022-01-12 08:39:19 +03:00
"hostname",
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
"k9",
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",
fixup build for macos
2020-10-05 19:11:17 +03:00
"libc",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"log",
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",
mux: add some metrics around reading from ptys
2021-07-11 06:53:10 +03:00
"metrics",
mux: understand process tree, add mux-is-process-stateful event This commit adds plumbing to support mapping the process tree to lua objects which in turn allows a new `mux-is-process-stateful` event to be defined by the user for finer control over closing prompt behavior. refs: #1412
2021-12-18 18:44:18 +03:00
"mlua",
mux: function to list workspaces and generate a new name refs: #1531
2022-01-15 18:46:21 +03:00
"names",
mux: remove dep on sysinfo; we now do our own win32 stuff This also removes the sysinfo cache; will replace it with something else in a follow up commit.
2022-01-01 05:20:51 +03:00
"ntapi",
refactor: move split_pane logic from mux server to mux
2022-01-14 20:59:20 +03:00
"percent-encoding",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"portable-pty",
move procinfo bits into own crate
2022-01-01 05:30:52 +03:00
"procinfo",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"promise",
"rangeset",
"regex",
"serde",
ssh: use `env` when assume_shell=Posix This allows us to send over COLORTERM and TERM_PROGRAM_XXX environment that the SSH server would have denied via AcceptEnv rules.
2022-01-26 20:44:27 +03:00
"shell-words",
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",
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
"terminfo",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"termwiz",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
"termwiz-funcs",
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
"textwrap 0.15.0",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"thiserror",
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
"unicode-segmentation",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"url",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
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",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"wezterm-term",
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
"winapi 0.3.9",
move mux to its own crate
2020-10-03 03:42:49 +03:00
]
mux: function to list workspaces and generate a new name refs: #1531
2022-01-15 18:46:21 +03:00
[[package]]
name = "names"
version = "0.12.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10a8690bf09abf659851e58cd666c3d37ac6af07c2bd7a9e332cfba471715775"
dependencies = [
cargo update
2022-02-22 05:44:27 +03:00
"rand 0.8.5",
mux: function to list workspaces and generate a new name refs: #1531
2022-01-15 18:46:21 +03:00
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "nanorand"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "0.7.0"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "6a51313c5820b0b02bd422f4b44776fbf47961755c74ce64afc73bfad10226c3"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
cargo update
2022-04-04 04:26:59 +03:00
"getrandom 0.2.6",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
[[package]]
name = "native-tls"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.2.10"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "fd7e2f3618557f980e0b17e8856252eee3c97fa12c54dff0ca290fb6266ca4a9"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
dependencies = [
"lazy_static",
"libc",
"log",
"openssl",
"openssl-probe",
"openssl-sys",
"schannel",
"security-framework",
"security-framework-sys",
"tempfile",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "net2"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
version = "0.2.37"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
checksum = "391630d12b68002ae1e25e8f974306474966550ad82dac6886fb8910c19568ae"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
[[package]]
name = "nix"
cargo update
2022-01-24 08:19:09 +03:00
version = "0.22.3"
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-24 08:19:09 +03:00
checksum = "e4916f159ed8e5de0082076562152a76b7a1f64a01fd9d1e0fea002c37624faf"
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
dependencies = [
"bitflags",
"cc",
"cfg-if 1.0.0",
"libc",
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
"memoffset",
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
]
cargo update
2021-03-01 20:02:05 +03:00
[[package]]
name = "nix"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
version = "0.23.1"
cargo update
2021-03-01 20:02:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
checksum = "9f866317acbd3a240710c63f065ffb1e4fd466259045ccb504130b7f668f35c6"
cargo update
2021-03-01 20:02:05 +03:00
dependencies = [
"bitflags",
"cc",
"cfg-if 1.0.0",
"libc",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"memoffset",
cargo update
2021-03-01 20:02:05 +03:00
]
deps: nix -> 0.24
2022-05-05 04:55:56 +03:00
[[package]]
name = "nix"
version = "0.24.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f17df307904acd05aa8e32e97bb20f2a0df1728bbc2d771ae8f9a90463441e9"
dependencies = [
"bitflags",
"cfg-if 1.0.0",
"libc",
"memoffset",
]
bump some versions
2020-01-10 09:39:34 +03:00
[[package]]
name = "nom"
cargo update
2020-06-13 20:21:49 +03:00
version = "5.1.2"
bump some versions
2020-01-10 09:39:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-13 20:21:49 +03:00
checksum = "ffb4262d26ed83a1c0a33a38fe2bb15797329c85770da05e6b828ddb782627af"
bump some versions
2020-01-10 09:39:34 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"memchr",
"version_check",
]
cargo update
2021-08-23 17:33:44 +03:00
[[package]]
name = "nom"
deps: cargo update
2022-03-21 17:47:57 +03:00
version = "7.1.1"
cargo update
2021-08-23 17:33:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-03-21 17:47:57 +03:00
checksum = "a8903e5a29a317527874d0402f867152a3d21c908bb0b933e416c65e301d4c36"
cargo update
2021-08-23 17:33:44 +03:00
dependencies = [
"memchr",
"minimal-lexical",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "nonzero_ext"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "db1b4163932b207be6e3a06412aed4d84cca40dc087419f231b3a38cba2ca8e9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "normalize-line-endings"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "61807f77802ff30975e01f4f071c8ba10c022052f98b3294119f3e615d13e5be"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "notify"
cargo update
2021-05-17 17:28:56 +03:00
version = "4.0.17"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-17 17:28:56 +03:00
checksum = "ae03c8c853dba7bfd23e571ff0cff7bc9dceb40a4cd684cd1681824183f45257"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filetime",
"fsevent",
"fsevent-sys",
"inotify",
"libc",
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
"mio 0.6.23",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"mio-extras",
"walkdir",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
refine skip_close_confirmation_for_processes_named to look at proc tree That means that we won't be fooled by a shell with a backgrounded editor. refs: https://github.com/wez/wezterm/issues/562
2021-03-23 07:34:10 +03:00
[[package]]
name = "ntapi"
cargo update
2022-02-14 06:31:40 +03:00
version = "0.3.7"
refine skip_close_confirmation_for_processes_named to look at proc tree That means that we won't be fooled by a shell with a backgrounded editor. refs: https://github.com/wez/wezterm/issues/562
2021-03-23 07:34:10 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-14 06:31:40 +03:00
checksum = "c28774a7fd2fbb4f0babd8237ce554b73af68021b5f695a3cebd6c59bac0980f"
refine skip_close_confirmation_for_processes_named to look at proc tree That means that we won't be fooled by a shell with a backgrounded editor. refs: https://github.com/wez/wezterm/issues/562
2021-03-23 07:34:10 +03:00
dependencies = [
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "num"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.3.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "8b7a8e9be5e039e2ff869df49155f1c06bd01ade2117ec783e56ab0932b67a8f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-09-06 09:23:40 +03:00
"num-bigint",
"num-complex",
cargo update for latest xcb-imdkit refs: #1064
2021-08-26 04:57:57 +03:00
"num-integer",
"num-iter",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"num-rational 0.3.2",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "num-bigint"
cargo update
2021-09-06 09:23:40 +03:00
version = "0.3.3"
cargo update for latest xcb-imdkit refs: #1064
2021-08-26 04:57:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-09-06 09:23:40 +03:00
checksum = "5f6f7833f2cbf2360a6cfd58cd41a53aa7a90bd4c202f5b1c7dd2ed73c57b2c3"
cargo update for latest xcb-imdkit refs: #1064
2021-08-26 04:57:57 +03:00
dependencies = [
"autocfg",
"num-integer",
"num-traits",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "num-complex"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.3.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "747d632c0c558b87dbabbe6a82f3b4ae03720d0646ac5b7b4dae89394be5f2c5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "num-derive"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.3.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "876a53fff98e03a936a674b29568b0e605f06b29372c2489ff4de23f1949743d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "num-integer"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.1.45"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "225d3389fb3509a24c93f5c29eb6bde2586b98d9f016636dff58d7c6f7569cd9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "num-iter"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.1.43"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "7d03e6c028c5dc5cac6e2dec0efda81fc887605bb3d884578bb6d6bf7514e252"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"num-integer",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "num-rational"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.3.2"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "12ac428b1cb17fce6f731001d307d351ec70a6d202fc2e60f7d4c5e42d8f4f07"
cargo update
2020-06-30 03:52:14 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update
2021-09-06 09:23:40 +03:00
"num-bigint",
cargo update
2020-06-30 03:52:14 +03:00
"num-integer",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "num-rational"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d41702bd167c2df5520b384281bc111a4b5efcf7fbc4c9c222c815b07e0a6a6a"
dependencies = [
"autocfg",
"num-integer",
"num-traits",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "num-traits"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "0.2.15"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "578ede34cf02f8924ab9447f50c28075b4d3e5b269972345e7e0372b38c6cdcd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "num_cpus"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
version = "1.13.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
checksum = "19e64526ebdee182341572e50e9ad03965aa510cd94427a4549448f285e957a1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hermit-abi",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
[[package]]
name = "num_threads"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2819ce041d2ee131036f4fc9d6ae7ae125a3a40e97ba64d04fe799ad9dabbb44"
dependencies = [
"libc",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "objc"
version = "0.2.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "915b1b472bc21c53464d6c8461c9d3af805ba1ef837e1cac254428f4a77177b1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"malloc_buf",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "objc-foundation"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "1add1b659e36c9607c7aab864a76c7a4c2760cd0cd2e120f3fb8b952c7e22bf9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"block",
"objc",
"objc_id",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "objc_id"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "c92d4ddb4bd7b50d730c215ff871754d0da6b2178849f8a2a2ab69712d0c073b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"objc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2020-05-26 08:25:39 +03:00
[[package]]
name = "object"
cargo update
2022-05-16 05:44:27 +03:00
version = "0.28.4"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "e42c982f2d955fac81dd7e1d0e1426a7d702acd9c98d19ab01083a6a0328c424"
cargo update
2021-06-07 18:32:05 +03:00
dependencies = [
"memchr",
]
cargo update
2020-05-26 08:25:39 +03:00
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "once_cell"
cargo update
2022-03-09 17:31:53 +03:00
version = "1.10.0"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-03-09 17:31:53 +03:00
checksum = "87f3e037eac156d1775da914196f0f37741a274155e34a0b7e427c35d2a2ecb9"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "opaque-debug"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2839e79665f131bdb5782e51f2c6c9599c133c6098982a54c794358bf432529c"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "opaque-debug"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "624a8340c38c1b80fd549087862da4ba43e08858af025b236e509b6649fc13d5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "open"
cargo update
2022-05-02 07:21:14 +03:00
version = "2.1.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "e0524af9508f9b5c4eb41dce095860456727748f63b478d625f119a70e0d764a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
"pathdiff",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "openssl"
cargo update
2021-11-03 16:41:06 +03:00
version = "0.10.38"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-11-03 16:41:06 +03:00
checksum = "0c7ae222234c30df141154f159066c5093ff73b63204dcda7121eb082fc56a95"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
build(deps): bump openssl from 0.10.30 to 0.10.31 Bumps [openssl](https://github.com/sfackler/rust-openssl) from 0.10.30 to 0.10.31. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-v0.10.30...openssl-v0.10.31) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-10 10:11:07 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
cargo update
2021-03-15 16:32:14 +03:00
"once_cell",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"openssl-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
[[package]]
name = "openssl-probe"
cargo update
2022-01-17 04:46:30 +03:00
version = "0.1.5"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "ff011a302c396a5197692431fc1948019154afc178baf7d8e37367442a4601cf"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "openssl-src"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "300.0.6+3.0.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "9ddc3e825b97984039e35930b676557b3beb327220d1e711371d2885cdfbe311"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "openssl-sys"
fix windows build A recent cargo update caused openssl-sys to do a minor semver update from 0.9.71 -> 0.9.72, but that release downgraded from openssl 3 to openssl 1 to resolve a performance regression: <https://github.com/sfackler/rust-openssl/pull/1578> That in turn caused libssh to fail to build because the ENGINE feature required by libssh isn't compiled in in openssl-src 1 crate when vendoring on windows. For now, my libssh git repo is constrained to openssl-sys 0.9.71, and we're pointing to that from the wezterm repo.
2021-12-13 19:00:13 +03:00
version = "0.9.71"
remove patched openssl-sys crate The appropriate openssl-src is now used upstream
2021-11-03 16:38:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
fix windows build A recent cargo update caused openssl-sys to do a minor semver update from 0.9.71 -> 0.9.72, but that release downgraded from openssl 3 to openssl 1 to resolve a performance regression: <https://github.com/sfackler/rust-openssl/pull/1578> That in turn caused libssh to fail to build because the ENGINE feature required by libssh isn't compiled in in openssl-src 1 crate when vendoring on windows. For now, my libssh git repo is constrained to openssl-sys 0.9.71, and we're pointing to that from the wezterm repo.
2021-12-13 19:00:13 +03:00
checksum = "7df13d165e607909b363a4757a6f133f8a818a74e9d3a98d09c6128e15fa4c73"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
"openssl-src",
"pkg-config",
"vcpkg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "ordered-float"
deps: ordered-float closes: https://github.com/wez/wezterm/pull/1946
2022-05-02 07:43:22 +03:00
version = "3.0.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: ordered-float closes: https://github.com/wez/wezterm/pull/1946
2022-05-02 07:43:22 +03:00
checksum = "96bcbab4bfea7a59c2c0fe47211a1ac4e3e96bea6eb446d704f310bc5c732ae2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
FEATURE: Allow ScrollByPage f64 values `ScrollByPage` can accept non-integer values in the configuration. This allows fractional page scrolling, such as by half a page. The default remains the same, at 1 page.
2022-01-12 08:49:36 +03:00
"serde",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
[[package]]
name = "ordered-stream"
version = "0.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44630c059eacfd6e08bdaa51b1db2ce33119caa4ddc1235e923109aa5f25ccb1"
dependencies = [
"futures-core",
"pin-project-lite",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "parking"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "427c3892f9e783d91cc128285287e70a59e206ca452770ece88a76f7a3eddd72"
cargo update
2020-06-30 03:52:14 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "parking_lot"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f842b1982eb6c2fe34036a4fbfb06dd185a3f5c8edfaacdf7d1ea10b07de6252"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
"lock_api 0.3.4",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
"parking_lot_core 0.6.2",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"rustc_version 0.2.3",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
[[package]]
name = "parking_lot"
cargo update
2021-08-30 07:30:03 +03:00
version = "0.11.2"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-30 07:30:03 +03:00
checksum = "7d17b78036a60663b797adeaee46f5c9dfebb86948d1255007a1d6be0271ff99"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
dependencies = [
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
"instant",
cargo update
2022-04-04 04:26:59 +03:00
"lock_api 0.4.7",
cargo update
2021-08-30 07:30:03 +03:00
"parking_lot_core 0.8.5",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "parking_lot_core"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "b876b1b9e7ac6e1a74a6da34d25c42e17e8862aa409cbbbdcfc8d86c6f3bc62b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cloudabi",
"libc",
cargo update
2021-01-11 19:43:32 +03:00
"redox_syscall 0.1.57",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"rustc_version 0.2.3",
cargo update
2021-01-11 19:43:32 +03:00
"smallvec 0.6.14",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
[[package]]
name = "parking_lot_core"
cargo update
2021-08-30 07:30:03 +03:00
version = "0.8.5"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-30 07:30:03 +03:00
checksum = "d76e8e1493bcac0d2766c42737f34458f1c8c50c0d23bcb24ea953affb273216"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
dependencies = [
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
"cfg-if 1.0.0",
"instant",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
"libc",
cargo update
2022-04-04 04:26:59 +03:00
"redox_syscall 0.2.13",
cargo update
2022-01-17 04:46:30 +03:00
"smallvec 1.8.0",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
]
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
[[package]]
name = "pathdiff"
deps: cargo update
2021-10-04 08:10:01 +03:00
version = "0.2.1"
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2021-10-04 08:10:01 +03:00
checksum = "8835116a5c179084a830efb3adc117ab007512b535bc1a21c991d3b32a6b44dd"
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
[[package]]
name = "pem"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "1.0.2"
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "e9a3b09a20e374558580a4914d3b7d89bd61b954a5a5e1dcbea98753addb1947"
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
]
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "percent-encoding"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "pest"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10f4872ae94d7b90ae48754df22fd42ad52ce740b8f370b03da4835417403e53"
dependencies = [
"ucd-trie",
]
[[package]]
name = "pest_derive"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "833d1ae558dc601e9a60366421196a8d94bc0ac980476d0b67e1d0988d72b2d0"
dependencies = [
"pest",
"pest_generator",
]
[[package]]
name = "pest_generator"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "99b8db626e31e5b81787b9783425769681b347011cc59471e33ea46d2ea0cf55"
dependencies = [
"pest",
"pest_meta",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
]
[[package]]
name = "pest_meta"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "54be6e404f5317079812fc8f9f5279de376d8856929e21c184ecf6bbd692a11d"
dependencies = [
"maplit",
"pest",
"sha-1",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "phf"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "3dfb61232e34fcb633f43d12c58f83c1df82962dcdfa565a4e866ffc17dafe12"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
"phf_macros",
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
"phf_shared 0.8.0",
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
"proc-macro-hack",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
[[package]]
name = "phf"
version = "0.10.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fabbf1ead8a5bcbc20f5f8b939ee3f5b0f6f281b6ad3468b84656b658b455259"
dependencies = [
"phf_shared 0.10.0",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "phf_codegen"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "cbffee61585b0411840d3ece935cce9cb6321f01c45477d30066498cd5e1a815"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"phf_generator",
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
"phf_shared 0.8.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "phf_generator"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "17367f0cc86f2d25802b2c26ee58a7b23faeccf78a396094c13dced0d0182526"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
"phf_shared 0.8.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand 0.7.3",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
[[package]]
name = "phf_macros"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f6fde18ff429ffc8fe78e2bf7f8b7a5a5a6e2a8b58bc5a9ac69198bbda9189c"
dependencies = [
"phf_generator",
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
"phf_shared 0.8.0",
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
"proc-macro-hack",
"proc-macro2",
"quote",
"syn",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "phf_shared"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "c00cf8b9eafe68dde5e9eaa2cef8ee84a9336a47d566ec55ca16589633b65af7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"siphasher",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
[[package]]
name = "phf_shared"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6796ad771acdc0123d2a88dc428b5e38ef24456743ddb1744ed628f9815c096"
dependencies = [
"siphasher",
]
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "pin-project"
cargo update
2022-01-03 05:48:38 +03:00
version = "1.0.10"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-03 05:48:38 +03:00
checksum = "58ad3879ad3baf4e44784bc6a718a8698867bb991f8ce24d1bcbe2cfb4c3a75e"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"pin-project-internal",
]
[[package]]
name = "pin-project-internal"
cargo update
2022-01-03 05:48:38 +03:00
version = "1.0.10"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-03 05:48:38 +03:00
checksum = "744b6f092ba29c3650faf274db506afd39944f48420f6c86b17cfe0ee1cb36bb"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
]
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
[[package]]
name = "pin-project-lite"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.2.9"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "e0a7ae3ac2f1173085d398531c705756c94a4c56843785df85a60c1a0afac116"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "pin-utils"
cargo update
2020-05-02 22:13:10 +03:00
version = "0.1.0"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-02 22:13:10 +03:00
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "pkg-config"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.3.25"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "1df8c4ec4b0627e53bdf214615ad287367e482558cf84b109250b37464dc03ae"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
[[package]]
name = "png"
cargo update
2022-03-09 17:31:53 +03:00
version = "0.17.5"
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-03-09 17:31:53 +03:00
checksum = "dc38c0ad57efb786dd57b9864e5b18bae478c00c824dc55a38bbc9da95dde3ba"
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
dependencies = [
"bitflags",
"crc32fast",
cargo update
2022-02-14 06:31:40 +03:00
"deflate",
"miniz_oxide 0.5.1",
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "polling"
cargo update Mostly to pick up a libssh fix on arm refs: https://github.com/wez/libssh-rs/issues/2
2021-11-15 01:45:37 +03:00
version = "2.2.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update Mostly to pick up a libssh fix on arm refs: https://github.com/wez/libssh-rs/issues/2
2021-11-15 01:45:37 +03:00
checksum = "685404d509889fade3e86fe3a5803bca2ec09b0c0778d5ada6ec8bf7a8de5259"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
cargo update
2021-03-22 06:18:02 +03:00
"cfg-if 1.0.0",
cargo update
2020-09-09 19:31:37 +03:00
"libc",
"log",
cargo update
2021-06-21 05:06:54 +03:00
"wepoll-ffi",
cargo update
2020-09-09 19:31:37 +03:00
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "portable-pty"
pty: introduce ChildKiller trait In the mux layer, we have some code that takes a `Child` and then does a bit of naughty reaching through the abstraction to get at the pid/handle of the child so that we can send it signals even if the child is itself mutably (and thus exclusively) borrowed for the purposes of waiting. That worked fine for local processes spawned in the mux, but we also use LocalPane to wrap around arbitrary `Child`ren, such as Ssh, that are not local and that don't have a local process id, which meant that this hack wouldn't work for them. To make things a bit worse, those ssh ptys were used to ssh2 days where we didn't have a way to signal the remote process and just did nothing, leading to confusing situations such as https://github.com/wez/wezterm/issues/1197 This commit graduates the hack mentioned in the first paragraph to its own ChildKiller trait. This makes the concept of waiting for the Child distinct from signalling it and explicitly allows getting a separate object that can be used for signalling. With that in place, we're forced to implement something appropriate for the ssh pty implementations; one in the pty crate itself, one in wezterm-ssh and the wrapper that we use in the mux crate. The upshot of this is that the `CloseCurrentPane` action now operates correctly on panes that were the result of split operations.
2021-12-11 18:32:21 +03:00
version = "0.7.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
term: ignore first OSC title change sequence on Windows ConPTY emits a sequence that sets the title to the name of the program that is initially launched into it. This commit tries to ignore that sequence in that circumstance, so that the logic in b5d156c282a01f2f1cb10aee98655a4a2c2c71e5 can more dynamically set the tab title.
2021-12-25 10:58:25 +03:00
"downcast-rs",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filedescriptor",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
"futures",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
"log",
"serde",
"serde_derive",
"serial",
"shared_library",
"shell-words",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
"smol",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"ssh2",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
pty: pre-fill base env from registry env settings on Windows I think I'd like to make a config option for this, but for the moment, this first pass unconditionally updates the base environment with data from the registry. refs: https://github.com/wez/wezterm/issues/1848
2022-04-19 19:56:23 +03:00
"winreg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "ppv-lite86"
cargo update
2022-01-03 05:48:38 +03:00
version = "0.2.16"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-03 05:48:38 +03:00
checksum = "eb9f9e6e233e5c4a35559a617bf40a4ec447db2e84c20b55a6f83167b7e57872"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "predicates"
cargo update
2022-01-17 04:46:30 +03:00
version = "2.1.1"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "a5aab5be6e4732b473071984b3164dbbfb7a3674d30ea5ff44410b6bcd960c3c"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
dependencies = [
"difflib",
"float-cmp",
remove our incomplete allsorts shaper implementation We rely on using freetype in order to support more fonts in more situations, and we have a deeper existing integration with harfbuzz. I'm unlikely to come back to allsorts to complete our integration, and in the meantime, it just adds overhead to build/test and those builds are taking longer and longer. I loved the idea of using pure rust for all the font stuff, but its time is not now. closes: #587 closes: #66
2021-11-23 15:43:13 +03:00
"itertools",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"normalize-line-endings",
"predicates-core",
"regex",
]
[[package]]
name = "predicates-core"
cargo update
2022-01-17 04:46:30 +03:00
version = "1.0.3"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "da1c2388b1513e1b605fcec39a95e0a9e8ef088f71443ef37099fa9ae6673fcb"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "predicates-tree"
cargo update
2022-01-17 04:46:30 +03:00
version = "1.0.5"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "4d86de6de25020a36c6d3643a86d9a6a9f552107c0559c60ea03551b5e16c032"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
dependencies = [
"predicates-core",
cargo update
2021-10-11 05:15:00 +03:00
"termtree",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
]
cargo update
2021-06-14 09:36:22 +03:00
[[package]]
name = "proc-macro-crate"
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
version = "1.1.3"
cargo update
2021-06-14 09:36:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
checksum = "e17d47ce914bf4de440332250b0edd23ce48c005f59fab39d3335866b114f11a"
cargo update
2021-06-14 09:36:22 +03:00
dependencies = [
"thiserror",
"toml",
]
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
[[package]]
name = "proc-macro-error"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.0.4"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "da25490ff9892aab3fcf7c36f08cfb902dd3e71ca0f9f9517bea02a73a5ce38c"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
dependencies = [
"proc-macro-error-attr",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"version_check",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
]
[[package]]
name = "proc-macro-error-attr"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.0.4"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "a1be40180e52ecc98ad80b184934baf3d0d29f979574e439af5a55274b35f869"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"version_check",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
]
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
[[package]]
name = "proc-macro-hack"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.5.19"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "dbf0c48bc1d91375ae5c3cd81e3722dff1abcf81a30960240640d223f59fe0e5"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "proc-macro2"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "1.0.38"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "9027b48e9d4c9175fa2218adf3557f91c1137021739951d4932f5f8268ac48aa"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"unicode-xid",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
move procinfo bits into own crate
2022-01-01 05:30:52 +03:00
[[package]]
name = "procinfo"
version = "0.1.0"
dependencies = [
"libc",
procinfo: windows: tweak and add more tracing Use an alternative function to query the executable path for a target process. Add more tracing. refs: #1896
2022-04-20 19:43:56 +03:00
"log",
move procinfo bits into own crate
2022-01-01 05:30:52 +03:00
"luahelper",
"ntapi",
cut more things over to dynamic
2022-05-17 19:48:50 +03:00
"wezterm-dynamic",
move procinfo bits into own crate
2022-01-01 05:30:52 +03:00
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "promise"
version = "0.2.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
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",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"async-std",
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
"flume",
move spawn_task into a new promise::spawn module
2020-01-16 14:39:44 +03:00
"lazy_static",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"thiserror",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
[[package]]
name = "pulldown-cmark"
cargo update
2022-01-24 08:19:09 +03:00
version = "0.9.1"
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-24 08:19:09 +03:00
checksum = "34f197a544b0c9ab3ae46c359a7ec9cbbb5c7bf97054266fecb7ead794a181d6"
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
"getopts",
"memchr",
"unicase",
]
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
[[package]]
name = "pure-rust-locales"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.5.6"
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-05 18:46:55 +03:00
checksum = "b45c49fc4f91f35bae654f85ebb3a44d60ac64f11b3166ffa609def390c732d8"
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
window: deps: upgrade to xcb 1.1 Was a bit fiddly. Eliminated the xcb_util crate refs: https://github.com/wez/wezterm/issues/1952
2022-05-08 00:18:26 +03:00
[[package]]
name = "quick-xml"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8533f14c8382aaad0d592c812ac3b826162128b65662331e1127b45c3d18536b"
dependencies = [
"memchr",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "quote"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "1.0.18"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "a1feb54ed693b93a84e14094943b84b7c4eae204c512b7ccb95ab0c66d278ad1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "552840b97013b1a26992c11eac34bdd778e464601a4c2054b5f0bff7c6761293"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fuchsia-cprng",
"libc",
"rand_core 0.3.1",
"rdrand",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
version = "0.7.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"getrandom 0.1.16",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
"rand_chacha 0.2.2",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.5.1",
cargo update
2022-02-22 05:44:27 +03:00
"rand_hc",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_pcg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
[[package]]
name = "rand"
cargo update
2022-02-22 05:44:27 +03:00
version = "0.8.5"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-22 05:44:27 +03:00
checksum = "34af8d1a0e25924bc5b7c43c079c942339d8f0a8b57c39049bef581b46327404"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
dependencies = [
"libc",
"rand_chacha 0.3.1",
"rand_core 0.6.3",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rand_chacha"
cargo update
2020-03-14 19:39:38 +03:00
version = "0.2.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-03-14 19:39:38 +03:00
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-03-14 19:39:38 +03:00
"ppv-lite86",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.5.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
[[package]]
name = "rand_chacha"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e6c10a63a0fa32252be49d21e7709d4d4baf8d231c2dbce1eaa8141b9b127d88"
dependencies = [
"ppv-lite86",
"rand_core 0.6.3",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rand_core"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.4.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand_core"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "9c33a3c44ca05fa6f1807d8e6743f3824e8509beca625669633be0acbdf509dc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rand_core"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"getrandom 0.1.16",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
[[package]]
name = "rand_core"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d34f1408f55294453790c48b2f1ebbb1c5b4b7563eb1f418bcfcfdbb06ebb4e7"
dependencies = [
cargo update
2022-04-04 04:26:59 +03:00
"getrandom 0.2.6",
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.5.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand_pcg"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.2.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "16abd0c1b639e9eb4d7c50c0b8100b0d0f849be2349829c740fe8e6eb4816429"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.5.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add RangeSet type The idea is to use this to maintain a set of dirty StableRowIndex values for the mux rpc.
2020-01-05 05:10:53 +03:00
[[package]]
name = "rangeset"
version = "0.1.0"
dependencies = [
cargo update
2021-09-06 09:23:40 +03:00
"num",
add RangeSet type The idea is to use this to maintain a set of dirty StableRowIndex values for the mux rpc.
2020-01-05 05:10:53 +03:00
]
move ratelim to its own crate
2020-10-03 03:31:39 +03:00
[[package]]
name = "ratelim"
version = "0.1.0"
dependencies = [
"config",
"ratelimit_meter",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ratelimit_meter"
version = "5.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "a37d4f95369ef809d01448bdf8d82ef974e3b21f3698d87015a575bb26f27724"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"evmap",
"nonzero_ext",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
"parking_lot 0.9.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add raw-window-handle impls
2021-05-06 08:59:52 +03:00
[[package]]
name = "raw-window-handle"
cargo update
2021-11-29 05:09:45 +03:00
version = "0.3.4"
add raw-window-handle impls
2021-05-06 08:59:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-11-29 05:09:45 +03:00
checksum = "e28f55143d0548dad60bb4fbdc835a3d7ac6acc3324506450c5fdd6e42903a76"
add raw-window-handle impls
2021-05-06 08:59:52 +03:00
dependencies = [
"libc",
cargo update
2022-04-04 04:26:59 +03:00
"raw-window-handle 0.4.3",
cargo update
2021-11-29 05:09:45 +03:00
]
[[package]]
name = "raw-window-handle"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.4.3"
cargo update
2021-11-29 05:09:45 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "b800beb9b6e7d2df1fe337c9e3d04e3af22a124460fb4c30fcc22c9117cefb41"
cargo update
2021-11-29 05:09:45 +03:00
dependencies = [
"cty",
add raw-window-handle impls
2021-05-06 08:59:52 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rayon"
cargo update
2022-05-16 05:44:27 +03:00
version = "1.5.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "bd99e5772ead8baa5215278c9b15bf92087709e9c1b2d1f97cdb5a183c933a7d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-deque",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"either",
"rayon-core",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rayon-core"
cargo update
2022-05-16 05:44:27 +03:00
version = "1.9.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "258bcdb5ac6dad48491bb2992db6b7cf74878b0384908af124823d118c99683f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-channel",
"crossbeam-deque",
"crossbeam-utils",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"num_cpus",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
[[package]]
name = "rcgen"
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
version = "0.9.2"
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
checksum = "d7fa2d386df8533b02184941c76ae2e0d0c1d053f5d43339169d80f21275fc5e"
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
dependencies = [
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"pem",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"ring",
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
"time 0.3.9",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"yasna",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rdrand"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.3.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "redox_syscall"
cargo update
2020-09-09 19:31:37 +03:00
version = "0.1.57"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2021-01-11 19:43:32 +03:00
[[package]]
name = "redox_syscall"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.2.13"
cargo update
2021-01-11 19:43:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "62f25bc4c7e55e0b0b7a1d43fb893f4fa1361d0abe38b9ce4f323c2adfe6ef42"
cargo update
2021-01-11 19:43:32 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update
2021-01-11 19:43:32 +03:00
]
[[package]]
name = "redox_users"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.4.3"
cargo update
2021-01-11 19:43:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "b033d837a7cf162d7993aded9304e30a83213c648b6e389db233191f891e5c2b"
cargo update
2021-01-11 19:43:32 +03:00
dependencies = [
cargo update
2022-04-04 04:26:59 +03:00
"getrandom 0.2.6",
"redox_syscall 0.2.13",
deps: cargo update
2022-03-21 17:47:57 +03:00
"thiserror",
cargo update
2021-01-11 19:43:32 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "regex"
cargo update
2022-03-09 17:31:53 +03:00
version = "1.5.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-03-09 17:31:53 +03:00
checksum = "1a11647b6b25ff05a515cb92c365cec08801e83423a235b51e231e1808747286"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-02-11 18:49:05 +03:00
"aho-corasick",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"memchr",
cargo update
2020-02-11 18:49:05 +03:00
"regex-syntax",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
lua: add serde-powered to_lua_value function This will help in implementing lua helper functions for various config and other structures.
2020-03-01 08:46:59 +03:00
[[package]]
name = "regex-automata"
cargo update
2021-06-07 18:32:05 +03:00
version = "0.1.10"
lua: add serde-powered to_lua_value function This will help in implementing lua helper functions for various config and other structures.
2020-03-01 08:46:59 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-07 18:32:05 +03:00
checksum = "6c230d73fb8d8c1b9c0b3135c5142a8acee3a0558fb8db5cf1cb65f8d7862132"
lua: add serde-powered to_lua_value function This will help in implementing lua helper functions for various config and other structures.
2020-03-01 08:46:59 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "regex-syntax"
cargo update
2021-05-03 19:34:29 +03:00
version = "0.6.25"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-03 19:34:29 +03:00
checksum = "f497285884f3fcff424ffc933e56d7cbca511def0c9831a7f9b5f6153e3cc89b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "remove_dir_all"
cargo update
2020-06-13 20:21:49 +03:00
version = "0.5.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-13 20:21:49 +03:00
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "resize"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.5.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f2a08c42ea86684dc00256494c4eb8b54707890ddac50c05060a717f29669029"
dependencies = [
"rgb",
]
[[package]]
name = "rgb"
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
version = "0.8.32"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
checksum = "e74fdc210d8f24a7dbfedc13b04ba5764f5232754ccebfdf5fff1bad791ccbc6"
deps: misc updates
2020-12-29 20:21:50 +03:00
dependencies = [
"bytemuck",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "ring"
cargo update
2021-02-04 10:28:23 +03:00
version = "0.16.20"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-04 10:28:23 +03:00
checksum = "3053cf52e236a3ed746dfc745aa9cacf1b791d846bdaf412f60a8d7d6e17c8fc"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"cc",
"libc",
cargo update
2020-05-02 22:13:10 +03:00
"once_cell",
cargo update
2021-08-25 20:00:33 +03:00
"spin 0.5.2",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"untrusted",
"web-sys",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "rstest"
cargo update
2022-05-16 05:44:27 +03:00
version = "0.13.0"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "b939295f93cb1d12bc1a83cf9ee963199b133fb8a79832dd51b68bb9f59a04dc"
dependencies = [
"async-std",
"futures",
"futures-timer",
"rstest_macros",
"rustc_version 0.4.0",
]
[[package]]
name = "rstest_macros"
version = "0.13.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f78aba848123782ba59340928ec7d876ebe745aa0365d6af8a630f19a5c16116"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
dependencies = [
"cfg-if 1.0.0",
"proc-macro2",
"quote",
"rustc_version 0.4.0",
"syn",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rustc-demangle"
cargo update
2021-08-25 20:00:33 +03:00
version = "0.1.21"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-25 20:00:33 +03:00
checksum = "7ef03e0a2b150c7a90d01faf6254c9c48a41e95fb2a8c2ac1c6f0d2b9aefc342"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
Add get_foreground_process_name, expose it and cwd in PaneInformation Add `get_foreground_process_name` to both Pane and the lua wrapper. Add `foreground_process_name` and `current_working_dir` fields to `PaneInformation`. In order for those to be dynamically fetched, switch the lua conversion for `PaneInformation` to be a UserData with field access methods. It's a little more verbose but allows us to lazily compute these two new fields. refs: https://github.com/wez/wezterm/discussions/1421 refs: https://github.com/wez/wezterm/issues/915 refs: https://github.com/wez/wezterm/issues/876
2021-12-24 04:44:12 +03:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"semver 0.9.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "rustc_version"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfa0f585226d2e68097d4f95d113b15b83a82e819ab25717ec0590d9584ef366"
dependencies = [
cargo update
2022-05-02 07:21:14 +03:00
"semver 1.0.9",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
]
bump some versions
2020-01-10 09:39:34 +03:00
[[package]]
name = "ryu"
cargo update
2022-05-16 05:44:27 +03:00
version = "1.0.10"
bump some versions
2020-01-10 09:39:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "f3f6f92acf49d1b98f7a81226834412ada05458b7364277387724a237f062695"
bump some versions
2020-01-10 09:39:34 +03:00
zeno -> tiny_skia Mostly so that we can turn off anti-aliasing for smaller sizes, but it also happens to be more complete anyway.
2021-06-26 08:55:42 +03:00
[[package]]
name = "safe_arch"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c1ff3d6d9696af502cc3110dacce942840fb06ff4514cad92236ecc455f2ce05"
dependencies = [
"bytemuck",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "same-file"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
version = "1.0.6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "93fc1dc3aaa9bfed95e02e6eadabb4baf7e3078b0bd1b4d7b6b0b68378900502"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi-util",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
[[package]]
name = "schannel"
version = "0.1.19"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8f05ba609c234e60bee0d547fe94a4c7e9da733d1c962cf6e59efa4cd9c8bc75"
dependencies = [
"lazy_static",
"winapi 0.3.9",
]
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
cargo update
2020-06-30 03:52:14 +03:00
name = "scoped-tls"
version = "1.0.0"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "ea6a9290e3c9cf0f18145ef7ffa62d68ee0bf5fcd651017e586dc7fd5da448c2"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "scoped_threadpool"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "1d51f5df5af43ab3f1360b429fa5e0152ac5ce8c0bd6485cae490332e96846a8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "scopeguard"
cargo update
2020-03-14 19:39:38 +03:00
version = "1.1.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-03-14 19:39:38 +03:00
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
name = "security-framework"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "2.6.1"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "2dc14f172faf8a0194a3aded622712b0de276821addc574fa54fc0a1167e10dc"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
dependencies = [
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
"bitflags",
cargo update
2022-02-14 06:31:40 +03:00
"core-foundation 0.9.3",
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
"core-foundation-sys 0.8.3",
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
"libc",
"security-framework-sys",
]
[[package]]
name = "security-framework-sys"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "2.6.1"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "0160a13a177a45bfb43ce71c01580998474f556ad854dcbca936dd2841a5c556"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
dependencies = [
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
"core-foundation-sys 0.8.3",
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
"libc",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"semver-parser 0.7.0",
]
[[package]]
name = "semver"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f301af10236f6df4160f7c3f04eec6dbc70ace82d23326abad5edee88801c6b6"
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"semver-parser 0.10.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "semver"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.0.9"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "8cb243bdfdb5936c8dc3c45762a19d12ab4550cdc753bc247637d4ec35a040fd"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
deps: misc updates
2020-12-29 20:21:50 +03:00
[[package]]
name = "semver-parser"
cargo update
2021-01-06 11:28:11 +03:00
version = "0.10.2"
deps: misc updates
2020-12-29 20:21:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-06 11:28:11 +03:00
checksum = "00b0bef5b7f9e0df16536d3961cfb6e84331c065b4066afb39768d0e319411f7"
deps: misc updates
2020-12-29 20:21:50 +03:00
dependencies = [
"pest",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "serde"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.0.137"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "61ea8d54c77f8315140a05f4c7237403bf38b72704d031543aa1d16abbf517d1"
serde_derive -> serde with derive feature
2020-01-03 20:22:17 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serde_derive",
serde_derive -> serde with derive feature
2020-01-03 20:22:17 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "serde_derive"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.0.137"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "1f26faba0c3959972377d3b2d306ee9f71faee9714294e41bb777f83f88578be"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "serde_json"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "1.0.81"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "9b7ce2b32a1aed03c558dc61a5cd328f15aff2dbc17daad8fb8af04d2100e15c"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
dependencies = [
"itoa",
"ryu",
"serde",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "serde_repr"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.1.8"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "a2ad84e47328a31223de7fed7a4f5087f2d6ddfe586cf3ca25b7a165bc0a5aed"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
dependencies = [
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "serial"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "a1237a96570fc377c13baa1b88c7589ab66edced652e43ffb17088f003db3e86"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serial-core",
"serial-unix",
"serial-windows",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "serial-core"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "3f46209b345401737ae2125fe5b19a77acce90cd53e1658cda928e4fe9a64581"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "serial-unix"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f03fbca4c9d866e24a459cbca71283f545a37f8e3e002ad8c70593871453cab7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"ioctl-rs",
"libc",
"serial-core",
"termios 0.2.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "serial-windows"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "15c6d3b776267a75d31bbdfd5d36c0ca051251caafc285827052bc53bcdc8162"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"serial-core",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "sha-1"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7d94d0bede923b3cea61f3f1ff57ff8cdfd77b400fb8f9998949e0cf04163df"
dependencies = [
"block-buffer 0.7.3",
"digest 0.8.1",
"fake-simd",
"opaque-debug 0.2.3",
]
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
[[package]]
name = "sha1"
cargo update
2022-01-17 04:46:30 +03:00
version = "0.6.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c1da05c97445caa12d05e848c4a4fcbbea29e748ac28f7e80e9b010392063770"
dependencies = [
"sha1_smol",
]
[[package]]
name = "sha1_smol"
version = "1.0.0"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "ae1a47186c03a32177042e55dbc5fd5aee900b8e0069a8d70fba96a9375cd012"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "sha2"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.9.9"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "4d58a1e1bf39749807d89cf2d98ac2dfa0ff1cb3faa38fbb64dd88ac8013d800"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
dependencies = [
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
"block-buffer 0.9.0",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update
2021-05-12 03:03:06 +03:00
"cpufeatures",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
"digest 0.9.0",
"opaque-debug 0.3.0",
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "shared_library"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "5a9e7e0f2bfae24d8a5b5a66c5b257a83c7412304311512a0c054cd5e619da11"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "shell-words"
deps: shell-words -> 1.1.0
2022-02-07 04:32:10 +03:00
version = "1.1.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: shell-words -> 1.1.0
2022-02-07 04:32:10 +03:00
checksum = "24188a676b6ae68c3b2cb3a01be17fbf7240ce009799bb56d5b1409051e78fde"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
introduce quote_dropped_files config option Signed-off-by: Ye Sijun <junnplus@gmail.com>
2022-04-25 09:31:33 +03:00
[[package]]
name = "shlex"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "43b2853a4d09f215c24cc5489c992ce46052d359b5109343cbafbf26bc62f8a3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "signal-hook"
cargo update
2020-12-28 19:23:20 +03:00
version = "0.1.17"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-12-28 19:23:20 +03:00
checksum = "7e31d442c16f047a671b5a71e2161d6e68814012b7f5379d269ebd915fac2729"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"signal-hook-registry",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2021-02-08 09:51:28 +03:00
[[package]]
name = "signal-hook"
deps: update
2021-12-20 18:15:56 +03:00
version = "0.3.13"
cargo update
2021-02-08 09:51:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update
2021-12-20 18:15:56 +03:00
checksum = "647c97df271007dcea485bb74ffdb57f2e683f1306c854f468a0c244badabf2d"
cargo update
2021-02-08 09:51:28 +03:00
dependencies = [
"libc",
"signal-hook-registry",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "signal-hook-registry"
cargo update
2021-06-07 18:32:05 +03:00
version = "1.4.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-07 18:32:05 +03:00
checksum = "e51e73328dc4ac0c7ccbda3a494dfa03df1de2f46018127f60c693f2648455b0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "siphasher"
cargo update
2022-03-09 17:31:53 +03:00
version = "0.3.10"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-03-09 17:31:53 +03:00
checksum = "7bd3e3206899af3f8b12af284fafc038cc1dc2b41d1b89dd17297221c5d225de"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "slab"
cargo update
2022-04-04 04:26:59 +03:00
version = "0.4.6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-04 04:26:59 +03:00
checksum = "eb703cfe953bccee95685111adeedb76fabe4e97549a58d16f03ea7b9367bb32"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "smallvec"
cargo update
2021-01-11 19:43:32 +03:00
version = "0.6.14"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-11 19:43:32 +03:00
checksum = "b97fcaeba89edba30f044a10c6a3cc39df9c3f17d7cd829dd1446cab35f890e0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"maybe-uninit",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "smallvec"
cargo update
2022-01-17 04:46:30 +03:00
version = "1.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "f2dd574626839106c320a323308629dcb1acfc96e32a8cba364ddc61ac23ee83"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
textwrap -> 0.13
2020-12-10 01:07:35 +03:00
[[package]]
name = "smawk"
cargo update
2021-02-01 18:54:01 +03:00
version = "0.3.1"
textwrap -> 0.13
2020-12-10 01:07:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-01 18:54:01 +03:00
checksum = "f67ad224767faa3c7d8b6d91985b78e70a1324408abcb1cfcc2be4c06bc06043"
textwrap -> 0.13
2020-12-10 01:07:35 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "smithay-client-toolkit"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.15.4"
window: update smithay-client-toolkit However, I'm not able to create wayland windows any more on my nvidia system (either with or without this change). I don't know if this is specific to my nvidia drivers or something else :-/ refs: https://github.com/wez/wezterm/issues/476
2020-12-30 22:09:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "8a28f16a97fa0e8ce563b2774d1e732dd5d4025d2772c5dba0a41a0f90a29da3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wayland: update to SCTK 0.14
2021-06-27 03:45:24 +03:00
"dlib",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"log",
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
"memmap2 0.3.1",
cargo update
2022-01-24 08:19:09 +03:00
"nix 0.22.3",
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
"pkg-config",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-client",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"wayland-cursor",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-protocols",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "smol"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.2.5"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "85cf3b5351f3e783c1d79ab5fc604eeed8b8ae9abd36b166e8b87a089efd85e4"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"async-channel",
"async-executor",
"async-fs",
"async-io",
"async-lock",
"async-net",
"async-process",
"blocking",
"futures-lite",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
"once_cell",
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "smol-potat"
version = "1.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "894ffa61af5c0fab697c8c29b1ab10cb6ec4978a1ccac4a81b5b312df1ffd88e"
dependencies = [
"async-io",
"smol-potat-macro",
]
[[package]]
name = "smol-potat-macro"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6b7cd8129a18069385b4eadaa81182b1451fab312ad6f58d1d99253082bf3932"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
cargo update
2021-02-15 23:14:00 +03:00
[[package]]
name = "socket2"
cargo update
2022-05-16 05:44:27 +03:00
version = "0.4.4"
cargo update
2021-02-15 23:14:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "66d72b759436ae32898a2af0a14218dbf55efde3feeb170eb623637db85ee1e0"
cargo update
2021-02-15 23:14:00 +03:00
dependencies = [
"libc",
cargo update
2022-05-16 05:44:27 +03:00
"winapi 0.3.9",
cargo update
2021-02-15 23:14:00 +03:00
]
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
[[package]]
name = "spawn-funcs"
version = "0.1.0"
dependencies = [
"anyhow",
"bstr 0.2.17",
"config",
"luahelper",
"open",
"smol",
"wezterm-dynamic",
fixup win32 build
2022-05-19 19:23:22 +03:00
"winapi 0.3.9",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "spin"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e63cff320ae2c57904679ba7cb63280a3dc4613885beafb148ee7bf9aa9042d"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
[[package]]
cargo update
2021-08-25 20:00:33 +03:00
name = "spin"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "0.9.3"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "c530c2b0d0bf8b69304b39fe2001993e267461948b890cd037d8ad4293fa1a0d"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
dependencies = [
cargo update
2022-04-04 04:26:59 +03:00
"lock_api 0.4.7",
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
]
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
[[package]]
name = "ssh-funcs"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"luahelper",
"wezterm-ssh",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ssh2"
ssh: my openssl+windows ssh2 patch was published upstream So remove my local patch
2021-10-10 17:29:54 +03:00
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "269343e64430067a14937ae0e3c4ec604c178fb896dde0964b1acd22b3e2eeb1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"libssh2-sys",
cargo update
2021-08-30 07:30:03 +03:00
"parking_lot 0.11.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: migrate battery to starship-battery The former is unmaintained and is flagging in cargo audit for its indirect deps. The starship folks have forked it; let's use that. refs: https://github.com/svartalf/rust-battery/pull/92 refs: https://github.com/wez/wezterm/issues/1952
2022-05-05 06:11:48 +03:00
[[package]]
name = "starship-battery"
version = "0.7.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3336198ad004af4447ae69be4f4e562c26814570f8f0c1e37858405a294e015d"
dependencies = [
"cfg-if 1.0.0",
"core-foundation 0.7.0",
"lazycell",
"libc",
"mach",
"nix 0.23.1",
"num-traits",
"uom",
"winapi 0.3.9",
]
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
[[package]]
name = "static_assertions"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2eb9349b6444b326872e140eb1cf5e7c522154d69e7a0ffb0fb81c06b37543f"
move strip-ansi-escapes into its own crate
2020-10-03 09:54:54 +03:00
[[package]]
name = "strip-ansi-escapes"
version = "0.1.0"
dependencies = [
"structopt",
"termwiz",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "strsim"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
lua: give a nice error message when using an invalid field name Make a reasonable suggestion to the user based on similarity with possible field names, but don't error out. This facilitates evolving the configuration over time, and makes the config more forgiving of typos.
2020-03-01 20:39:14 +03:00
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "structopt"
cargo update
2022-01-24 08:19:09 +03:00
version = "0.3.26"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-24 08:19:09 +03:00
checksum = "0c6b5c64445ba8094a6ab0c3cd2ad323e07171012d9c98b0b15651daf1787a10"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"clap",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
"lazy_static",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"structopt-derive",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "structopt-derive"
cargo update
2021-10-25 05:20:45 +03:00
version = "0.4.18"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-10-25 05:20:45 +03:00
checksum = "dcb5ae327f9cc13b68763b5749770cb9e048a99bd9dfdfa58d0cf05d5f64afe0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"heck",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
"proc-macro-error",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
[[package]]
name = "svg_fmt"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8fb1df15f412ee2e9dfc1c504260fa695c1c3f10fe9f4a6ee2d2184d7d6450e2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "syn"
cargo update
2022-05-16 05:44:27 +03:00
version = "1.0.94"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "a07e33e919ebcd69113d5be0e4d70c5707004ff45188910106854f38b960df4a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"unicode-xid",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "tabout"
tabout: bump version for termwiz bump
2020-04-15 18:20:46 +03:00
version = "0.3.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"termwiz",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "takeable-option"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "36ae8932fcfea38b7d3883ae2ab357b0d57a02caaa18ebb4f5ece08beaec4aa0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "tempdir"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "15f2b5fb00ccdf689e0149d1b1b3c03fead81c2b37735d812fa8bddbbf41b6d8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand 0.4.6",
"remove_dir_all",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
[[package]]
name = "tempfile"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "3.3.0"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "5cdb1ef4eaeeaddc8fbd371e5017057064af0911902ef36b39801f67cc6d79e4"
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
dependencies = [
"cfg-if 1.0.0",
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
"fastrand",
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
"libc",
cargo update
2022-04-04 04:26:59 +03:00
"redox_syscall 0.2.13",
update http_req -> 0.8 0.8 doesn't seem to build with rusttls, but I don't think we need that any more: we've been using vendored openssl on windows and mac for some time. closes: #924 refs: https://github.com/jayjamesjay/http_req/issues/48
2021-07-07 23:37:57 +03:00
"remove_dir_all",
"winapi 0.3.9",
]
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "term_size"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1e4129646ca0ed8f45d09b929036bafad5377103edd06e50bf574b353d2b08d9"
dependencies = [
"libc",
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "termcolor"
cargo update
2022-03-09 17:31:53 +03:00
version = "1.1.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-03-09 17:31:53 +03:00
checksum = "bab24d30b911b2376f3a13cc2cd443142f0c81dda04c118693e35b3835757755"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi-util",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "terminfo"
cargo update
2020-05-26 08:25:39 +03:00
version = "0.7.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-26 08:25:39 +03:00
checksum = "76971977e6121664ec1b960d1313aacfa75642adc93b9d4d53b247bd4cb1747e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"dirs",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fnv",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"nom 5.1.2",
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
"phf 0.8.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"phf_codegen",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "termios"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d5d9cf598a6d7ce700a4e6a9199da127e6819a61e64b68609683cc9a01b5683a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "termios"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.3.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "411c5bf740737c7918b8b1fe232dca4dc9f8e754b8ad5e20966814001ed0ac6b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2021-10-11 05:15:00 +03:00
[[package]]
name = "termtree"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.2.4"
cargo update
2021-10-11 05:15:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "507e9898683b6c43a9aa55b64259b721b52ba226e0f3779137e50ad114a4c90b"
cargo update
2021-10-11 05:15:00 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "termwiz"
termwiz: prep for crates.io
2022-04-07 17:27:54 +03:00
version = "0.16.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cassowary",
fix one 32-bit build issue refs: #474
2021-02-12 19:35:00 +03:00
"cfg-if 1.0.0",
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filedescriptor",
"fnv",
termwiz: recognize the XTGETTCAP DCS sequence Parse and respond to this sequence docs can be found https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h4-Device-Control-functions:DCS-plus-q-Pt-ST.F95 refs: https://github.com/wez/wezterm/issues/954
2021-07-25 07:02:54 +03:00
"hex",
move image decoding into termwiz Adds a use_image feature to termwiz that enables an optional dep on the image crate. This in turn allows decoding of animation formats (gif, apng) from file data, but more crucially, allows modeling animation frames at the termwiz layer, which is a pre-req for enabling kitty img protocol animation support. refs: #986
2021-08-03 02:22:55 +03:00
"image",
deps: replace pretty_assertions dep with k9
2022-05-05 04:51:51 +03:00
"k9",
Remove dep on palette for resolving color names Embed rgb.txt and parse it on the fly to produce the list of colors. This list is a superset of palette's SVG color list. refs: https://github.com/wez/wezterm/pull/144
2020-02-07 19:58:53 +03:00
"lazy_static",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"log",
"memmem",
deps: nix -> 0.24
2022-05-05 04:55:56 +03:00
"nix 0.24.1",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"num-derive",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"ordered-float",
move tmux-cc crate to be module inside termwiz refs: #1090
2022-01-17 23:43:35 +03:00
"pest",
"pest_derive",
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10:00 +03:00
"phf 0.10.1",
cargo update
2020-02-11 18:49:05 +03:00
"regex",
deps: misc updates
2020-12-29 20:21:50 +03:00
"semver 0.11.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serde",
termwiz: add ImageData::hash Moves the localized hashing logic from term -> termwiz where it can be re-used. refs: #986
2021-08-02 19:10:36 +03:00
"sha2",
cargo update
2021-02-08 09:51:28 +03:00
"signal-hook 0.1.17",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"terminfo",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"termios 0.3.3",
termwiz: Remove anyhow::Result from public API It's been replaced with an opaque termwiz error type instead. This is a bit of a more conservative approach than that in (refs: #407) and has less of an impact on the surrounding code, which appeals to me from a maintenance perspective. refs: #406 refs: #407
2021-01-08 11:21:54 +03:00
"thiserror",
termwiz: improve performance of emoji presentation lookup
2021-08-12 00:26:57 +03:00
"ucd-trie",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-segmentation",
"varbincode",
"vtparse",
wezterm: add experimental_bidi config option and very basic bidi This commit is larger than it appears to due fanout from threading through bidi parameters. The main changes are: * When clustering cells, add an additional phase to resolve embedding levels and further sub-divide a cluster based on the resolved bidi runs; this is where we get the direction for a run and this needs to be passed through to the shaper. * When doing bidi, the forced cluster boundary hack that we use to de-ligature when cursoring through text needs to be disabled, otherwise the cursor appears to push/rotate the text in that cluster when moving through it! We'll need to find a different way to handle shading the cursor that eliminates the original cursor/ligature/black issue. * In the shaper, the logic for coalescing unresolved runs for font fallback assumed LTR and needed to be adjusted to cluster RTL. That meant also computing a little index of codepoint lengths. * Added `experimental_bidi` boolean option that defaults to false. When enabled, it activates the bidi processing phase in clustering with a strong hint that the paragraph is LTR. This implementation is incomplete and/or wrong for a number of cases: * The config option should probably allow specifying the paragraph direction hint to use by default. * https://terminal-wg.pages.freedesktop.org/bidi/recommendation/paragraphs.html recommends that bidi be applied to logical lines, not physical lines (or really: ranges within physical lines) that we're doing at the moment * The paragraph direction hint should be overridden by cell attributes and other escapes; see 85a6b178cfddee94b3ddb39c26652bbd5a973666 and probably others. However, as of this commit, if you `experimental_bidi=true` then ``` echo This is RTL -> عربي فارسی bidi ``` (that text was sourced from: https://github.com/microsoft/terminal/issues/538#issuecomment-677017322) then wezterm will display the text in the same order as the text renders in Chrome for that github comment. ``` ; ./target/debug/wezterm --config experimental_bidi=false ls-fonts --text "عربي فارسی ->" LeftToRight 0 ع \u{639} x_adv=8 glyph=300 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 2 ر \u{631} x_adv=3.78125 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 4 ب \u{628} x_adv=4 glyph=244 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 6 ي \u{64a} x_adv=4 glyph=363 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 8 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 9 ف \u{641} x_adv=11 glyph=328 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 11 ا \u{627} x_adv=4 glyph=240 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 13 ر \u{631} x_adv=3.78125 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 15 س \u{633} x_adv=10 glyph=278 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 17 ی \u{6cc} x_adv=4 glyph=664 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 19 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 20 - \u{2d} x_adv=8 glyph=276 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 21 > \u{3e} x_adv=8 glyph=338 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs ``` ``` ; ./target/debug/wezterm --config experimental_bidi=true ls-fonts --text "عربي فارسی ->" RightToLeft 17 ی \u{6cc} x_adv=9 glyph=906 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 15 س \u{633} x_adv=10 glyph=277 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 13 ر \u{631} x_adv=4.78125 glyph=272 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 11 ا \u{627} x_adv=4 glyph=241 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 9 ف \u{641} x_adv=5 glyph=329 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 8 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 6 ي \u{64a} x_adv=9 glyph=904 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 4 ب \u{628} x_adv=4 glyph=243 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 2 ر \u{631} x_adv=5 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 0 ع \u{639} x_adv=6 glyph=301 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText LeftToRight 0 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 1 - \u{2d} x_adv=8 glyph=480 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 2 > \u{3e} x_adv=8 glyph=470 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs ; ``` refs: https://github.com/wez/wezterm/issues/784
2022-01-25 18:16:51 +03:00
"wezterm-bidi",
refactor: move color parsing into wezerm-color-types crate Resolves a little bit of the awkward duplication of color types between some of the crates by factoring them a little bit better. This is prep for allowing specifying alpha for some colors in the config.
2022-02-05 23:59:54 +03:00
"wezterm-color-types",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
[[package]]
name = "termwiz-funcs"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"lazy_static",
"luahelper",
"terminfo",
"termwiz",
"unicode-segmentation",
"wezterm-dynamic",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-width",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
[[package]]
name = "textwrap"
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
version = "0.15.0"
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
checksum = "b1141d4d61095b28419e22cb0bbf02755f5e54e0526f97f1e3d1d160e60885fb"
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
dependencies = [
textwrap -> 0.13
2020-12-10 01:07:35 +03:00
"smawk",
cargo update
2021-06-07 18:32:05 +03:00
"unicode-linebreak",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"unicode-width",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "thiserror"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.0.31"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "bd829fe32373d27f76265620b5309d0340cb8550f523c1dda251d6298069069a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"thiserror-impl",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "thiserror-impl"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.0.31"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "0396bc89e626244658bef819e22d0cc459e795a5ebe878e6ec336d1674a8d79a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
[[package]]
name = "thread_local"
cargo update
2022-01-24 08:19:09 +03:00
version = "1.1.4"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-24 08:19:09 +03:00
checksum = "5516c27b78311c50bf42c071425c560ac799b11c30b31f87e3081965fe5e0180"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
dependencies = [
"once_cell",
]
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "threadpool"
version = "1.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d050e60b33d41c19108b32cea32164033a9013fe3b46cbd4457559bfbf77afaa"
dependencies = [
"num_cpus",
]
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "tiff"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "0.7.2"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "7cfada0986f446a770eca461e8c6566cb879682f7d687c8348aa0c857bd52286"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
dependencies = [
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"flate2",
deps: cargo update
2022-04-19 06:51:19 +03:00
"jpeg-decoder",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"weezl",
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "time"
cargo update
2021-01-11 19:43:32 +03:00
version = "0.1.43"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-11 19:43:32 +03:00
checksum = "ca8a50ef2360fbd1eeb0ecd46795a87a19024eb4b53c5dc916ca1fd95fe62438"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
[[package]]
name = "time"
version = "0.3.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c2702e08a7a860f005826c6815dcac101b19b5eb330c27fe4a5928fec1d20ddd"
dependencies = [
"libc",
"num_threads",
]
zeno -> tiny_skia Mostly so that we can turn off anti-aliasing for smaller sizes, but it also happens to be more complete anyway.
2021-06-26 08:55:42 +03:00
[[package]]
name = "tiny-skia"
deps: cargo update
2022-02-06 17:46:12 +03:00
version = "0.6.3"
zeno -> tiny_skia Mostly so that we can turn off anti-aliasing for smaller sizes, but it also happens to be more complete anyway.
2021-06-26 08:55:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-02-06 17:46:12 +03:00
checksum = "1bcfd4339bdd4545eabed74b208f2f1555f2e6540fb58135c01f46c0940aa138"
zeno -> tiny_skia Mostly so that we can turn off anti-aliasing for smaller sizes, but it also happens to be more complete anyway.
2021-06-26 08:55:42 +03:00
dependencies = [
"arrayref",
"arrayvec",
"bytemuck",
"cfg-if 1.0.0",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"png",
zeno -> tiny_skia Mostly so that we can turn off anti-aliasing for smaller sizes, but it also happens to be more complete anyway.
2021-06-26 08:55:42 +03:00
"safe_arch",
]
wezterm: update allsorts shaper The current master of allsorts supports color fonts in both bitmap and svg varieties. I'm interested to see if I can teach wezterm to render the svg based variety in a subsequent diff. First though, it's times to dust off our allsorts shaper logic. This commit updates to point to the current master of allsorts at the time of writing; there's a little bit of API fanout that makes it a bit easier to manage font fallback. The fallback logic has been improved so that we can now successfully fall back to the emoji font. The shaping logic has been improved so that we turn on the options that enable ZWJ for combining sequences of emoji, such as "man health worker". Running with the allsorts shaper enabled produces generally superior emoji/ligature substitution results compared to harfbuzz with Noto Color Emoji; the "man health worker" and the flags (eg: `flag: England`) from the subdivsion-flag section don't get substituted at all with harfbuzz, but do produce appropriate glyphs with allsorts. refs: https://github.com/wez/wezterm/issues/66
2020-11-21 03:56:07 +03:00
[[package]]
name = "tinyvec"
cargo update
2022-05-02 07:21:14 +03:00
version = "1.6.0"
wezterm: update allsorts shaper The current master of allsorts supports color fonts in both bitmap and svg varieties. I'm interested to see if I can teach wezterm to render the svg based variety in a subsequent diff. First though, it's times to dust off our allsorts shaper logic. This commit updates to point to the current master of allsorts at the time of writing; there's a little bit of API fanout that makes it a bit easier to manage font fallback. The fallback logic has been improved so that we can now successfully fall back to the emoji font. The shaping logic has been improved so that we turn on the options that enable ZWJ for combining sequences of emoji, such as "man health worker". Running with the allsorts shaper enabled produces generally superior emoji/ligature substitution results compared to harfbuzz with Noto Color Emoji; the "man health worker" and the flags (eg: `flag: England`) from the subdivsion-flag section don't get substituted at all with harfbuzz, but do produce appropriate glyphs with allsorts. refs: https://github.com/wez/wezterm/issues/66
2020-11-21 03:56:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "87cc5ceb3875bb20c2890005a4e226a4651264a5c75edb2421b52861a0a0cb50"
wezterm: update allsorts shaper The current master of allsorts supports color fonts in both bitmap and svg varieties. I'm interested to see if I can teach wezterm to render the svg based variety in a subsequent diff. First though, it's times to dust off our allsorts shaper logic. This commit updates to point to the current master of allsorts at the time of writing; there's a little bit of API fanout that makes it a bit easier to manage font fallback. The fallback logic has been improved so that we can now successfully fall back to the emoji font. The shaping logic has been improved so that we turn on the options that enable ZWJ for combining sequences of emoji, such as "man health worker". Running with the allsorts shaper enabled produces generally superior emoji/ligature substitution results compared to harfbuzz with Noto Color Emoji; the "man health worker" and the flags (eg: `flag: England`) from the subdivsion-flag section don't get substituted at all with harfbuzz, but do produce appropriate glyphs with allsorts. refs: https://github.com/wez/wezterm/issues/66
2020-11-21 03:56:07 +03:00
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cda74da7e1a664f795bb1f8a87ec406fb89a02522cf6e50620d016add6dbbf5c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "toml"
deps: cargo update
2022-04-19 06:51:19 +03:00
version = "0.5.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-19 06:51:19 +03:00
checksum = "8d82e1a7758622a465f8cee077614c73484dac5b836c02ff6a40d5d1010324d7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serde",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "typenum"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
version = "1.15.0"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
checksum = "dcf81ac59edc17cc8697ff311e8f5ef2d99fcbd9817b34cec66f90b6c3dfd987"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "ucd-trie"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56dee185309b50d1f11bfedef0fe6d036842e3fb77413abef29f8f8d1c5d4c1c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "uds_windows"
deps: update
2021-12-20 18:15:56 +03:00
version = "1.0.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update
2021-12-20 18:15:56 +03:00
checksum = "486992108df0fe0160680af1941fe856c521be931d5a5ecccefe0de86dc47e4a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"tempdir",
cargo update
2021-02-04 10:28:23 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
[[package]]
name = "umask"
version = "0.1.0"
dependencies = [
Take care to restore the original umask wezterm sets a more restrictive umask (`0o077`) by default so that any files that it creates (eg: unix domain socket, log files) are more secure by default. However, some environments rely on the more general default of (`0o022`) without checking that it is set. This matters because programs spawned by wezterm inherit its more restricted umask. I hadn't noticed this because I've had `umask 022` in my shell RC files since sometime in the 1990's. This commit adds some plumbing to the pty layer to specify an optional umask for the child process, and some more to our umask saver helper so that any thread can determine the saved umask without needing a reference to the saver itself, which may be in a different crate. The logic in the config crate has been adjusted to connect the saved value to the default command builder arguments. The net result of this is that running `wezterm -n start bash -- --norc` and typing `umask` in the resultant window now prints `0022`. refs: #416
2021-01-07 20:14:51 +03:00
"lazy_static",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"libc",
]
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "unicase"
version = "2.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "50f37be617794602aabbeee0be4f259dc1778fabe05e2d67ee8f79326d5cb4f6"
dependencies = [
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"version_check",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
]
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "unicode-bidi"
cargo update
2022-05-02 07:21:14 +03:00
version = "0.3.8"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "099b7128301d285f79ddd55b9a83d5e6b9e97c92e0ea0daebee7263e932de992"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
cargo update
2021-06-07 18:32:05 +03:00
[[package]]
name = "unicode-linebreak"
deps: cargo update
2021-07-26 18:16:03 +03:00
version = "0.1.2"
cargo update
2021-06-07 18:32:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2021-07-26 18:16:03 +03:00
checksum = "3a52dcaab0c48d931f7cc8ef826fa51690a08e1ea55117ef26f89864f532383f"
cargo update
2021-06-07 18:32:05 +03:00
dependencies = [
"regex",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "unicode-normalization"
cargo update
2021-06-07 18:32:05 +03:00
version = "0.1.19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-07 18:32:05 +03:00
checksum = "d54590932941a9e9266f0832deed84ebe1bf2e4c9e4a3554d393d18f5e854bf9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"tinyvec",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "unicode-segmentation"
cargo update
2022-02-14 06:31:40 +03:00
version = "1.9.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-14 06:31:40 +03:00
checksum = "7e8820f5d777f6224dc4be3632222971ac30164d4a258d595640799554ebfd99"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "unicode-width"
cargo update
2021-09-20 04:21:46 +03:00
version = "0.1.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-09-20 04:21:46 +03:00
checksum = "3ed742d4ea2bd1176e236172c8429aaf54486e7ac098db29ffe6529e0ce50973"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "unicode-xid"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "0.2.3"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "957e51f3646910546462e67d5f7599b9e4fb8acdd304b087a6494730f9eebf04"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "untrusted"
cargo update
2020-05-02 22:13:10 +03:00
version = "0.7.1"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-02 22:13:10 +03:00
checksum = "a156c684c91ea7d62626509bce3cb4e1d9ed5c4d978f7b4352658f96a4c26b4a"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
[[package]]
name = "uom"
version = "0.30.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e76503e636584f1e10b9b3b9498538279561adcef5412927ba00c2b32c4ce5ed"
dependencies = [
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
"typenum",
]
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "url"
cargo update
2021-05-12 03:03:06 +03:00
version = "2.2.2"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-12 03:03:06 +03:00
checksum = "a507c383b2d33b5fc35d1861e77e6b383d158b2da5e14fe51b83dfedf6fd578c"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"form_urlencoded",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"idna",
"matches",
"percent-encoding",
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "utf8parse"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.2.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "936e4b492acfd135421d8dca4b1aa80a7bfc26e702ef3af710e0752684df5372"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2021-02-01 18:54:01 +03:00
[[package]]
name = "value-bag"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
version = "1.0.0-alpha.9"
cargo update
2021-02-01 18:54:01 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
checksum = "2209b78d1249f7e6f3293657c9779fe31ced465df091bbd433a1cf88e916ec55"
cargo update
2021-02-01 18:54:01 +03:00
dependencies = [
"ctor",
cargo update
2021-05-17 17:28:56 +03:00
"version_check",
cargo update
2021-02-01 18:54:01 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "varbincode"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "b712fa900b441e2d5226a094ca37ca70c0d26d26b79822a5cf34a853a9e26f9f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"byteorder",
"leb128",
"serde",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "vcpkg"
cargo update
2021-06-21 05:06:54 +03:00
version = "0.2.15"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-21 05:06:54 +03:00
checksum = "accd4ea62f7bb7a82fe23066fb0957d48ef677f6eeb8215f372f52e48bb32426"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "vec_map"
cargo update
2020-05-26 08:25:39 +03:00
version = "0.8.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-26 08:25:39 +03:00
checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2020-03-14 19:39:38 +03:00
[[package]]
name = "version_check"
cargo update
2022-01-03 05:48:38 +03:00
version = "0.9.4"
cargo update
2020-03-14 19:39:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-03 05:48:38 +03:00
checksum = "49874b5167b65d7193b8aba1567f5c7d93d001cafc34600cee003eda787e483f"
cargo update
2020-03-14 19:39:38 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "vswhom"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "be979b7f07507105799e854203b470ff7c78a1639e330a58f183b5fea574608b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"vswhom-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "vswhom-sys"
cargo update
2022-02-22 05:44:27 +03:00
version = "0.1.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-02-22 05:44:27 +03:00
checksum = "22025f6d8eb903ebf920ea6933b70b1e495be37e2cb4099e62c80454aaf57c39"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "vtparse"
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
version = "0.6.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: replace pretty_assertions dep with k9
2022-05-05 04:51:51 +03:00
"k9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"utf8parse",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "waker-fn"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.1.0"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "9d5b2c62b4012a3e1eca5a7e077d13b3bf498c4073e33ccd58626607748ceeca"
cargo update
2020-06-30 03:52:14 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "walkdir"
cargo update
2021-03-25 20:08:03 +03:00
version = "2.3.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-25 20:08:03 +03:00
checksum = "808cf2735cd4b6866113f648b791c6adc5714537bc222d9347bb203386ffda56"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"same-file",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi-util",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "wasi"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.9.0+wasi-snapshot-preview1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "wasi"
cargo update
2021-02-01 18:54:01 +03:00
version = "0.10.2+wasi-snapshot-preview1"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-01 18:54:01 +03:00
checksum = "fd6fbd9a79829dd1ad0cc20627bf1ed606756a7f77edff7b66b7064f9cb327c6"
cargo update
2020-09-09 19:31:37 +03:00
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
[[package]]
name = "wasi"
version = "0.11.0+wasi-snapshot-preview1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9c8d87e72b64a3b4db28d11ce29237c246188f4f51057d65a7eab63b7987e423"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "wasm-bindgen"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.2.80"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "27370197c907c55e3f1a9fbe26f44e937fe6451368324e009cba39e139dc08ad"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.2.80"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "53e04185bfa3a779273da532f5025e33398409573f348985af9a1cbf3774d3f4"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"bumpalo",
"lazy_static",
"log",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"wasm-bindgen-shared",
]
cargo update
2020-05-26 08:25:39 +03:00
[[package]]
name = "wasm-bindgen-futures"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.4.30"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "6f741de44b75e14c35df886aff5f1eb73aa114fa5d4d00dcd37b5e01259bf3b2"
cargo update
2020-05-26 08:25:39 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update
2020-05-26 08:25:39 +03:00
"js-sys",
"wasm-bindgen",
"web-sys",
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "wasm-bindgen-macro"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.2.80"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "17cae7ff784d7e83a2fe7611cfe766ecf034111b49deb850a3dc7699c08251f5"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"wasm-bindgen-macro-support",
]
[[package]]
name = "wasm-bindgen-macro-support"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.2.80"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "99ec0dc7a4756fffc231aab1b9f2f578d23cd391390ab27f952ae0c9b3ece20b"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.2.80"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "d554b7f530dee5964d9a9468d95c1f8b8acae4f282807e7d27d4b03099a46744"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "wayland-client"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.29.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "91223460e73257f697d9e23d401279123d36039a3f7a449e983f123292d4458f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"downcast-rs",
"libc",
cargo update
2022-01-24 08:19:09 +03:00
"nix 0.22.3",
cargo update
2020-09-09 19:31:37 +03:00
"scoped-tls",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-commons",
"wayland-scanner",
"wayland-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "wayland-commons"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.29.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "94f6e5e340d7c13490eca867898c4cec5af56c27a5ffe5c80c6fc4708e22d33e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2022-01-24 08:19:09 +03:00
"nix 0.22.3",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"once_cell",
cargo update
2022-01-17 04:46:30 +03:00
"smallvec 1.8.0",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"wayland-sys",
]
[[package]]
name = "wayland-cursor"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.29.4"
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "c52758f13d5e7861fc83d942d3d99bf270c83269575e52ac29e5b73cb956a6bd"
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
dependencies = [
cargo update
2022-01-24 08:19:09 +03:00
"nix 0.22.3",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"wayland-client",
"xcursor",
]
[[package]]
name = "wayland-egl"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.29.4"
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "83281d69ee162b59031c666385e93bde4039ec553b90c4191cdb128ceea29a3a"
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
dependencies = [
"wayland-client",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "wayland-protocols"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.29.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "60147ae23303402e41fe034f74fb2c35ad0780ee88a1c40ac09a3be1e7465741"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-client",
"wayland-commons",
"wayland-scanner",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "wayland-scanner"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.29.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "39a1ed3143f7a143187156a2ab52742e89dac33245ba505c17224df48939f9e0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"xml-rs",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "wayland-sys"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
version = "0.29.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
checksum = "d9341df79a8975679188e37dab3889bfa57c44ac2cb6da166f519a81cbe452d4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
wayland: update to SCTK 0.14
2021-06-27 03:45:24 +03:00
"dlib",
window: update smithay-client-toolkit However, I'm not able to create wayland windows any more on my nvidia system (either with or without this change). I don't know if this is specific to my nvidia drivers or something else :-/ refs: https://github.com/wez/wezterm/issues/476
2020-12-30 22:09:21 +03:00
"pkg-config",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "web-sys"
cargo update
2022-04-11 04:32:03 +03:00
version = "0.3.57"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-04-11 04:32:03 +03:00
checksum = "7b17e741662c70c8bd24ac5c5b18de314a2c26c32bf8346ee1e6f53de919c283"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"js-sys",
"wasm-bindgen",
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "weezl"
deps: cargo update
2022-04-25 02:41:29 +03:00
version = "0.1.6"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-04-25 02:41:29 +03:00
checksum = "9c97e489d8f836838d497091de568cf16b117486d529ec5579233521065bd5e4"
cargo update
2020-10-02 17:16:20 +03:00
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
cargo update
2021-06-21 05:06:54 +03:00
name = "wepoll-ffi"
version = "0.1.2"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-06-21 05:06:54 +03:00
checksum = "d743fdedc5c64377b5fc2bc036b01c7fd642205a0d96356034ae3404d49eb7fb"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"cc",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
move strip-ansi-escapes into its own crate
2020-10-03 09:54:54 +03:00
name = "wezterm"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
mux: track list of clients Define a way to compute a client ID and pass that through to the mux server when verifying version compatibility. Once associated, the session handler will keep some metadata updated in the mux. A new cli subcommand exposes the info: ``` ; ./target/debug/wezterm cli list-clients USER HOST PID CONNECTED IDLE WORKSPACE wez mba.localdomain 52979 30.009225s 1.009225s ``` refs: #1531
2022-01-12 08:39:19 +03:00
"chrono",
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
"codec",
"config",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
"env-bootstrap",
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
"filedescriptor",
wezterm: add `wezterm set-working-directory` This command formats an OSC 7 escape sequence to inform the terminal of the working directory. It has two optional arguments: * The hostname - if unspecified the hostname of the system will be used * The working directory - if unspecified the working directory of the process will be used This command formats the hostname and working directory into a `file://` URL and emits an OSC 7 escape sequence. The intent of this is to make it a bit easier to produce shell integration scripts for various shell environments without trying to implement URL encoding in eg: bash.
2020-11-13 20:24:16 +03:00
"hostname",
Add `wezterm record` and `wezterm replay` subcommands These are intended to replace the `wt-record` and `wt-replay` scripts that are primarily for me to diagnose wezterm issues. The thinking is that this gives a cross platform implementation of this functionality and squashes out some of the pain of dealing with different versions and file formats. The new subcommands use the asciicast v2 file format, meaning that wezterm can record for asciicast/asciinema and vice-versa. This commit only handles unix; windows support will follow in a separate commit.
2022-03-25 08:23:13 +03:00
"libc",
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
"log",
"mux",
"portable-pty",
"promise",
Add `wezterm record` and `wezterm replay` subcommands These are intended to replace the `wt-record` and `wt-replay` scripts that are primarily for me to diagnose wezterm issues. The thinking is that this gives a cross platform implementation of this functionality and squashes out some of the pain of dealing with different versions and file formats. The new subcommands use the asciicast v2 file format, meaning that wezterm can record for asciicast/asciinema and vice-versa. This commit only handles unix; windows support will follow in a separate commit.
2022-03-25 08:23:13 +03:00
"serde",
"serde_json",
record: add more metadata, change filename suffix to .txt The metadata is useful from a troubleshooting/diagnostic perspective. `.cast` isn't on github's list of allowed file name suffixes, so make it a simple text file for convenience.
2022-03-25 19:46:24 +03:00
"shell-words",
fix: cli proxy would terminate too soon refs: https://github.com/wez/wezterm/issues/507
2021-03-28 17:10:30 +03:00
"smol",
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
"structopt",
"tabout",
Add `wezterm record` and `wezterm replay` subcommands These are intended to replace the `wt-record` and `wt-replay` scripts that are primarily for me to diagnose wezterm issues. The thinking is that this gives a cross platform implementation of this functionality and squashes out some of the pain of dealing with different versions and file formats. The new subcommands use the asciicast v2 file format, meaning that wezterm can record for asciicast/asciinema and vice-versa. This commit only handles unix; windows support will follow in a separate commit.
2022-03-25 08:23:13 +03:00
"tempfile",
"termios 0.3.3",
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
"termwiz",
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
"textwrap 0.15.0",
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
"umask",
wezterm: add `wezterm set-working-directory` This command formats an OSC 7 escape sequence to inform the terminal of the working directory. It has two optional arguments: * The hostname - if unspecified the hostname of the system will be used * The working directory - if unspecified the working directory of the process will be used This command formats the hostname and working directory into a `file://` URL and emits an OSC 7 escape sequence. The intent of this is to make it a bit easier to produce shell integration scripts for various shell environments without trying to implement URL encoding in eg: bash.
2020-11-13 20:24:16 +03:00
"url",
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
"wezterm-client",
"wezterm-gui-subcommands",
"wezterm-term",
record: add support for running on Windows
2022-03-25 18:37:38 +03:00
"winapi 0.3.9",
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
]
Add wezterm-bidi crate In order to support RTL/BIDI, wezterm needs a bidi implementation. I don't think a well-conforming rust implementation exists today; what I found were implementations that didn't pass 100% of the conformance tests. So I decided to port "bidiref", the reference implementation of the UBA described in http://unicode.org/reports/tr9/ to Rust. This implementation focuses on conformance: no special measures have been taken to optimize it so far, with my focus having been to ensure that all of the approx 780,000 test cases in the unicode data for unicode 14 pass. Having the tests passing 100% allows for making performance improvements with confidence in the future. The API isn't completely designed/fully baked. Until I get to hooking it up to wezterm's shaper, I'm not 100% sure exactly what I'll need. There's a good discussion on API in https://github.com/open-i18n/rust-unic/issues/273 that suggests omitting "legacy" operations such as reordering. I suspect that wezterm may actually need that function to support monospace text layout in some terminal scenarios, but regardless: reordering is part of the conformance test suite so it remains a part of the API. That said: the API does model the major operations as separate phases, so you should be able to pay for just what you use: * Resolving the embedding levels from a paragraph * Returning paragraph runs of those levels (and their directions) * Returning the whitespace-level-reset runs for a line-slice within the paragraph * Returning the reordered indices + levels for a line-slice within the paragraph. refs: https://github.com/wez/wezterm/issues/784 refs: https://github.com/kas-gui/kas-text/issues/20
2022-01-21 18:42:44 +03:00
[[package]]
name = "wezterm-bidi"
version = "0.1.0"
dependencies = [
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
Add wezterm-bidi crate In order to support RTL/BIDI, wezterm needs a bidi implementation. I don't think a well-conforming rust implementation exists today; what I found were implementations that didn't pass 100% of the conformance tests. So I decided to port "bidiref", the reference implementation of the UBA described in http://unicode.org/reports/tr9/ to Rust. This implementation focuses on conformance: no special measures have been taken to optimize it so far, with my focus having been to ensure that all of the approx 780,000 test cases in the unicode data for unicode 14 pass. Having the tests passing 100% allows for making performance improvements with confidence in the future. The API isn't completely designed/fully baked. Until I get to hooking it up to wezterm's shaper, I'm not 100% sure exactly what I'll need. There's a good discussion on API in https://github.com/open-i18n/rust-unic/issues/273 that suggests omitting "legacy" operations such as reordering. I suspect that wezterm may actually need that function to support monospace text layout in some terminal scenarios, but regardless: reordering is part of the conformance test suite so it remains a part of the API. That said: the API does model the major operations as separate phases, so you should be able to pay for just what you use: * Resolving the embedding levels from a paragraph * Returning paragraph runs of those levels (and their directions) * Returning the whitespace-level-reset runs for a line-slice within the paragraph * Returning the reordered indices + levels for a line-slice within the paragraph. refs: https://github.com/wez/wezterm/issues/784 refs: https://github.com/kas-gui/kas-text/issues/20
2022-01-21 18:42:44 +03:00
"k9",
"log",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
Add wezterm-bidi crate In order to support RTL/BIDI, wezterm needs a bidi implementation. I don't think a well-conforming rust implementation exists today; what I found were implementations that didn't pass 100% of the conformance tests. So I decided to port "bidiref", the reference implementation of the UBA described in http://unicode.org/reports/tr9/ to Rust. This implementation focuses on conformance: no special measures have been taken to optimize it so far, with my focus having been to ensure that all of the approx 780,000 test cases in the unicode data for unicode 14 pass. Having the tests passing 100% allows for making performance improvements with confidence in the future. The API isn't completely designed/fully baked. Until I get to hooking it up to wezterm's shaper, I'm not 100% sure exactly what I'll need. There's a good discussion on API in https://github.com/open-i18n/rust-unic/issues/273 that suggests omitting "legacy" operations such as reordering. I suspect that wezterm may actually need that function to support monospace text layout in some terminal scenarios, but regardless: reordering is part of the conformance test suite so it remains a part of the API. That said: the API does model the major operations as separate phases, so you should be able to pay for just what you use: * Resolving the embedding levels from a paragraph * Returning paragraph runs of those levels (and their directions) * Returning the whitespace-level-reset runs for a line-slice within the paragraph * Returning the reordered indices + levels for a line-slice within the paragraph. refs: https://github.com/wez/wezterm/issues/784 refs: https://github.com/kas-gui/kas-text/issues/20
2022-01-21 18:42:44 +03:00
]
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
[[package]]
name = "wezterm-client"
version = "0.1.0"
dependencies = [
"anyhow",
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
"async-trait",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"async_ossl",
move codec into is own crate
2020-10-03 08:39:15 +03:00
"codec",
move config into its own crate
2020-10-02 21:50:50 +03:00
"config",
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
"filedescriptor",
"futures",
multiplexer: improve handling of image attachments There were a a couple of issues: * `ImageData::hash` would re-hash the image on every call, and this was called for every cell that comprised an image on the mux server side * `SerializedLine` needed to understand how to remove the `Arc<ImageData>` image attachments so that we didn't serialize a complete copy of the image per cell that comprised the image. A new RPC was introduced to attempt to fetch `ImageData` given its content hash and pane, row and cell index as a hint to locate it. A client side LRU of content hash to `ImageData` is used to avoid issuing repeat calls to that new RPC. refs: #1237
2022-03-29 06:21:37 +03:00
"lazy_static",
thread original umask through when spawning mux server refs: #1633
2022-02-11 20:00:09 +03:00
"libc",
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
"log",
"lru",
"metrics",
"mux",
"openssl",
"portable-pty",
"promise",
"rangeset",
"ratelim",
"smol",
"termwiz",
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
"textwrap 0.15.0",
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
"thiserror",
wezterm: fixup win32 build for wezterm-gui changes refs: #301
2020-10-25 03:00:07 +03:00
"uds_windows",
thread original umask through when spawning mux server refs: #1633
2022-02-11 20:00:09 +03:00
"umask",
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
"url",
wezterm-client: cut over to new wezterm-ssh bits refs: https://github.com/wez/wezterm/issues/507
2021-03-28 17:11:14 +03:00
"wezterm-ssh",
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
"wezterm-term",
gui/client: add stubs for publishing a main gui instance sock path This will help to route things through a main gui instance per desktop session/class. Currently has stubs for windows.
2022-01-07 06:07:46 +03:00
"winapi 0.3.9",
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
]
refactor: move color parsing into wezerm-color-types crate Resolves a little bit of the awkward duplication of color types between some of the crates by factoring them a little bit better. This is prep for allowing specifying alpha for some colors in the config.
2022-02-05 23:59:54 +03:00
[[package]]
name = "wezterm-color-types"
version = "0.1.0"
dependencies = [
allow using CSS style color specs in the config This change also allows removing the dep on the palette crate, which I found to be difficult to use (API changed often, and relied on a lot of `.into` that was hard to follow and reconcile across upgrades). We already pulled in the csscolorparse crate as an indirect dep of colorgrad, so we can replace the color conversion we need for sixel with that crate while we're in here. refs: #1615
2022-02-06 18:20:56 +03:00
"csscolorparser",
refactor: move color parsing into wezerm-color-types crate Resolves a little bit of the awkward duplication of color types between some of the crates by factoring them a little bit better. This is prep for allowing specifying alpha for some colors in the config.
2022-02-05 23:59:54 +03:00
"lazy_static",
allow setting selection colors with alpha values This commit allows the following configuration: ``` wezterm -n --config 'colors = { selection_fg = "clear", selection_bg = "rgba:50% 50% 50% 50%" }' ``` which sets the selection_bg to fully transparent, and selection_bg to 50% transparent gray. When selection_fg is fully transparent we'll use the normal fg color. When selection_bg is partially (or fully!) transparent, it will be alpha blended over the current cell background color. To support this, the config file will now accept rgba colors specified as 4 whitespace delimited numeric values. If a value ends with `%` it is interpreted as a number in the range 0-100. Otherwise, it is interpreted as a number in the range 0-255. The 4 values are red, green, blue, alpha. At this time, only the selection_fg and selection_bg settings accept alpha values. refs: #1615
2022-02-06 01:13:19 +03:00
"serde",
refactor: move color parsing into wezerm-color-types crate Resolves a little bit of the awkward duplication of color types between some of the crates by factoring them a little bit better. This is prep for allowing specifying alpha for some colors in the config.
2022-02-05 23:59:54 +03:00
]
add wezterm-dynamic crate
2022-05-11 18:19:00 +03:00
[[package]]
name = "wezterm-dynamic"
version = "0.1.0"
dependencies = [
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"log",
add wezterm-dynamic crate
2022-05-11 18:19:00 +03:00
"maplit",
"ordered-float",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"strsim 0.10.0",
add wezterm-dynamic crate
2022-05-11 18:19:00 +03:00
"thiserror",
"wezterm-dynamic-derive",
]
[[package]]
name = "wezterm-dynamic-derive"
version = "0.1.0"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
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
[[package]]
name = "wezterm-font"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
cargo update
2022-02-14 06:31:40 +03:00
"core-foundation 0.9.3",
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
"core-text",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"dwrote",
fonts: improve font name decoding freetype can't handle a wide range of encodings for font names and can return strings like `?????` when the family name is only present in the font as a non-unicode encoding, such as Chinese. This commit improves our handling of the font name table and prefers to use results from processing that over the results returned for eg: font family directly from the freetype API. refs: https://github.com/wez/wezterm/issues/1761
2022-03-26 09:27:27 +03:00
"encoding_rs",
Add `wezterm ls-fonts` subcommand At this time it just shows you the fonts that your config matches and where they came from: ``` ; wezterm -n ls-fonts Primary font: wezterm.font("JetBrains Mono", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/JetBrainsMono-Regular.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/usr/share/fonts/google-noto-emoji/NotoColorEmoji.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/NotoColorEmoji.ttf, FontConfig) wezterm.font("Last Resort High-Efficiency", weight="Regular", stretch="Normal", italic=false) (<built-in>, BuiltIn) When Italic=true: wezterm.font("JetBrains Mono", weight="Regular", stretch="Normal", italic=true) (/home/wez/.fonts/JetBrainsMono-Italic.ttf, FontConfig) wezterm.font("JetBrains Mono", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/JetBrainsMono-Regular.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/usr/share/fonts/google-noto-emoji/NotoColorEmoji.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/NotoColorEmoji.ttf, FontConfig) wezterm.font("Last Resort High-Efficiency", weight="Regular", stretch="Normal", italic=false) (<built-in>, BuiltIn) When Intensity=Bold: wezterm.font("JetBrains Mono", weight="Bold", stretch="Normal", italic=false) (/home/wez/.fonts/JetBrainsMono-Bold.ttf, FontConfig) wezterm.font("JetBrains Mono", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/JetBrainsMono-Regular.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/usr/share/fonts/google-noto-emoji/NotoColorEmoji.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/NotoColorEmoji.ttf, FontConfig) wezterm.font("Last Resort High-Efficiency", weight="Regular", stretch="Normal", italic=false) (<built-in>, BuiltIn) When Intensity=Bold Italic=true: wezterm.font("JetBrains Mono", weight="Bold", stretch="Normal", italic=true) (/home/wez/.fonts/JetBrainsMono-Bold-Italic.ttf, FontConfig) wezterm.font("JetBrains Mono", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/JetBrainsMono-Regular.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/usr/share/fonts/google-noto-emoji/NotoColorEmoji.ttf, FontConfig) wezterm.font("Noto Color Emoji", weight="Regular", stretch="Normal", italic=false) (/home/wez/.fonts/NotoColorEmoji.ttf, FontConfig) wezterm.font("Last Resort High-Efficiency", weight="Regular", stretch="Normal", italic=false) (<built-in>, BuiltIn) ``` refs: #347
2021-04-12 19:36:56 +03:00
"enum-display-derive",
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fontconfig",
wezterm-font: remove font-kit dep This wasn't used by anything and the version was getting pretty stale. Upgrading is awkward because newer versions pull in an incompatible freetype library version.
2020-10-25 08:01:00 +03:00
"freetype",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"harfbuzz",
Add shaper post-processing function This function is intended to deal with certain kinds of ligatures and certain combining sequences that don't have corresponding glyphs. It isn't hooked up to the gui yet, but does have unit tests that are probably mostly correct. refs: https://github.com/wez/wezterm/issues/478
2021-02-22 20:19:05 +03:00
"k9",
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",
"log",
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
"memmap2 0.2.3",
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
"metrics",
wezterm-font: cache metrics lookup in harfbuzz shaper 98f289f511c8f819b6c81dfee6dfa192ed794973 causes more metrics retrieval than in earlier versions; each unchached glyph render would trigger a metrics recompute for the relevant font. Add a simple cache for this. refs: #353
2020-11-25 05:19:49 +03:00
"ordered-float",
wezterm-font: introduce FontDatabase This tidies up the font-dir and built-in font management a little bit and paves the way for codepoint -> font resolution for fonts discovered in font-dirs.
2020-11-26 06:15:08 +03:00
"rangeset",
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
"termwiz",
"thiserror",
"unicode-segmentation",
"walkdir",
wezterm: add experimental_bidi config option and very basic bidi This commit is larger than it appears to due fanout from threading through bidi parameters. The main changes are: * When clustering cells, add an additional phase to resolve embedding levels and further sub-divide a cluster based on the resolved bidi runs; this is where we get the direction for a run and this needs to be passed through to the shaper. * When doing bidi, the forced cluster boundary hack that we use to de-ligature when cursoring through text needs to be disabled, otherwise the cursor appears to push/rotate the text in that cluster when moving through it! We'll need to find a different way to handle shading the cursor that eliminates the original cursor/ligature/black issue. * In the shaper, the logic for coalescing unresolved runs for font fallback assumed LTR and needed to be adjusted to cluster RTL. That meant also computing a little index of codepoint lengths. * Added `experimental_bidi` boolean option that defaults to false. When enabled, it activates the bidi processing phase in clustering with a strong hint that the paragraph is LTR. This implementation is incomplete and/or wrong for a number of cases: * The config option should probably allow specifying the paragraph direction hint to use by default. * https://terminal-wg.pages.freedesktop.org/bidi/recommendation/paragraphs.html recommends that bidi be applied to logical lines, not physical lines (or really: ranges within physical lines) that we're doing at the moment * The paragraph direction hint should be overridden by cell attributes and other escapes; see 85a6b178cfddee94b3ddb39c26652bbd5a973666 and probably others. However, as of this commit, if you `experimental_bidi=true` then ``` echo This is RTL -> عربي فارسی bidi ``` (that text was sourced from: https://github.com/microsoft/terminal/issues/538#issuecomment-677017322) then wezterm will display the text in the same order as the text renders in Chrome for that github comment. ``` ; ./target/debug/wezterm --config experimental_bidi=false ls-fonts --text "عربي فارسی ->" LeftToRight 0 ع \u{639} x_adv=8 glyph=300 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 2 ر \u{631} x_adv=3.78125 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 4 ب \u{628} x_adv=4 glyph=244 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 6 ي \u{64a} x_adv=4 glyph=363 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 8 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 9 ف \u{641} x_adv=11 glyph=328 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 11 ا \u{627} x_adv=4 glyph=240 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 13 ر \u{631} x_adv=3.78125 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 15 س \u{633} x_adv=10 glyph=278 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 17 ی \u{6cc} x_adv=4 glyph=664 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 19 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 20 - \u{2d} x_adv=8 glyph=276 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 21 > \u{3e} x_adv=8 glyph=338 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs ``` ``` ; ./target/debug/wezterm --config experimental_bidi=true ls-fonts --text "عربي فارسی ->" RightToLeft 17 ی \u{6cc} x_adv=9 glyph=906 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 15 س \u{633} x_adv=10 glyph=277 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 13 ر \u{631} x_adv=4.78125 glyph=272 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 11 ا \u{627} x_adv=4 glyph=241 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 9 ف \u{641} x_adv=5 glyph=329 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 8 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 6 ي \u{64a} x_adv=9 glyph=904 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 4 ب \u{628} x_adv=4 glyph=243 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 2 ر \u{631} x_adv=5 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 0 ع \u{639} x_adv=6 glyph=301 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText LeftToRight 0 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 1 - \u{2d} x_adv=8 glyph=480 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 2 > \u{3e} x_adv=8 glyph=470 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs ; ``` refs: https://github.com/wez/wezterm/issues/784
2022-01-25 18:16:51 +03:00
"wezterm-bidi",
refactor: move color parsing into wezerm-color-types crate Resolves a little bit of the awkward duplication of color types between some of the crates by factoring them a little bit better. This is prep for allowing specifying alpha for some colors in the config.
2022-02-05 23:59:54 +03:00
"wezterm-color-types",
refactor deps so that window can depend on wezterm-font I want to use this to render the font in the title bar
2021-06-27 05:48:06 +03:00
"wezterm-input-types",
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
"wezterm-term",
fonts: use toast notification for missing glyph notification Popping open the config error window is a bit of overkill
2021-05-02 02:05:23 +03:00
"wezterm-toast-notification",
wezterm: fixup win32 build for wezterm-gui changes refs: #301
2020-10-25 03:00:07 +03:00
"winapi 0.3.9",
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
]
[[package]]
name = "wezterm-gui"
version = "0.1.0"
dependencies = [
"anyhow",
benchmarking shaping `cargo test --release -p wezterm-gui -- --nocapture bench_shaping`: ``` running 1 test 100: 139.82µs 1000: 385.333µs 10000: 3.144203ms test shapecache::test::bench_shaping ... ok ```
2021-04-28 07:48:15 +03:00
"benchmarking",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
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
"cc",
add debug overlay Adds a `ShowDebugOverlay` key assignment that will create a tab overlay that shows a limited number of recently logged events. refs: https://github.com/wez/wezterm/issues/641
2021-05-03 06:50:01 +03:00
"chrono",
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
"codec",
gui: tidy up gradient calculation
2021-08-13 22:14:14 +03:00
"colorgrad",
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
"config",
term: allow iterm2 file transfer protocol Adds some plumbing to allow the GUI to implement a download handler and connect that up for iterm2 image/file transfers that have their inline property set to false. Previously we'd just log an error. Now we will by default download the file to the user's download directory. This behavior can be turned off via the new `allow_download_protocols` configuration setting. File transfers can be initiated on a remote host via the https://iterm2.com/utilities/it2dl script. When the download completes, a toast notification is shown that will open the file when clicked. refs: https://github.com/wez/wezterm/discussions/1450
2021-12-22 19:17:29 +03:00
"dirs-next",
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
"downcast-rs",
"embed-resource",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
"env-bootstrap",
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
gui: add some randomness to gradients to avoid banding
2021-08-13 23:35:55 +03:00
"fastrand",
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
"filedescriptor",
launcher now has fuzzy matching Just start typing text to build up the fuzzy matching term. The list of items updates to match the results. refs: #664 refs: #1485
2022-01-04 18:45:15 +03:00
"fuzzy-matcher",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hdrhistogram",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
"http_req",
cargo update
2020-06-13 20:21:49 +03:00
"image",
Add shaper post-processing function This function is intended to deal with certain kinds of ligatures and certain combining sequences that don't have corresponding glyphs. It isn't hooked up to the gui yet, but does have unit tests that are probably mostly correct. refs: https://github.com/wez/wezterm/issues/478
2021-02-22 20:19:05 +03:00
"k9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
"log",
"lru",
move lua helpers into own crate
2020-10-02 20:28:58 +03:00
"luahelper",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"metrics",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
"mlua",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"mux",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"open",
wezterm: allow adding images to termwiztermtab apps Tidies up the plumbing around pixel dimensions so that ImageData can be rendered via the termwiztermtab bits. I put this together to play with sticking the wezterm logo in the close confirmation dialogs. I didn't end up using that though, but have preserved the commented code for use in future hacking.
2020-12-27 01:01:48 +03:00
"ordered-float",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"portable-pty",
"promise",
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
"pulldown-cmark",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rangeset",
move ratelim to its own crate
2020-10-03 03:31:39 +03:00
"ratelim",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
"regex",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serde",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
"serde_json",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serial",
"shared_library",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"smol",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"structopt",
"tabout",
wezterm: enable scrollback in the error window This commit doesn't do anything specific to scrollback though! It moves the implementation of the TermWizTermTab away from a directly manipulated Surface and over to using the term::Terminal, making the renderer look more like the one used by the local tab and domain implementation. As a side effect of doing this, we get scrollback management for free. refs: https://github.com/wez/wezterm/issues/201
2020-06-03 17:58:20 +03:00
"terminfo",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"termwiz",
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
"termwiz-funcs",
deps: textwrap -> 0.15
2022-02-28 16:59:10 +03:00
"textwrap 0.15.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"thiserror",
zeno -> tiny_skia Mostly so that we can turn off anti-aliasing for smaller sizes, but it also happens to be more complete anyway.
2021-06-26 08:55:42 +03:00
"tiny-skia",
gui: add missing dep for windows refs: #1402
2021-12-18 07:28:16 +03:00
"uds_windows",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"umask",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-normalization",
"unicode-segmentation",
"unicode-width",
"url",
"walkdir",
wezterm: add experimental_bidi config option and very basic bidi This commit is larger than it appears to due fanout from threading through bidi parameters. The main changes are: * When clustering cells, add an additional phase to resolve embedding levels and further sub-divide a cluster based on the resolved bidi runs; this is where we get the direction for a run and this needs to be passed through to the shaper. * When doing bidi, the forced cluster boundary hack that we use to de-ligature when cursoring through text needs to be disabled, otherwise the cursor appears to push/rotate the text in that cluster when moving through it! We'll need to find a different way to handle shading the cursor that eliminates the original cursor/ligature/black issue. * In the shaper, the logic for coalescing unresolved runs for font fallback assumed LTR and needed to be adjusted to cluster RTL. That meant also computing a little index of codepoint lengths. * Added `experimental_bidi` boolean option that defaults to false. When enabled, it activates the bidi processing phase in clustering with a strong hint that the paragraph is LTR. This implementation is incomplete and/or wrong for a number of cases: * The config option should probably allow specifying the paragraph direction hint to use by default. * https://terminal-wg.pages.freedesktop.org/bidi/recommendation/paragraphs.html recommends that bidi be applied to logical lines, not physical lines (or really: ranges within physical lines) that we're doing at the moment * The paragraph direction hint should be overridden by cell attributes and other escapes; see 85a6b178cfddee94b3ddb39c26652bbd5a973666 and probably others. However, as of this commit, if you `experimental_bidi=true` then ``` echo This is RTL -> عربي فارسی bidi ``` (that text was sourced from: https://github.com/microsoft/terminal/issues/538#issuecomment-677017322) then wezterm will display the text in the same order as the text renders in Chrome for that github comment. ``` ; ./target/debug/wezterm --config experimental_bidi=false ls-fonts --text "عربي فارسی ->" LeftToRight 0 ع \u{639} x_adv=8 glyph=300 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 2 ر \u{631} x_adv=3.78125 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 4 ب \u{628} x_adv=4 glyph=244 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 6 ي \u{64a} x_adv=4 glyph=363 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 8 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 9 ف \u{641} x_adv=11 glyph=328 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 11 ا \u{627} x_adv=4 glyph=240 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 13 ر \u{631} x_adv=3.78125 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 15 س \u{633} x_adv=10 glyph=278 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 17 ی \u{6cc} x_adv=4 glyph=664 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 19 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 20 - \u{2d} x_adv=8 glyph=276 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 21 > \u{3e} x_adv=8 glyph=338 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs ``` ``` ; ./target/debug/wezterm --config experimental_bidi=true ls-fonts --text "عربي فارسی ->" RightToLeft 17 ی \u{6cc} x_adv=9 glyph=906 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 15 س \u{633} x_adv=10 glyph=277 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 13 ر \u{631} x_adv=4.78125 glyph=272 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 11 ا \u{627} x_adv=4 glyph=241 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 9 ف \u{641} x_adv=5 glyph=329 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 8 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 6 ي \u{64a} x_adv=9 glyph=904 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 4 ب \u{628} x_adv=4 glyph=243 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 2 ر \u{631} x_adv=5 glyph=273 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText 0 ع \u{639} x_adv=6 glyph=301 wezterm.font(".Geeza Pro Interface", {weight="Regular", stretch="Normal", italic=false}) /System/Library/Fonts/GeezaPro.ttc index=2 variation=0, CoreText LeftToRight 0 \u{20} x_adv=8 glyph=2 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 1 - \u{2d} x_adv=8 glyph=480 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs 2 > \u{3e} x_adv=8 glyph=470 wezterm.font("Operator Mono SSm Lig", {weight="DemiLight", stretch="Normal", italic=false}) /Users/wez/.fonts/OperatorMonoSSmLig-Medium.otf, FontDirs ; ``` refs: https://github.com/wez/wezterm/issues/784
2022-01-25 18:16:51 +03:00
"wezterm-bidi",
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
"wezterm-client",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
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
"wezterm-font",
"wezterm-gui-subcommands",
wezterm-gui: we now start an implicit unix mux server When running the GUI, we generate a unix domain socket path for the current process and start up a mux server for that path. This allows `wezterm cli list` and `wezterm cli split-pane` to work implicitly inside the GUI session. When started in this way, the mux server is not persistent; when the GUI process is terminated, all of its windows, tabs and panes are terminated. refs: https://github.com/wez/wezterm/issues/230
2020-12-30 02:58:39 +03:00
"wezterm-mux-server-impl",
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",
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
"wezterm-term",
tweak updating checking * Allow injecting some initial output to new panes * Have the update checker set this new-pane-banner to a short upsell to let the user know there is an update. * Refactor toast notifications into their own crate * Have the update checker call a new stub function that triggers a toast notification with an URL... but it does nothing because the rust ecosystem doesn't support this on macos yet and I'm writing this code there
2020-12-13 11:17:10 +03:00
"wezterm-toast-notification",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"window",
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
"windows",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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
[[package]]
name = "wezterm-gui-subcommands"
version = "0.1.0"
dependencies = [
add --position CLI option for requesting initial window position refs: #1794
2022-04-02 19:32:21 +03:00
"anyhow",
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
"config",
"structopt",
]
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
[[package]]
name = "wezterm-input-types"
version = "0.1.0"
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
input-types: introduce PhysKeyCode type Based on the mac constants of the equivalent functionality; may need some tweaking for other OS's. refs: https://github.com/wez/wezterm/issues/1483
2022-01-02 07:34:43 +03:00
"lazy_static",
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
"serde",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
]
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
[[package]]
name = "wezterm-mux-server"
version = "0.1.0"
dependencies = [
"anyhow",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"async_ossl",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"config",
wezterm: add env bootstrap to mux server, too
2020-10-25 09:29:52 +03:00
"env-bootstrap",
clean up mux server startup kindof a lot going on in this commit, unintentionally: * Need the lua context set to be moved into the config crate otherwise configs cannot be parsed by the server and we end up with the default configs * Make the server use smol for async io * Drop the use of the daemonize crate, which I had forked anyway. Just inline our own tighter daemonize module * Improve daemon spawning synchronization, however, it still needs work for windows to avoid blocking forever where we don't do daemonizing.
2020-10-04 19:39:28 +03:00
"libc",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"log",
"mux",
"openssl",
"portable-pty",
"promise",
"structopt",
"umask",
add --config name=value CLI options `wezterm`, `wezterm-gui` and `wezterm-mux-server` now all support a new `--config name=value` CLI option that can be specified multiple times to supply config overrides. Since there isn't a simple, direct way to update arbitrary fields of a struct in Rust (there's no runtime reflection), we do this work in lua. The config file returns a config table. Before that is mapped to the Rust Config type, we have a new phase that takes each of the `--config` values and applies it to the config table. For example, you can think of configuration as working like this if wezterm is started as `wezterm --config foo="bar"`: ```lua config = load_config_file(); config.foo = "bar"; return config; ``` The `--config name=value` option is split into `name` and `value` parts. The name part is literally concatenated with `config` in the generated lua code, so the name MUST be valid in that context. The `value` portion is literally inserted verbatim as the rvalue in the assignment. Not quoting or other processing is done, which means that you can (and must!) use the same form that you would use in the config file for the RHS. Strings must be quoted. This allows you to use more complicated expressions on the right hand side, such as: ``` wezterm --config 'font=wezterm.font("Fira Code")' ``` The overrides stick for the lifetime of the process; even if you change the config file and reload, then the value specified by the override will take precedence. refs: https://github.com/wez/wezterm/issues/469 refs: https://github.com/wez/wezterm/issues/499
2021-02-27 21:41:48 +03:00
"wezterm-gui-subcommands",
mux: factor out server bits to helper crate
2020-12-30 02:21:46 +03:00
"wezterm-mux-server-impl",
fixup windows build
2020-12-30 03:59:59 +03:00
"winapi 0.3.9",
mux: factor out server bits to helper crate
2020-12-30 02:21:46 +03:00
]
[[package]]
name = "wezterm-mux-server-impl"
version = "0.1.0"
dependencies = [
"anyhow",
"async_ossl",
"codec",
"config",
"futures",
"hostname",
"lazy_static",
"log",
"mux",
"portable-pty",
"promise",
"rangeset",
"rcgen",
"smol",
model: replace LineBits::DIRTY with a sequence number Terminal now maintains a sequence number that increments for each Action that is applied to it. Changes to lines are tagged with the current sequence number. This makes it a bit easier to reason about when an individual line has changed relative to some point in "time"; the consumer of the terminal can sample the current sequence number and then can later determine which lines have changed since that point in time. refs: https://github.com/wez/wezterm/issues/867
2021-08-08 22:45:08 +03:00
"termwiz",
wezterm-gui: we now start an implicit unix mux server When running the GUI, we generate a unix domain socket path for the current process and start up a mux server for that path. This allows `wezterm cli list` and `wezterm cli split-pane` to work implicitly inside the GUI session. When started in this way, the mux server is not persistent; when the GUI process is terminated, all of its windows, tabs and panes are terminated. refs: https://github.com/wez/wezterm/issues/230
2020-12-30 02:58:39 +03:00
"uds_windows",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"url",
"wezterm-term",
wezterm-gui: we now start an implicit unix mux server When running the GUI, we generate a unix domain socket path for the current process and start up a mux server for that path. This allows `wezterm cli list` and `wezterm cli split-pane` to work implicitly inside the GUI session. When started in this way, the mux server is not persistent; when the GUI process is terminated, all of its windows, tabs and panes are terminated. refs: https://github.com/wez/wezterm/issues/230
2020-12-30 02:58:39 +03:00
"winapi 0.3.9",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
]
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
[[package]]
name = "wezterm-ssh"
ssh: prep for crate release
2022-01-31 04:29:59 +03:00
version = "0.4.0"
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
dependencies = [
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs
2021-03-19 18:07:44 +03:00
"anyhow",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"assert_fs",
Update cargo.lock for 705d5182420582fc7cde2e7f733d3fd996f28abd
2022-01-31 06:18:27 +03:00
"async_ossl",
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs
2021-03-19 18:07:44 +03:00
"base64",
Add bitflags type safety to sftp flags
2021-10-03 23:37:19 +03:00
"bitflags",
Switch to camino::{Utf8PathBuf, Utf8Path}
2021-10-04 04:36:30 +03:00
"camino",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
"dirs-next",
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs
2021-03-19 18:07:44 +03:00
"filedescriptor",
wezterm-ssh: process Include statements refs: https://github.com/wez/wezterm/issues/824
2021-05-29 07:30:26 +03:00
"filenamegen",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
"k9",
ssh: can now pass e2e tests using libssh backend
2021-10-19 19:19:33 +03:00
"libc",
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
"libssh-rs",
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs
2021-03-19 18:07:44 +03:00
"log",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"once_cell",
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs
2021-03-19 18:07:44 +03:00
"portable-pty",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"predicates",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
"regex",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"rstest",
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs
2021-03-19 18:07:44 +03:00
"shell-words",
"smol",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"smol-potat",
ssh: support BindAddress for libssh2
2022-04-15 04:35:31 +03:00
"socket2",
wezterm-ssh: flesh out improved ssh crate This implementation should be less prone to stutters/stalls than my earlier hacky implementation in pty/src/ssh.rs
2021-03-19 18:07:44 +03:00
"ssh2",
"structopt",
"termwiz",
Create SftpError type and associated structs to provide more verbose errors for sftp
2021-09-27 04:54:08 +03:00
"thiserror",
Ensure /run/sshd exists, explicitly set username in sshd fixture, add back use_privilege_mode no
2021-09-27 08:14:06 +03:00
"whoami",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
]
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
[[package]]
name = "wezterm-term"
version = "0.1.0"
dependencies = [
"anyhow",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
allow using CSS style color specs in the config This change also allows removing the dep on the palette crate, which I found to be difficult to use (API changed often, and relied on a lot of `.into` that was hard to follow and reconcile across upgrades). We already pulled in the csscolorparse crate as an indirect dep of colorgrad, so we can replace the color conversion we need for sixel with that crate while we're in here. refs: #1615
2022-02-06 18:20:56 +03:00
"csscolorparser",
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
"env_logger",
termwiz: recognize the XTGETTCAP DCS sequence Parse and respond to this sequence docs can be found https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h4-Device-Control-functions:DCS-plus-q-Pt-ST.F95 refs: https://github.com/wez/wezterm/issues/954
2021-07-25 07:02:54 +03:00
"hex",
cargo update
2020-06-13 20:21:49 +03:00
"image",
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
"k9",
term: revise color cube in the default palette This commit adjusts the default color palette to use the same color cube calculation as xterm; it isn't the ideal color cube calculation and results in slightly brighter colors. This commit also memoizes the default palette calculation so that it isn't recomputed each time a palette is created. refs: https://github.com/wez/wezterm/issues/348
2020-12-09 11:52:24 +03:00
"lazy_static",
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
"log",
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
"lru",
cargo update
2022-02-14 06:31:40 +03:00
"miniz_oxide 0.4.4",
cargo update
2021-06-07 18:32:05 +03:00
"num-traits",
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
"ordered-float",
"serde",
termwiz: recognize the XTGETTCAP DCS sequence Parse and respond to this sequence docs can be found https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h4-Device-Control-functions:DCS-plus-q-Pt-ST.F95 refs: https://github.com/wez/wezterm/issues/954
2021-07-25 07:02:54 +03:00
"terminfo",
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
"termwiz",
fonts: allow harfbuzz to guess the script Our default meant that harfbuzz wouldn't engage preprocessing steps that normalized the text to NFC. With this change we now correctly normalize and render certain compositions that were totally borked previously. refs: https://github.com/wez/wezterm/issues/1573 refs: https://github.com/wez/wezterm/issues/1474
2022-01-21 20:08:31 +03:00
"unicode-normalization",
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
"unicode-segmentation",
"url",
bidi: tag Line with bidi mode This commit refines bidi property handling: * experimental_bidi has been split into two new configuration settings; `bidi_enabled` (which controls whether the terminal performs implicit bidi processing) and `bidi_direction` which specifies the base direction and whether auto detection is enabled. * The `Line` type can now store those bidi properties (they are actually split across 3 bits representing enabled, auto-detection and direction) * The terminal now has a concept of active bidi properties and default bidi properties * The default properties are pulled from the wezterm configuration * active bidi properties are potentially set via escape sequences, BDSM (which sets bidi_enabled) and SCP (which sets bidi_direction). We don't support the 2501 temporary dec private mode suggested by the BIDI recommendation doc at this time. * When creating new `Line`'s or clearing from the start of a `Line`, the effective bidi properties are computed (from the active props, falling back to default propr) and applied to the `Line`. * When rendering the line, we now look at its bidi properties instead of just the global config. The default bidi properties are `bidi_enabled: false` and `bidi_direction: LeftToRight` which corresponds to the typical bidi-unaware mode of most terminals. It is possible to live reload the config to change the effective defaults, but note that they apply, by design, to new lines being processed through the terminal. That means existing output is left unaffected by a config reload, but subsequently printed lines will respect it. Pressing CTRL-L or otherwise contriving to have the running application refresh its display should cause the refreshed display to update and apply the new bidi mode. refs: #784
2022-01-30 19:22:17 +03:00
"wezterm-bidi",
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x.
2022-05-14 18:00:03 +03:00
"wezterm-dynamic",
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
]
tweak updating checking * Allow injecting some initial output to new panes * Have the update checker set this new-pane-banner to a short upsell to let the user know there is an update. * Refactor toast notifications into their own crate * Have the update checker call a new stub function that triggers a toast notification with an URL... but it does nothing because the rust ecosystem doesn't support this on macos yet and I'm writing this code there
2020-12-13 11:17:10 +03:00
[[package]]
name = "wezterm-toast-notification"
version = "0.1.0"
dependencies = [
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"async-std",
wezterm: macos: show a toast notification when an update is available This commit implements the deprecated NSUserNotification bits needed to be able to handle clicking on a notification and open our choice of URL. Ideally we'd use the newer UserNotifications framework, but that requires code signing.
2020-12-16 08:21:23 +03:00
"cocoa",
"core-foundation 0.7.0",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"futures-util",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"log",
wezterm: macos: show a toast notification when an update is available This commit implements the deprecated NSUserNotification bits needed to be able to handle clicking on a notification and open our choice of URL. Ideally we'd use the newer UserNotifications framework, but that requires code signing.
2020-12-16 08:21:23 +03:00
"objc",
"open",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"serde",
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
"windows",
toast: hook up action/event handling on Windows refs: #489
2021-03-15 01:23:42 +03:00
"xml-rs",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"zbus",
fix unix build for zbus updates
2021-12-27 20:33:41 +03:00
"zvariant",
tweak updating checking * Allow injecting some initial output to new panes * Have the update checker set this new-pane-banner to a short upsell to let the user know there is an update. * Refactor toast notifications into their own crate * Have the update checker call a new stub function that triggers a toast notification with an URL... but it does nothing because the rust ecosystem doesn't support this on macos yet and I'm writing this code there
2020-12-13 11:17:10 +03:00
]
Ensure /run/sshd exists, explicitly set username in sshd fixture, add back use_privilege_mode no
2021-09-27 08:14:06 +03:00
[[package]]
name = "whoami"
cargo update
2021-11-29 05:09:45 +03:00
version = "1.2.1"
Ensure /run/sshd exists, explicitly set username in sshd fixture, add back use_privilege_mode no
2021-09-27 08:14:06 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-11-29 05:09:45 +03:00
checksum = "524b58fa5a20a2fb3014dd6358b70e6579692a56ef6fce928834e488f42f65e8"
Ensure /run/sshd exists, explicitly set username in sshd fixture, add back use_privilege_mode no
2021-09-27 08:14:06 +03:00
dependencies = [
"wasm-bindgen",
"web-sys",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "winapi"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "winapi"
cargo update
2020-06-30 03:52:14 +03:00
version = "0.3.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "winapi-util"
cargo update
2020-05-02 22:13:10 +03:00
version = "0.1.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-02 22:13:10 +03:00
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "window"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
window: separate gui window state from app state Removes the callbacks type and replaces event dispatch with an async capable channel. This makes it a bit simpler to model some of the window internals, and to prepare for a wgpu enabled future. This changes have been tested only on linux so far.
2021-05-04 18:38:43 +03:00
"async-channel",
wayland: fix key repeat The main culprit was the calloop feature that is used by default in the underlying SCTK crate. This commit: * Routes keyboard processing via the same keyboard mapping code that we use for X11 * Implements key repeats directly, and with awareness of elapsed time in case the repeat rate is quicker than the event dispatching quantum * Disables the calloop feature of SCTK and let us do our own polling of the wayland connection. Critically, key repeat is sticky and unpredictable while calloop is enabled. closes: #669
2021-06-28 00:24:41 +03:00
"async-io",
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
window: separate gui window state from app state Removes the callbacks type and replaces event dispatch with an async capable channel. This makes it a bit simpler to model some of the window internals, and to prepare for a wgpu enabled future. This changes have been tested only on linux so far.
2021-05-04 18:38:43 +03:00
"async-trait",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
window: add xsettings support on X11 systems This allows reading xsettings which contain information about both the active theme as well as the DPI. refs: #947
2021-07-18 22:52:20 +03:00
"bytes",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cgl",
"clipboard-win",
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
"clipboard_macos",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cocoa",
remove the config bridge and have window -> config directly
2021-03-24 07:56:57 +03:00
"config",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"core-foundation 0.7.0",
cargo update
2020-06-30 03:52:14 +03:00
"core-graphics 0.19.2",
x11: load XCursor.theme based cursors when available This requires `xcb-util-image-devel` on fedora, not sure about debian or other systems so far. refs: #524
2021-03-09 09:00:42 +03:00
"dirs-next",
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filedescriptor",
window: glium and gl_generator version bump
2020-06-15 07:24:54 +03:00
"gl_generator",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"glium",
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
"guillotiere",
window: add xsettings support on X11 systems This allows reading xsettings which contain information about both the active theme as well as the DPI. refs: #947
2021-07-18 22:52:20 +03:00
"k9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
cargo update
2021-03-01 20:02:05 +03:00
"libloading 0.6.7",
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
"line_drawing",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"log",
"metrics",
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
"mio 0.8.3",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"objc",
"promise",
cargo update
2021-11-29 05:09:45 +03:00
"raw-window-handle 0.3.4",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"resize",
wezterm: add raw_code concept to input layer This commit is a bit noisy because it also meant flipping the key map code from using the termwiz input types to the window input types, which I thought I'd done some time ago, but clearly didn't. This commit allows defining key assignments in terms of the underlying operating system raw codes, if provided by the relevant layer in the window crate (currently, only X11/Wayland). The raw codes are inherently OS/Machine/Hardware dependent; they are the rawest value that we have available and there is no meaningful understanding that we can perform in code to understand what that key is. One useful property of the raw code is that, because it hasn't gone through any OS level keymapping processing, its value reflects its physical position on the keyboard, allowing you to map keys by position rather than by value. That's useful if you use software to implement eg: DVORAK or COLEMAK but want your muscle memory to kick in for some of your key bindings. New config option: `debug_key_events = true` will cause wezterm to log an "error" to stderr each time you press a key and show the details in the key event: ``` 2020-12-06T21:23:10.313Z ERROR wezterm_gui::gui::termwindow > key_event KeyEvent { key: Char('@'), modifiers: SHIFT | CTRL, raw_key: None, raw_modifiers: SHIFT | CTRL, raw_code: Some(11), repeat_count: 1, key_is_down: true } ``` This is useful if you want to figure out the `raw_code` for a key in your setup. In your config, you can use this information to setup new key bindings. The motivating example for me is that because `raw_key` (the unmodified equivalent of `key`) is `None`, the built-in `CTRL-SHIFT-1` key assignment doesn't function for me on Linux, but I can now "fix" this in my local configuration, taking care to make it linux specific: ```lua local wezterm = require 'wezterm'; local keys = {} if wezterm.target_triple == "x86_64-unknown-linux-gnu" then local tab_no = 0 -- raw codes 10 through 19 correspond to the number key 1-9 positions -- on my keyboard on my linux system. They may be different on -- your system! for i = 10, 20 do table.insert(keys, { key="raw:"..tostring(i), mods="CTRL|SHIFT", action=wezterm.action{ActivateTab=tab_no}, }) tab_no = tab_no + 1 end end return { keys = keys, } ``` Notice that the key assignment accepts encoding a raw key code using a value like `key="raw:11"` to indicate that you want a `raw_code` of `11` to match your key assignment. The `raw_modifiers` portion of the `KeyEvent` is used together with the `raw_code` when deciding the key assignment. cc: @bew
2020-12-07 00:23:37 +03:00
"serde",
Windows: fix enabling dark mode This got broken by a recentish windows update.
2020-10-18 05:48:43 +03:00
"shared_library",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"smithay-client-toolkit",
"thiserror",
wayland: replace andrew with tiny_skia This has the consequence of removing the title bar text when client side decorations are in use.
2021-06-27 05:16:56 +03:00
"tiny-skia",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-client",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"wayland-egl",
wayland: import ConceptFrame impl from SCTK This has been removed in a later version, so pull it in ahead of updating that dependency to verify that it builds.
2021-06-27 03:37:45 +03:00
"wayland-protocols",
fix build on linux refs: https://github.com/wez/wezterm/issues/784
2022-01-25 19:27:01 +03:00
"wezterm-bidi",
refactor: move color parsing into wezerm-color-types crate Resolves a little bit of the awkward duplication of color types between some of the crates by factoring them a little bit better. This is prep for allowing specifying alpha for some colors in the config.
2022-02-05 23:59:54 +03:00
"wezterm-color-types",
refactor deps so that window can depend on wezterm-font I want to use this to render the font in the title bar
2021-06-27 05:48:06 +03:00
"wezterm-font",
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
"wezterm-input-types",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Improve RESIZE window_decoration on Windows
2022-03-24 17:20:26 +03:00
"windows",
pty: pre-fill base env from registry env settings on Windows I think I'd like to make a config option for this, but for the moment, this first pass unconditionally updates the base environment with data from the registry. refs: https://github.com/wez/wezterm/issues/1848
2022-04-19 19:56:23 +03:00
"winreg",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"x11",
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
"xcb",
IME support on X11 (#1043) * WIP: IME support for X11 * Handle text generated by IME. * Set IME position according to the cursor position. * Improve IME position handling. Geometry as well as window focus changes are now handled. * Dispatch IME strings like it's done on windows. * Make sure not to silently drop IME errors. * Respect `use_ime` configuration. * Add xcb-util as dependency. * Only update IME position if necessary. * Formatting. * Update xcb-imdkit-rs. * Set IME position under the start of the cursor. This seems to be the way it is commonly done among gui frameworks. (Tested with Firefox for GTK and Konsole for QT). * Update xcb-imdkit-rs. * Handle systems only providing libxcb-util0-dev. * Add libxcb to freebsd dependencies. Required by xcb-imdkit-rs. * Update xcb-imdkit-rs. * Try to use more recent gcc on centos7. * More recent C++ compiler on centos7 as well. * Also setup correct env on centos7 for tests.
2021-08-20 06:51:56 +03:00
"xcb-imdkit",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"xkbcommon",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
toast: hook up action/event handling on Windows refs: #489
2021-03-15 01:23:42 +03:00
[[package]]
name = "windows"
Use newer windows crate
2022-03-07 03:01:59 +03:00
version = "0.33.0"
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Use newer windows crate
2022-03-07 03:01:59 +03:00
checksum = "0128fa8e65e0616e45033d68dc0b7fbd521080b7844e5cad3a4a4d201c4b2bd2"
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
dependencies = [
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
"windows_aarch64_msvc 0.33.0",
"windows_i686_gnu 0.33.0",
"windows_i686_msvc 0.33.0",
"windows_x86_64_gnu 0.33.0",
"windows_x86_64_msvc 0.33.0",
]
[[package]]
name = "windows-sys"
version = "0.36.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ea04155a16a59f9eab786fe12a4a450e75cdb175f9e0d80da1e17db09f55b8d2"
dependencies = [
"windows_aarch64_msvc 0.36.1",
"windows_i686_gnu 0.36.1",
"windows_i686_msvc 0.36.1",
"windows_x86_64_gnu 0.36.1",
"windows_x86_64_msvc 0.36.1",
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
]
[[package]]
Use newer windows crate
2022-03-07 03:01:59 +03:00
name = "windows_aarch64_msvc"
version = "0.33.0"
toast: hook up action/event handling on Windows refs: #489
2021-03-15 01:23:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Use newer windows crate
2022-03-07 03:01:59 +03:00
checksum = "cd761fd3eb9ab8cc1ed81e56e567f02dd82c4c837e48ac3b2181b9ffc5060807"
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
[[package]]
name = "windows_aarch64_msvc"
version = "0.36.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9bb8c3fd39ade2d67e9874ac4f3db21f0d710bee00fe7cab16949ec184eeaa47"
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
[[package]]
Use newer windows crate
2022-03-07 03:01:59 +03:00
name = "windows_i686_gnu"
version = "0.33.0"
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Use newer windows crate
2022-03-07 03:01:59 +03:00
checksum = "cab0cf703a96bab2dc0c02c0fa748491294bf9b7feb27e1f4f96340f208ada0e"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
[[package]]
name = "windows_i686_gnu"
version = "0.36.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "180e6ccf01daf4c426b846dfc66db1fc518f074baa793aa7d9b9aaeffad6a3b6"
Use newer windows crate
2022-03-07 03:01:59 +03:00
[[package]]
name = "windows_i686_msvc"
version = "0.33.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8cfdbe89cc9ad7ce618ba34abc34bbb6c36d99e96cae2245b7943cd75ee773d0"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
[[package]]
name = "windows_i686_msvc"
version = "0.36.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2e7917148b2812d1eeafaeb22a97e4813dfa60a3f8f78ebe204bcc88f12f024"
Use newer windows crate
2022-03-07 03:01:59 +03:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.33.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b4dd9b0c0e9ece7bb22e84d70d01b71c6d6248b81a3c60d11869451b4cb24784"
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
[[package]]
name = "windows_x86_64_gnu"
version = "0.36.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4dcd171b8776c41b97521e5da127a2d86ad280114807d0b2ab1e462bc764d9e1"
Use newer windows crate
2022-03-07 03:01:59 +03:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.33.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ff1e4aa646495048ec7f3ffddc411e1d829c026a2ec62b39da15c1055e406eaa"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update note: this pins the openssl crate to workaround the combination of these two issues: refs: https://github.com/sfackler/rust-openssl/issues/1630 refs: https://github.com/sfackler/rust-openssl/pull/1578
2022-05-09 06:50:47 +03:00
[[package]]
name = "windows_x86_64_msvc"
version = "0.36.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c811ca4a8c853ef420abd8592ba53ddbbac90410fab6903b3e79972a631f7680"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
name = "winreg"
cargo update
2021-09-13 18:34:47 +03:00
version = "0.10.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-09-13 18:34:47 +03:00
checksum = "80d0f4e272c85def139476380b12f9ac60926689dd2e01d4923222f40580869d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
[[package]]
name = "wio"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5d129932f4644ac2396cb456385cbf9e63b5b30c6e8dc4820bdca4eb082037a5"
dependencies = [
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ws2_32-sys"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi 0.2.8",
"winapi-build",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "x11"
deps: cargo update
2021-10-04 08:10:01 +03:00
version = "2.19.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2021-10-04 08:10:01 +03:00
checksum = "6dd0565fa8bfba8c5efe02725b14dff114c866724eff2cfd44d76cea74bcd87a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"pkg-config",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
[[package]]
name = "xcb"
window: deps: upgrade to xcb 1.1 Was a bit fiddly. Eliminated the xcb_util crate refs: https://github.com/wez/wezterm/issues/1952
2022-05-08 00:18:26 +03:00
version = "1.1.1"
cargo update
2022-05-16 05:44:27 +03:00
source = "git+https://github.com/wez/rust-xcb?branch=ffi#362404a8f647da4f46cf7ed2631a4b7b0daf437c"
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
dependencies = [
window: deps: upgrade to xcb 1.1 Was a bit fiddly. Eliminated the xcb_util crate refs: https://github.com/wez/wezterm/issues/1952
2022-05-08 00:18:26 +03:00
"bitflags",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"libc",
window: deps: upgrade to xcb 1.1 Was a bit fiddly. Eliminated the xcb_util crate refs: https://github.com/wez/wezterm/issues/1952
2022-05-08 00:18:26 +03:00
"quick-xml",
window: x11: fix minor leak of a display connection These were two separate one-time losses. refs: https://github.com/wez/wezterm/issues/238
2020-07-08 18:34:22 +03:00
"x11",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
]
IME support on X11 (#1043) * WIP: IME support for X11 * Handle text generated by IME. * Set IME position according to the cursor position. * Improve IME position handling. Geometry as well as window focus changes are now handled. * Dispatch IME strings like it's done on windows. * Make sure not to silently drop IME errors. * Respect `use_ime` configuration. * Add xcb-util as dependency. * Only update IME position if necessary. * Formatting. * Update xcb-imdkit-rs. * Set IME position under the start of the cursor. This seems to be the way it is commonly done among gui frameworks. (Tested with Firefox for GTK and Konsole for QT). * Update xcb-imdkit-rs. * Handle systems only providing libxcb-util0-dev. * Add libxcb to freebsd dependencies. Required by xcb-imdkit-rs. * Update xcb-imdkit-rs. * Try to use more recent gcc on centos7. * More recent C++ compiler on centos7 as well. * Also setup correct env on centos7 for tests.
2021-08-20 06:51:56 +03:00
[[package]]
name = "xcb-imdkit"
window: deps: upgrade to xcb 1.1 Was a bit fiddly. Eliminated the xcb_util crate refs: https://github.com/wez/wezterm/issues/1952
2022-05-08 00:18:26 +03:00
version = "0.2.0"
window: point to my xcb for for IME changes refs: https://github.com/rust-x-bindings/rust-xcb/pull/190 refs: https://github.com/H-M-H/xcb-imdkit-rs/pull/2
2022-05-08 23:59:24 +03:00
source = "git+https://github.com/wez/xcb-imdkit-rs.git?rev=ede7c71b85fe2537efef6cf999a45690316211cf#ede7c71b85fe2537efef6cf999a45690316211cf"
IME support on X11 (#1043) * WIP: IME support for X11 * Handle text generated by IME. * Set IME position according to the cursor position. * Improve IME position handling. Geometry as well as window focus changes are now handled. * Dispatch IME strings like it's done on windows. * Make sure not to silently drop IME errors. * Respect `use_ime` configuration. * Add xcb-util as dependency. * Only update IME position if necessary. * Formatting. * Update xcb-imdkit-rs. * Set IME position under the start of the cursor. This seems to be the way it is commonly done among gui frameworks. (Tested with Firefox for GTK and Konsole for QT). * Update xcb-imdkit-rs. * Handle systems only providing libxcb-util0-dev. * Add libxcb to freebsd dependencies. Required by xcb-imdkit-rs. * Update xcb-imdkit-rs. * Try to use more recent gcc on centos7. * More recent C++ compiler on centos7 as well. * Also setup correct env on centos7 for tests.
2021-08-20 06:51:56 +03:00
dependencies = [
"bitflags",
"cc",
"lazy_static",
"pkg-config",
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
"xcb",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
]
[[package]]
name = "xcursor"
cargo update
2021-08-23 17:33:44 +03:00
version = "0.3.4"
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-23 17:33:44 +03:00
checksum = "463705a63313cd4301184381c5e8042f0a7e9b4bb63653f216311d4ae74690b7"
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
dependencies = [
deps: cargo update
2022-03-21 17:47:57 +03:00
"nom 7.1.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "xkbcommon"
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
version = "0.5.0-beta.0"
source = "git+https://github.com/wez/xkbcommon-rs.git?branch=key-by-name#546ba7dbf2ace214b9947fc4646a0f4afd70cb0a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
window: point to re-integrated xkbcommon refs: https://github.com/rust-x-bindings/xkbcommon-rs/pull/30
2022-05-10 03:24:20 +03:00
"memmap2 0.5.3",
switch macos clipboard crate This cleans up the `cargo audit` output on linux because the `clipboard` crate (which hasn't been updated in 3 years) depends on xcb=0.8.2 which is flagged by cargo audit. We don't use `clipboard` on any platform except macos This commit switches to the `clipboard_macos` crate; that appears to use a copy and paste of the macos specific code from the `clipboard` crate, so this shouldn't have any change in functionality. refs: https://github.com/wez/wezterm/issues/1952
2022-05-09 07:11:39 +03:00
"xcb",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "xml-rs"
cargo update
2021-08-02 04:40:25 +03:00
version = "0.8.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-08-02 04:40:25 +03:00
checksum = "d2d7d3948613f75c98fd9328cfdcc45acc4d360655289d0a7d4ec931392200a3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "yasna"
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
version = "0.5.0"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
checksum = "346d34a236c9d3e5f3b9b74563f238f955bbd05fa0b8b4efa53c130c43982f4c"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
"time 0.3.9",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "zbus"
cargo update
2022-05-02 07:21:14 +03:00
version = "2.2.0"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "53819092b9db813b2c6168b097b4b13ad284d81c9f2b0165a0a1b190e505a1f3"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
dependencies = [
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"async-broadcast",
"async-channel",
"async-executor",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"async-io",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"async-lock",
"async-recursion",
"async-task",
"async-trait",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"byteorder",
"derivative",
"enumflags2",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"event-listener",
"futures-core",
"futures-sink",
"futures-util",
"hex",
deps: cargo update
2022-02-06 17:46:12 +03:00
"lazy_static",
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
"nix 0.23.1",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"once_cell",
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
"ordered-stream",
cargo update
2022-02-22 05:44:27 +03:00
"rand 0.8.5",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"serde",
"serde_repr",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"sha1",
"static_assertions",
cargo update
2022-05-02 07:21:14 +03:00
"uds_windows",
deps: cargo update
2022-02-06 17:46:12 +03:00
"winapi 0.3.9",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"zbus_macros",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"zbus_names",
fix unix build for zbus updates
2021-12-27 20:33:41 +03:00
"zvariant",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
[[package]]
name = "zbus_macros"
cargo update
2022-05-02 07:21:14 +03:00
version = "2.2.0"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-02 07:21:14 +03:00
checksum = "c7174ebe6722c280d6d132d694bb5664ce50a788cb70eeb518e7fc1ca095a114"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
dependencies = [
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"proc-macro-crate",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"regex",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
[[package]]
name = "zbus_names"
cargo update
2022-01-17 04:46:30 +03:00
version = "2.1.0"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-01-17 04:46:30 +03:00
checksum = "45dfcdcf87b71dad505d30cc27b1b7b88a64b6d1c435648f48f9dbc1fdc4b7e1"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
dependencies = [
"serde",
"static_assertions",
fix unix build for zbus updates
2021-12-27 20:33:41 +03:00
"zvariant",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "zstd"
cargo update
2021-03-08 10:18:21 +03:00
version = "0.6.1+zstd.1.4.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "5de55e77f798f205d8561b8fe2ef57abfb6e0ff2abe7fd3c089e119cdb5631a3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"zstd-safe",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "zstd-safe"
cargo update
2021-03-08 10:18:21 +03:00
version = "3.0.1+zstd.1.4.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "1387cabcd938127b30ce78c4bf00b30387dddf704e3f0881dbc4ff62b5566f8c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"zstd-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "zstd-sys"
cargo update
2021-03-08 10:18:21 +03:00
version = "1.4.20+zstd.1.4.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "ebd5b733d7cf2d9447e2c3e76a5589b4f5e5ae065c22a2bc0b023cbc331b6c8e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
[[package]]
name = "zvariant"
cargo update
2022-05-16 05:44:27 +03:00
version = "3.2.1"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "cbd1abd8bc2c855412b9c8af9fc11c0d695c73c732ad5a1a1be10f3fd4bf19b2"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
dependencies = [
"byteorder",
"enumflags2",
deps: cargo update
2021-10-04 08:10:01 +03:00
"libc",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"serde",
cargo update
2021-06-14 09:36:22 +03:00
"static_assertions",
fix unix build for zbus updates
2021-12-27 20:33:41 +03:00
"zvariant_derive",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
[[package]]
name = "zvariant_derive"
cargo update
2022-05-16 05:44:27 +03:00
version = "3.2.1"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-05-16 05:44:27 +03:00
checksum = "abebd57382dfacf3e7bbdd7b7c3d162d6ed0687a78f046263ddef4ddabc275ae"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
dependencies = [
"proc-macro-crate",
"proc-macro2",
"quote",
"syn",
]
Reference in New Issue Copy Permalink