wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-12-18 10:52:16 +03:00
Code Issues Projects Releases Wiki Activity
96d155170e
wezterm/Cargo.lock

6819 lines
152 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
2022-12-19 21:13:02 +03:00
version = "0.19.0"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-19 21:13:02 +03:00
checksum = "a76fd60b23679b7d19bd066031410fb7e458ccc5e958eb5c325888ce4baedc97"
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
2023-01-16 07:48:20 +03:00
"getrandom",
deps: cargo update, and a couple of dependabot suggestions
2021-07-19 05:10:46 +03:00
"once_cell",
"version_check",
]
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
[[package]]
name = "ahash"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "0.8.3"
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "2c99f64d1e06488f620f932677e24bc6e2897582980441ae90a671415bd7ec2f"
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
"getrandom",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +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
2022-11-28 07:32:51 +03:00
version = "0.7.20"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-11-28 07:32:51 +03:00
checksum = "cc936419f96fa211c1b9166887b38e5e40b19958e5b895be7c1f93adec7071ac"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2022-08-15 08:27:23 +03:00
[[package]]
name = "android_system_properties"
cargo update
2022-09-04 04:54:36 +03:00
version = "0.1.5"
cargo update
2022-08-15 08:27:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-09-04 04:54:36 +03:00
checksum = "819e7219dbd41043ac279b19830f2efc897156490d7fd6ea916720117ee66311"
cargo update
2022-08-15 08:27:23 +03:00
dependencies = [
"libc",
]
cargo update
2023-03-17 22:02:21 +03:00
[[package]]
name = "anstyle"
version = "0.3.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "23ea9e81bd02e310c216d080f6223c179012256e5151c41db88d12c88a1684d2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.70"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
checksum = "7de8ce5e0f9f8d88245311066a578d72b7af3e7088f32783804676302df237e4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
deps: tiny-skia 0.7 -> 0.8
2022-08-29 06:50:27 +03:00
version = "0.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"
deps: tiny-skia 0.7 -> 0.8
2022-08-29 06:50:27 +03:00
checksum = "8da52d66c7071e2e3fa2a1e5c6d088fec47b593032b254f5e980de8ea54454d6"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "ash"
cargo update
2023-01-16 07:48:20 +03:00
version = "0.37.2+1.3.238"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-16 07:48:20 +03:00
checksum = "28bf19c1f0a470be5fbf7522a308a05df06610252c5bcf5143e1b23f629a9a03"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"libloading 0.7.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
[[package]]
name = "assert_fs"
cargo update
2023-03-17 22:02:21 +03:00
version = "1.0.12"
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
2023-03-17 22:02:21 +03:00
checksum = "e9d5bf7e5441c6393b5a9670a5036abe6b4847612f594b870f7332dbf10cf6fa"
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 = [
cargo update
2023-03-17 22:02:21 +03:00
"anstyle",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"doc-comment",
"globwalk",
cargo update
2023-03-17 22:02:21 +03:00
"predicates 3.0.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
"predicates-core",
"predicates-tree",
"tempfile",
]
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
2023-02-27 08:32:52 +03:00
version = "0.5.1"
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
2023-02-27 08:32:52 +03:00
checksum = "7c48ccdbf6ca6b121e0f586cbc0e73ae440e56c67c30fa0873b4e110d9c26d2b"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
dependencies = [
"event-listener",
"futures-core",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "async-channel"
cargo update
2022-12-05 05:40:53 +03:00
version = "1.8.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-05 05:40:53 +03:00
checksum = "cf46fee83e5ccffc220104713af3292ff9bc7c64c7de289f66dae8e38d826833"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
cargo update
2022-12-05 05:40:53 +03:00
"concurrent-queue",
cargo update
2020-09-09 19:31:37 +03:00
"event-listener",
"futures-core",
]
[[package]]
name = "async-executor"
cargo update
2022-11-14 04:24:31 +03:00
version = "1.5.0"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-14 04:24:31 +03:00
checksum = "17adb73da160dfb475c183343c8cccd80721ea5a605d3eb57125f0a7b7a92d0b"
cargo update
2020-10-02 17:16:20 +03:00
dependencies = [
cargo update
2022-11-14 04:24:31 +03:00
"async-lock",
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
cargo update
2022-12-05 05:40:53 +03:00
"concurrent-queue",
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
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
2022-08-21 18:51:16 +03:00
version = "1.6.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-08-21 18:51:16 +03:00
checksum = "279cf904654eeebfa37ac9bb1598880884924aab82e290aa65c9e77a0e142e06"
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",
cargo update
2022-08-21 18:51:16 +03:00
"autocfg",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"blocking",
"futures-lite",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "async-io"
cargo update
2022-11-28 07:32:51 +03:00
version = "1.12.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-28 07:32:51 +03:00
checksum = "8c374dda1ed3e7d8f0d9ba58715f924862c63eae6849c92d3a18e7fbde9e2794"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
deps: remove async-std dep We were only using block_on from it, which we can call from the underlying async_io crate. Notably, removing async_std from the deps avoids async-global-executor being pulled in and spawning nproc threads that are never used by wezterm.
2022-11-01 17:05:33 +03:00
"async-lock",
cargo update
2022-08-21 18:51:16 +03:00
"autocfg",
cargo update
2022-12-05 05:40:53 +03:00
"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",
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
2023-03-06 08:18:33 +03:00
"socket2 0.4.9",
cargo update
2020-10-02 17:16:20 +03:00
"waker-fn",
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.42.0",
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
2023-03-06 08:18:33 +03:00
version = "2.7.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
2023-03-06 08:18:33 +03:00
checksum = "fa24f727524730b077666307f2734b4a1a1c57acb79193127dcc8914d5242dd7"
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
]
[[package]]
name = "async-net"
cargo update
2022-08-21 18:51:16 +03:00
version = "1.7.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-08-21 18:51:16 +03:00
checksum = "4051e67316bc7eff608fe723df5d32ed639946adcd69e07df41fd42a7b411f1f"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
"async-io",
cargo update
2022-08-21 18:51:16 +03:00
"autocfg",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"blocking",
"futures-lite",
]
[[package]]
name = "async-process"
cargo update
2022-11-28 07:32:51 +03:00
version = "1.6.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-11-28 07:32:51 +03:00
checksum = "6381ead98388605d0d9ff86371043b5aa922a3905824244de40dc263a14fcba4"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
"async-io",
cargo update
2022-11-28 07:32:51 +03:00
"async-lock",
cargo update
2022-08-21 18:51:16 +03:00
"autocfg",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"blocking",
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
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",
cargo update
2023-02-17 21:30:15 +03:00
"signal-hook 0.3.15",
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.42.0",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +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 = "async-recursion"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.4"
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
2023-03-20 06:20:34 +03:00
checksum = "0e97ce7de6cf12de5d7226c73f5ba9811622f4db3a5b91b55c53e987e5f91cba"
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
dependencies = [
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 2.0.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-10-02 17:16:20 +03:00
[[package]]
name = "async-task"
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
version = "4.3.0"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
checksum = "7a40729d2133846d9ed0ea60a8b9541bccddab49cd30f0715a1da672fe9a2524"
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"
cargo update
2023-03-20 06:20:34 +03:00
version = "0.1.67"
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"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "86ea188f25f0255d8f92797797c97ebf5631fa88178beb1a46fdf5622c9a00e4"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 2.0.2",
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",
]
add wezterm-blob-leases crate
2023-03-18 22:21:30 +03:00
[[package]]
name = "atomic"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b88d82667eca772c4aa12f0f1348b3ae643424c8876448f3f7bd5787032e234c"
dependencies = [
"autocfg",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "atomic-waker"
cargo update
2023-01-16 07:48:20 +03:00
version = "1.1.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-16 07:48:20 +03:00
checksum = "debc29dde2e69f9e47506b525f639ed42300fc014a3e007832592448fa8e4599"
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 = "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
2022-11-28 07:32:51 +03:00
"hermit-abi 0.1.19",
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: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2022-12-19 21:13:02 +03:00
version = "0.3.67"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-12-19 21:13:02 +03:00
checksum = "233d376d6d185f2a3093e58f283f60f880315b6c60075b01f36b3b85154564ca"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +03:00
"cfg-if",
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-12-19 21:13:02 +03:00
"miniz_oxide 0.6.2",
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
2022-10-23 22:08:11 +03:00
version = "0.13.1"
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
2022-10-23 22:08:11 +03:00
checksum = "9e1b586273c5702936fe7b7d6896644d8be71e6314cfe09d3167c95f712589e8"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
deps: update base64 closes: https://github.com/wez/wezterm/pull/2855
2022-12-12 19:14:42 +03:00
[[package]]
name = "base64"
update base64, work around another batch of breaking API changes closes: https://github.com/wez/wezterm/pull/2931
2023-01-09 04:49:45 +03:00
version = "0.21.0"
deps: update base64 closes: https://github.com/wez/wezterm/pull/2855
2022-12-12 19:14:42 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update base64, work around another batch of breaking API changes closes: https://github.com/wez/wezterm/pull/2931
2023-01-09 04:49:45 +03:00
checksum = "a4a4ddaa51a5bc52a6948f74c06d20aaaddb71924eab79b8c97a8c556e942d6a"
deps: update base64 closes: https://github.com/wez/wezterm/pull/2855
2022-12-12 19:14:42 +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
2023-02-06 07:53:11 +03:00
version = "0.4.12"
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
2023-02-06 07:53:11 +03:00
checksum = "32842502e72b27b30b2681692d16bf47a8a375c5a2795613f0dc699bed9a48bb"
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"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "bit-set"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0700ddab506f33b20a03b13996eccd309a48e5ff77d0d95926aa0210fb4e95f1"
dependencies = [
"bit-vec",
]
[[package]]
name = "bit-vec"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "349f9b6a179ed607305526ca489b34ad0a41aed5f7980fa90eb03160b69598fb"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "bit_field"
cargo update
2023-02-27 08:32:52 +03:00
version = "0.10.2"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-27 08:32:52 +03:00
checksum = "dc827186963e592360843fb5ba4b973e145841266c1357f7180c43526f2e5b61"
deps: image -> 0.24
2022-02-07 04:51: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 = "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
cargo update
2023-03-20 06:20:34 +03:00
[[package]]
name = "bitflags"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "487f1e0fcbe47deb8b0574e646def1c903389d95241dd1bbcc6ce4a715dfc0c1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
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
2022-08-01 06:14:19 +03:00
"generic-array",
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]]
cargo update
2022-08-01 06:14:19 +03:00
name = "block-buffer"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.10.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
2023-03-13 06:22:05 +03:00
checksum = "3078c7629b62d3f0439517fa394996acacc5cbc91c5a20d8c658e77abd503a71"
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 = [
cargo update
2022-08-01 06:14:19 +03:00
"generic-array",
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"
cargo update
2022-11-28 07:32:51 +03:00
version = "1.3.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-28 07:32:51 +03:00
checksum = "3c67b173a56acffd6d2326fb7ab938ba0b00a71480e14902b2591c87bc5741e8"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"async-channel",
cargo update
2022-11-28 07:32:51 +03:00
"async-lock",
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
]
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
]
cargo update
2023-01-08 17:46:31 +03:00
[[package]]
name = "bstr"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.4.0"
cargo update
2023-01-08 17:46:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "c3d4260bcc2e8fc9df1eac4919a720effeb63a3f0952f5bf4944adfa18897f09"
cargo update
2023-01-08 17:46:31 +03:00
dependencies = [
"memchr",
"serde",
]
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
2023-01-21 06:04:49 +03:00
version = "3.12.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"
cargo update
2023-01-21 06:04:49 +03:00
checksum = "0d261e256854913907f67ed06efbc3338dfe6179796deefc1ff763fc1aee5535"
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: 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
2023-03-06 08:18:33 +03:00
version = "1.13.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
2023-03-06 08:18:33 +03:00
checksum = "17febce684fd15d89027105661fec94afb475cb995fbc59d2865198446ba2eea"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"bytemuck_derive",
]
[[package]]
name = "bytemuck_derive"
cargo update
2023-01-21 06:04:49 +03:00
version = "1.4.0"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-21 06:04:49 +03:00
checksum = "1aca418a974d83d40a0c1f0c5cba6ff4bc28d8df099109ca459a2118d40b6322"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
]
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
2023-02-06 07:53:11 +03:00
version = "1.4.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
2023-02-06 07:53:11 +03:00
checksum = "89b2fd2a0dcf38d7971e2194b6b6eebab45ae01067456a7fd93d5547a61b70be"
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
Switch to camino::{Utf8PathBuf, Utf8Path}
2021-10-04 04:36:30 +03:00
[[package]]
name = "camino"
cargo update
2023-03-13 06:22:05 +03:00
version = "1.1.4"
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
2023-03-13 06:22:05 +03:00
checksum = "c530edf18f37068ac2d977409ed5cd50d53d73bc653c7647b48eb78976ac9ae2"
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
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "cast"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "37b2a672a2cb129a2e41c10b1224bb368f9f37a2b16b612598138befd7b37eb5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "1.0.79"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "50d30906286121d95be3d479533b458f87493b30a4b5f79a607db8f5d11aa91f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
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
2023-03-13 06:22:05 +03:00
version = "0.4.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
2023-03-13 06:22:05 +03:00
checksum = "4e3c5919066adf22df73762e50cffcde3a758f2a848b113b586d1f86728b673b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-08-15 08:27:23 +03:00
"iana-time-zone",
cargo update
2022-08-08 05:31:29 +03:00
"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
"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
2022-08-08 05:31:29 +03:00
"wasm-bindgen",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +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"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
checksum = "a0610544180c38b88101fecf2dd634b174a62eef6946f84dfc6a7127512b381c"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
"textwrap 0.11.0",
"unicode-width",
]
[[package]]
name = "clap"
cargo update
2023-03-20 06:20:34 +03:00
version = "4.1.11"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "42dfd32784433290c51d92c438bb72ea5063797fc3cc9a21a8c4346bebbb2098"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 2.0.2",
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
"clap_derive",
"clap_lex",
cargo update
2022-11-28 07:32:51 +03:00
"is-terminal",
cargo update
2022-06-20 07:40:05 +03:00
"once_cell",
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
"strsim",
"termcolor",
]
add `wezterm shell-completion` subcommand to generate shell completions
2022-05-28 17:43:28 +03:00
[[package]]
name = "clap_complete"
cargo update
2023-03-17 22:02:21 +03:00
version = "4.1.5"
add `wezterm shell-completion` subcommand to generate shell completions
2022-05-28 17:43:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "37686beaba5ac9f3ab01ee3172f792fc6ffdd685bfb9e63cfef02c0571a4e8e1"
add `wezterm shell-completion` subcommand to generate shell completions
2022-05-28 17:43:28 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
add `wezterm shell-completion` subcommand to generate shell completions
2022-05-28 17:43:28 +03:00
]
Add `fig` to shells for shell completion
2022-08-21 09:48:04 +03:00
[[package]]
name = "clap_complete_fig"
cargo update
2023-03-17 22:02:21 +03:00
version = "4.1.2"
Add `fig` to shells for shell completion
2022-08-21 09:48:04 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "2171bc6242ad7a1801422bff039574449b5bd832b715222e500714ce10f91a54"
Add `fig` to shells for shell completion
2022-08-21 09:48:04 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
Add `fig` to shells for shell completion
2022-08-21 09:48:04 +03:00
"clap_complete",
]
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
[[package]]
name = "clap_derive"
cargo update
2023-03-17 22:02:21 +03:00
version = "4.1.9"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "fddf67631444a3a3e3e5ac51c36a5e01335302de677bd78759eaa90ab1f46644"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
dependencies = [
"heck",
"proc-macro-error",
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
]
[[package]]
name = "clap_lex"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.3.3"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "033f6b7a4acb1f358c742aaca805c939ee73b4c6209ae4318ec7aca81c42e646"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
dependencies = [
"os_str_bytes",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = [
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.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
"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",
]
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "codespan-reporting"
version = "0.11.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3538270d33cc669650c4b093848450d380def10c331d38c768e34cac80576e6e"
dependencies = [
"termcolor",
"unicode-width",
]
add wezterm.color module for working with colors wezterm.color.parse() returns a color object that can be assigned in the wezterm color config, and that can be used to adjust hue, saturation and lightness, as well as calculate harmonizing colors (complements, triads, squares) from the RGB/HSL color wheel.
2022-07-11 09:41:18 +03:00
[[package]]
name = "color-funcs"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"csscolorparser",
lua: add wezterm.color.extract_colors_from_image This function can be used to extra distinct colors from an image to be fed into eg: color scheme generation.
2022-07-11 21:03:06 +03:00
"deltae",
"image",
"lazy_static",
"log",
"lru",
add wezterm.color module for working with colors wezterm.color.parse() returns a color object that can be assigned in the wezterm color config, and that can be used to adjust hue, saturation and lightness, as well as calculate harmonizing colors (complements, triads, squares) from the RGB/HSL color wheel.
2022-07-11 09:41:18 +03:00
"luahelper",
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
"plist",
color schemes: move other color scheme format code to color-funcs I want to add lua funcs for importing schemes; this is a step towards that.
2022-07-14 07:29:51 +03:00
"serde",
"serde_json",
"serde_yaml",
lua: add wezterm.color.extract_colors_from_image This function can be used to extra distinct colors from an image to be fed into eg: color scheme generation.
2022-07-11 21:03:06 +03:00
"wezterm-dynamic",
add wezterm.color.get_default_colors
2022-07-15 07:41:39 +03:00
"wezterm-term",
add wezterm.color module for working with colors wezterm.color.parse() returns a color object that can be assigned in the wezterm color config, and that can be used to adjust hue, saturation and lightness, as well as calculate harmonizing colors (complements, triads, squares) from the RGB/HSL color wheel.
2022-07-11 09:41: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 = "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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
[[package]]
name = "colorgrad"
cargo update
2022-10-17 06:57:48 +03:00
version = "0.6.2"
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"
cargo update
2022-10-17 06:57:48 +03:00
checksum = "6a5f405d474b9d05e0a093d3120e77e9bf26461b57a84b40aa2a221ac5617fb6"
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
dependencies = [
"csscolorparser",
]
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
[[package]]
name = "com-rs"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bf43edc576402991846b093a7ca18a3477e0ef9c588cde84964b5d3e43016642"
cargo update
2022-11-14 04:24:31 +03:00
[[package]]
name = "concurrent-queue"
cargo update
2023-01-16 07:48:20 +03:00
version = "2.1.0"
cargo update
2022-11-14 04:24:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-16 07:48:20 +03:00
checksum = "c278839b831783b70278b14df4d45e1beb1aad306c07bb796637de9a0e323e8e"
cargo update
2022-11-14 04:24:31 +03:00
dependencies = [
"crossbeam-utils",
]
move config into its own crate
2020-10-02 21:50:50 +03:00
[[package]]
name = "config"
version = "0.1.0"
dependencies = [
"anyhow",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
"git2",
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",
cargo update
2023-03-17 22:02:21 +03:00
"toml 0.7.3",
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: derive some metadata about the config This isn't used by anything yet, but will enable some runtime config editing functions that I have planeed for the future.
2022-09-22 03:42:43 +03:00
"wezterm-config-derive",
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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"
cargo update
2022-09-05 17:36:58 +03:00
version = "0.2.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
2022-09-05 17:36:58 +03:00
checksum = "28d997bd5e24a5928dd43e46dc529867e207907fe0b239c3477d924f7f2ca320"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "criterion"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b01d6de93b2b6c65e17c634a26653a29d107b3c98c607c765bf38d041531cd8f"
dependencies = [
"atty",
"cast",
"clap 2.34.0",
"criterion-plot",
"csv",
"itertools",
"lazy_static",
"num-traits",
"oorandom",
"plotters",
"rayon",
"regex",
"serde",
"serde_cbor",
"serde_derive",
"serde_json",
"tinytemplate",
"walkdir",
]
[[package]]
name = "criterion-plot"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2673cc8207403546f45f5fd319a974b1e6983ad1a3ee7e6041650013be041876"
dependencies = [
"cast",
"itertools",
]
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
2022-07-25 03:15:59 +03:00
version = "0.8.2"
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
2022-07-25 03:15:59 +03:00
checksum = "2801af0d36612ae591caa9568261fddce32ce6e08a7275ea334a06a4ad021a2c"
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 = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: misc updates
2020-12-29 20:21:50 +03:00
"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"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.5.7"
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
2023-03-06 08:18:33 +03:00
checksum = "cf2b3e8478797446514c91ef04bafcb59faba183e621ad488df88983cc14128c"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
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
2023-03-06 08:18:33 +03:00
version = "0.8.3"
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
2023-03-06 08:18:33 +03:00
checksum = "ce6fd6f855243022dcecf8702fef0c297d4338e226845fe067f6341ad9fa0cef"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
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"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.9.14"
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
2023-03-06 08:18:33 +03:00
checksum = "46bd5f3f85273295a9d14aedfb86f6aadbff6d8f5295c4a9edb08e819dcf5695"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
cargo update
2023-03-06 08:18:33 +03:00
"memoffset 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
"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"
cargo update
2022-11-28 07:32:51 +03:00
version = "0.3.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-28 07:32:51 +03:00
checksum = "d1cfb3ea8a53f37c40dea2c7bedcbd88bdfae54f5e2175d6ecaff1c988353add"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +03:00
"cfg-if",
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-utils"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.8.15"
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
2023-03-06 08:18:33 +03:00
checksum = "3c063cd8cc95f5c377ed0d4b49a4b21f632396ff690e8470c29b3359b346984b"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
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
]
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "crunchy"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7a81dae078cea95a014a339291cec439d2f232ebe854a9d672b796c6afafa9b7"
cargo update
2022-08-01 06:14:19 +03:00
[[package]]
name = "crypto-common"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1bfb12502f3fc46cca1bb51ac28df9d618d813cdc3d2f25b9fe775a34af26bb3"
dependencies = [
"generic-array",
"typenum",
]
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
[[package]]
name = "csscolorparser"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
version = "0.6.2"
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"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
checksum = "eb2a7d3066da2de787b7f032c736763eb7ae5d355f81a68bab2675a96008b0bf"
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
dependencies = [
add wezterm.color module for working with colors wezterm.color.parse() returns a color object that can be assigned in the wezterm color config, and that can be used to adjust hue, saturation and lightness, as well as calculate harmonizing colors (complements, triads, squares) from the RGB/HSL color wheel.
2022-07-11 09:41:18 +03:00
"lab",
cargo update
2022-08-15 08:27:23 +03:00
"phf 0.11.1",
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
]
[[package]]
name = "csv"
cargo update
2023-03-13 06:22:05 +03:00
version = "1.2.1"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "0b015497079b9a9d69c02ad25de6c0a6edef051ea6360a327d0bd05802ef64ad"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
dependencies = [
"csv-core",
cargo update
2023-02-17 21:30:15 +03:00
"itoa",
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
"ryu",
"serde",
]
[[package]]
name = "csv-core"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2b2466559f260f48ad25fe6317b3c8dac77b5bdb5763ac7d9d6103530663bc90"
dependencies = [
"memchr",
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
]
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "cxx"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.93"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "a9c00419335c41018365ddf7e4d5f1c12ee3659ddcf3e01974650ba1de73d038"
cargo update
2022-10-10 06:26:07 +03:00
dependencies = [
"cc",
"cxxbridge-flags",
"cxxbridge-macro",
"link-cplusplus",
]
[[package]]
name = "cxx-build"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.93"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "fb8307ad413a98fff033c8545ecf133e3257747b3bae935e7602aab8aa92d4ca"
cargo update
2022-10-10 06:26:07 +03:00
dependencies = [
"cc",
"codespan-reporting",
"once_cell",
"proc-macro2",
"quote",
"scratch",
cargo update
2023-03-20 06:20:34 +03:00
"syn 2.0.2",
cargo update
2022-10-10 06:26:07 +03:00
]
[[package]]
name = "cxxbridge-flags"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.93"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "edc52e2eb08915cb12596d29d55f0b5384f00d697a646dbd269b6ecb0fbd9d31"
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "cxxbridge-macro"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.93"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "631569015d0d8d54e6c241733f944042623ab6df7bc3be7466874b05fcdb1c5f"
cargo update
2022-10-10 06:26:07 +03:00
dependencies = [
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 2.0.2",
cargo update
2022-10-10 06:26:07 +03:00
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "d3d12"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
version = "0.6.0"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
checksum = "d8f0de2f5a8e7bd4a9eec0e3c781992a4ce1724f68aec7d7a3715344de8b39da"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"libloading 0.7.4",
"winapi",
]
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
[[package]]
name = "darling"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.14.4"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "7b750cb3417fd1b327431a470f388520309479ab0bf5e323505daf0290cd3850"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
dependencies = [
"darling_core",
"darling_macro",
]
[[package]]
name = "darling_core"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.14.4"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "109c1ca6e6b7f82cc233a97004ea8ed7ca123a9af07a8230878fcfda9b158bf0"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
dependencies = [
"fnv",
"ident_case",
"proc-macro2",
"quote",
"strsim",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
]
[[package]]
name = "darling_macro"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.14.4"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "a4aab4dbc9f7611d8b55048a3a16d2d010c2c8334e46304b40ac1cc14bf3b48e"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
dependencies = [
"darling_core",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
]
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
[[package]]
name = "dashmap"
cargo update
2022-09-04 04:54:36 +03:00
version = "5.4.0"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-09-04 04:54:36 +03:00
checksum = "907076dfda823b0b36d2a1bb5f90c96660a5bbcd7729e10727f07858f22c4edc"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
"hashbrown 0.12.3",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"lock_api",
cargo update
2022-09-04 04:54:36 +03:00
"once_cell",
cargo update
2023-02-06 07:53:11 +03:00
"parking_lot_core 0.9.7",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "data-encoding"
cargo update
2022-12-12 19:02:19 +03:00
version = "2.3.3"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-12 19:02:19 +03:00
checksum = "23d8666cb01533c39dde32bcbab8e227b4ed6679b2c925eba05feabea39508fb"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
lua: add wezterm.color.extract_colors_from_image This function can be used to extra distinct colors from an image to be fed into eg: color scheme generation.
2022-07-11 21:03:06 +03:00
[[package]]
name = "deltae"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e412cd91a4ec62fcc739ea50c40babe21e3de60d69f36393cce377c7c04ead5a"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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
]
Add support for heap profiling using dhat refs: https://github.com/wez/wezterm/issues/2626
2022-11-14 23:26:02 +03:00
[[package]]
name = "dhat"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4f2aaf837aaf456f6706cb46386ba8dffd4013a757e36f4ea05c20dd46b209a3"
dependencies = [
"backtrace",
"lazy_static",
"mintex",
"parking_lot 0.12.1",
"rustc-hash",
"serde",
"serde_json",
"thousands",
]
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"
cargo update
2022-07-04 08:48:58 +03:00
version = "0.1.13"
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
2022-07-04 08:48:58 +03:00
checksum = "56254986775e3233ffa9c4d7d3faaf6d36a2c09d30b20687e9f88bc8bafc16c8"
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
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"
cargo update
2022-08-01 06:14:19 +03:00
version = "0.9.0"
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
2022-08-01 06:14:19 +03:00
checksum = "d3dd60d1080a57a05ab032377049e0591415d2b31afd7028356dbf3cc6dcb066"
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 = [
cargo update
2022-08-01 06:14:19 +03:00
"generic-array",
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"
cargo update
2022-11-21 08:18:37 +03:00
version = "0.10.6"
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
2022-11-21 08:18:37 +03:00
checksum = "8168378f4e5023e7218c89c891c0fd8ecdb5e5e4f18cb78f38cf245dd021e76f"
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 = [
cargo update
2023-03-13 06:22:05 +03:00
"block-buffer 0.10.4",
cargo update
2022-08-01 06:14:19 +03:00
"crypto-common",
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
]
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
[[package]]
name = "dirs"
version = "4.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ca3aa72a6f96ea37bbc5aa912f6788242832f75369bdfdadcb0e38423f100059"
dependencies = [
"dirs-sys",
]
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 = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
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-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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
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-11-07 04:51:07 +03:00
"libloading 0.7.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
]
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
[[package]]
name = "either"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "1.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"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "7fcaabb2fef8c910e7f4c7ce9f67a1283a1715879a7c230ca9d6d1ae31f16d91"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-12-12 19:02:19 +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-12-12 19:02:19 +03:00
checksum = "e62abb876c07e4754fae5c14cafa77937841f01740637e17d78dc04352f32a5e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"rustc_version",
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
"toml 0.5.11",
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
]
Add CharSelect modal for emoji/nerdfont/unicode input CTRL-SHIFT-U is a new default key assignment for this new modal. It opens up a fuzzy searchable browser that defaults to showing emoji/emoticons. The category can by cycled through the suggested emoji categories using CTRL-r. Unlike the system emoji palette, wezterm includes a category for nerdfont symbols, and another that is a list of all unicode codepoint names, so you should be able to browse for pretty much any codepoint you can think of. The modal also allows fuzzy searching based on: * The official unicode name * The github shortcode * codepoint value in hex so if you know the codepoint value but not the name, you can still find a way to input what you're looking for. Pressing Enter will copy the selected item to the clipboard send it to the active pane, and cancel the modal. You can therefore repeat the insert by simply pasting. I plan to add frecency to this in a later commit: that way the frequently/recently used selections will show in a category of their own and make it easier to re-input them. refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 04:15:28 +03:00
[[package]]
name = "emojis"
cargo update
2022-11-28 07:32:51 +03:00
version = "0.5.2"
Add CharSelect modal for emoji/nerdfont/unicode input CTRL-SHIFT-U is a new default key assignment for this new modal. It opens up a fuzzy searchable browser that defaults to showing emoji/emoticons. The category can by cycled through the suggested emoji categories using CTRL-r. Unlike the system emoji palette, wezterm includes a category for nerdfont symbols, and another that is a list of all unicode codepoint names, so you should be able to browse for pretty much any codepoint you can think of. The modal also allows fuzzy searching based on: * The official unicode name * The github shortcode * codepoint value in hex so if you know the codepoint value but not the name, you can still find a way to input what you're looking for. Pressing Enter will copy the selected item to the clipboard send it to the active pane, and cancel the modal. You can therefore repeat the insert by simply pasting. I plan to add frecency to this in a later commit: that way the frequently/recently used selections will show in a category of their own and make it easier to re-input them. refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 04:15:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-28 07:32:51 +03:00
checksum = "44fe60b864b6544ad211d4053ced474a9b9d2c8d66b77f01d6c6bcfed10c6bf0"
deps: update emojis crate
2022-10-04 19:00:18 +03:00
dependencies = [
"phf 0.11.1",
]
Add CharSelect modal for emoji/nerdfont/unicode input CTRL-SHIFT-U is a new default key assignment for this new modal. It opens up a fuzzy searchable browser that defaults to showing emoji/emoticons. The category can by cycled through the suggested emoji categories using CTRL-r. Unlike the system emoji palette, wezterm includes a category for nerdfont symbols, and another that is a list of all unicode codepoint names, so you should be able to browse for pretty much any codepoint you can think of. The modal also allows fuzzy searching based on: * The official unicode name * The github shortcode * codepoint value in hex so if you know the codepoint value but not the name, you can still find a way to input what you're looking for. Pressing Enter will copy the selected item to the clipboard send it to the active pane, and cancel the modal. You can therefore repeat the insert by simply pasting. I plan to add frecency to this in a later commit: that way the frequently/recently used selections will show in a category of their own and make it easier to re-input them. refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 04:15:28 +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
2023-02-06 07:53:11 +03:00
version = "0.8.32"
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
2023-02-06 07:53:11 +03:00
checksum = "071a31f4ee85403370b58aca746f01041ede6f0da2730960ad001edc2b71b394"
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 = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
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
]
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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
]
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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",
add wezterm.color module for working with colors wezterm.color.parse() returns a color object that can be assigned in the wezterm color config, and that can be used to adjust hue, saturation and lightness, as well as calculate harmonizing colors (complements, triads, squares) from the RGB/HSL color wheel.
2022-07-11 09:41:18 +03:00
"color-funcs",
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
"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 wezterm.json_parse and wezterm.json_encode
2022-07-10 19:30:54 +03:00
"json",
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",
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
"mux-lua",
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",
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
"plugin",
lua: add wezterm.procinfo module
2022-07-16 18:49:58 +03:00
"procinfo-funcs",
lua: add wezterm.GLOBAL
2022-06-19 07:31:53 +03:00
"share-data",
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",
lua: add wezterm.time and Time object Includes a method for determining sunrise/sunset.
2022-07-17 21:38:02 +03:00
"time-funcs",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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"
env_logger -> 0.10 closes: https://github.com/wez/wezterm/pull/2803
2022-11-28 07:37:25 +03:00
version = "0.10.0"
Enable timestamps in the logger
2020-02-14 20:46:19 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
env_logger -> 0.10 closes: https://github.com/wez/wezterm/pull/2803
2022-11-28 07:37:25 +03:00
checksum = "85cdab6a89accf66733ad5a1693a4dcced6aeff64602b634530dd73c1f3ee9f0"
Enable timestamps in the logger
2020-02-14 20:46:19 +03:00
dependencies = [
"humantime",
env_logger -> 0.10 closes: https://github.com/wez/wezterm/pull/2803
2022-11-28 07:37:25 +03:00
"is-terminal",
Enable timestamps in the logger
2020-02-14 20:46:19 +03:00
"log",
"regex",
"termcolor",
]
cargo update
2022-11-28 07:32:51 +03:00
[[package]]
name = "errno"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f639046355ee4f37944e44f60642c6f3a7efa3cf6b78c78a0d989a8ce6c396a1"
dependencies = [
"errno-dragonfly",
"libc",
"winapi",
]
[[package]]
name = "errno-dragonfly"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa68f1b12764fab894d2755d2518754e71b4fd80ecfb822714a1206c2aab39bf"
dependencies = [
"cc",
"libc",
]
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-08-01 06:14:19 +03:00
version = "2.5.3"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-08-01 06:14:19 +03:00
checksum = "0206175f82b8d6bf6652ff7d71a1e27fd2e4efde587fd368662814d6ec1d9ce0"
cargo update
2020-09-09 19:31:37 +03:00
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
[[package]]
name = "exr"
cargo update
2023-03-13 06:22:05 +03:00
version = "1.6.3"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "bdd2162b720141a91a054640662d3edce3d50a944a50ffca5313cd951abb35b4"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
dependencies = [
"bit_field",
"flume",
cargo update
2023-01-16 07:48:20 +03:00
"half 2.2.1",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"lebe",
cargo update
2022-10-10 06:26:07 +03:00
"miniz_oxide 0.6.2",
cargo update
2023-03-13 06:22:05 +03:00
"rayon-core",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"smallvec",
cargo update
2023-02-06 07:53:11 +03:00
"zune-inflate",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "fallible-iterator"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4443176a9f2c162692bd3d352d745ef9413eec5782a80d8fd6f8a1ac692a07f7"
[[package]]
name = "fallible-streaming-iterator"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7360491ce676a36bf9bb3c56c1aa791658183a54d2744120f27285738d90465a"
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "fastrand"
cargo update
2023-02-17 21:30:15 +03:00
version = "1.9.0"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "e51093e27b0797c359783294ca4f0a911c270184cb10f85783b118614a1501be"
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"
Image decoding is now done in a bg thread Continuing from the previous commit, this shifts: * In-memory data -> temporary file * Image decoding -> background thread The background thread asynchronously decodes frames and sends them to the render thread via a bounded channel. While decoding frames, it writes them, uncompressed, to a scratch file so that when the animation loops, it is a very cheap operation to rewind and pull that data from the file, without having to burn CPU to re-decode the data from the start. Memory usage is bounded to 4 uncompressed frames while decoding, then 3 uncompressed frames (triple buffered) while looping over the rest. However, disk usage is N uncompressed frames. refs: https://github.com/wez/wezterm/issues/3263
2023-03-17 21:11:46 +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
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2023-02-09 07:25:41 +03:00
version = "0.2.20"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-09 07:25:41 +03:00
checksum = "8a3de6e8d11b22ff9edc6d916f890800597d60f8b2da1caf2955c274638d6412"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +03:00
"cfg-if",
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: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"redox_syscall",
cargo update
2023-02-09 07:25:41 +03:00
"windows-sys 0.45.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
]
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
[[package]]
name = "finl_unicode"
deps: upgrade finl_unicode to 1.2
2022-10-23 22:07:00 +03:00
version = "1.2.0"
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: upgrade finl_unicode to 1.2
2022-10-23 22:07:00 +03:00
checksum = "8fcfdc7a0362c9f4444381a9e697c79d435fe65b52a37466fc2c1184cee9edc6"
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
termwiz: add clustered line storage for line Adds the option to use an alternative clusted line storage for the cells component of the line. This structure is not optimal for mutation, but is better structured for: * matching/extracting textual content * using less memory than the prior simple vector For some contrast: the line "hello" occupies 5 Cells in the cell based storage; that 5 discrete Cells each with their own tiny string and a copy of their attributes. The clustered version of the line stores one copy of the cell attributes, the string "hello" and some small (almost constant size) overhead for some metadata. For simple lines of ascii text, the clustered version is smaller as there are fewer copies of the cell attributes. Over the span of a large scrollback and typical terminal display composition, this saving is anticipated to be significant. The clustered version is also cheaper to search as it doesn't require building a copy of the search text for each line (provided the line is already in clustered form). This commit introduces the capability: none of the internals request the new form yet, and there are likely a few call sites that need to be tweaked to avoid coersion from clustered to vector form.
2022-07-23 21:51:55 +03:00
[[package]]
name = "fixedbitset"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ce7134b9999ecaf8bcd65542e436736ef32ddca1b3e06094cb6ec5755203b80"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2022-11-28 07:32:51 +03:00
version = "1.0.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-11-28 07:32:51 +03:00
checksum = "a8a2db397cb1c8772f31494cb8917e48cd1e64f0fa7efac59fbd741a0a8ce841"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"crc32fast",
cargo update
2022-11-28 07:32:51 +03:00
"miniz_oxide 0.6.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 = "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"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
version = "0.10.14"
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"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
checksum = "1657b4441c3403d9f7b3409e47575237dac27b1b5726df654a6ecbf92f0f7577"
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",
cargo update
2023-03-17 22:02:21 +03:00
"spin 0.9.6",
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
2022-09-12 16:26:10 +03:00
version = "1.1.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"
cargo update
2022-09-12 16:26:10 +03:00
checksum = "a9c384f161156f5260c24a097c56119f9be8c798586aecc13afbcbe7b7e26bf8"
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 = [
"percent-encoding",
]
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
[[package]]
name = "frecency"
version = "0.1.0"
dependencies = [
"chrono",
"serde",
"serde_json",
"serde_with",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-sys"
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
version = "4.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: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
checksum = "76ee7a02da4d231650c7cea31349b889be2f45ddb3ef3032d2ec8185f6313fd2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "futures"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "531ac96c6ff5fd7c62263c5e3c67a603af4fcaee2e1a0ae5565ba3a11e69e549"
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "164713a5a0dcc3e7b4b1ed7d3b433cabc18025386f9339346e8daf15963cf7ac"
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "86d7a0c1aa76363dac491de0ee99faf6941128376f1cf96f07db7603b7de69dd"
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "1997dd9df74cdac935c76252744c1ed5794fac083242ea4fe77ef3ed60ba0f83"
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "89d422fa3cbe3b40dca574ab087abb5bc98258ea57eea3fd6f1fa7162c778b91"
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "3eb14ed937631bd8b8b8977f2c198443447a8355b6e3ca599f38c975e5a963b6"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "ec93083a4aecafb2a80a885c9de1f0ccae9dbd32c2bb54b0c3a65690e0b8d2f2"
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "fd65540d33b37b16542a0438c12e6aeead10d4ac5d05bd3f805b8f35ab592879"
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"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.3.27"
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
2023-03-13 06:22:05 +03:00
checksum = "3ef6b17e481503ec85211fed8f39d1970f128935ca1f814cd32ac4a6842e84ab"
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",
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "fxhash"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c31b6d751ae2c7f11320402d34e41349dd1016f8d5d45e48c4312bc8625af50c"
dependencies = [
"byteorder",
]
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",
]
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
2022-08-08 05:31:29 +03:00
version = "0.14.6"
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
2022-08-08 05:31:29 +03:00
checksum = "bff49e947297f3312447abdca79f45f4738097cc82b06e72054d2223f601f1b9"
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",
]
ssh: support %l and %L in config files We also log a warning when an unsupported token is used. refs: https://github.com/wez/wezterm/issues/3176
2023-03-02 04:44:11 +03:00
[[package]]
name = "gethostname"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8a329e22866dd78b35d2c639a4a23d7b950aeae300dfd79f4fb19f74055c2404"
dependencies = [
"libc",
"windows 0.43.0",
]
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",
]
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 = "getrandom"
cargo update
2022-10-23 22:08:11 +03:00
version = "0.2.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"
cargo update
2022-10-23 22:08:11 +03:00
checksum = "c05aeb6a22b8f62540c194aac980f2115af067bfe15a0734d7277a768d396b31"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
cargo update
2021-01-06 11:28:11 +03:00
"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
2022-06-20 07:40:05 +03:00
"wasi 0.11.0+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"
improve handling of animated webp images Use mainline image crate to avoid an otherwise unavoidable panic in the upstream: https://github.com/image-rs/image/issues/1775 Explicitly operate on the frames from the animation. refs: https://github.com/wez/wezterm/issues/3250
2023-03-15 21:34:47 +03:00
version = "0.12.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"
improve handling of animated webp images Use mainline image crate to avoid an otherwise unavoidable panic in the upstream: https://github.com/image-rs/image/issues/1775 Explicitly operate on the frames from the animation. refs: https://github.com/wez/wezterm/issues/3250
2023-03-15 21:34:47 +03:00
checksum = "80792593675e051cf94a4b111980da2ba60d4a83e43e0048c5693baab3977045"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-17 21:30:15 +03:00
version = "0.27.2"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "ad0a93d233ebf96623465aad4046a8d3aa4da22d4f4beba5388838c8a434bbb4"
cargo update
2020-05-26 08:25:39 +03:00
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
[[package]]
name = "git2"
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
version = "0.16.1"
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
checksum = "ccf7f68c2995f392c49fffb4f95ae2c873297830eb25c6bc4c114ce8f4562acc"
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
"libc",
"libgit2-sys",
"log",
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
"openssl-probe",
"openssl-sys",
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
"url",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"memoffset 0.6.5",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"smallvec",
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"
cargo update
2023-01-08 17:46:31 +03:00
version = "0.4.10"
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
2023-01-08 17:46:31 +03:00
checksum = "029d74589adefde59de1a0c4f4732695c32805624aec7b68d91503d4dba79afc"
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 = [
"aho-corasick",
cargo update
2023-03-20 06:20:34 +03:00
"bstr 1.4.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
"fnv",
"log",
"regex",
]
[[package]]
name = "globwalk"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "93e3af942408868f6934a7b85134a3230832b9977cf66125df2f9edcfce4ddcc"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.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
"ignore",
"walkdir",
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "glow"
cargo update
2023-02-27 08:32:52 +03:00
version = "0.12.1"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-27 08:32:52 +03:00
checksum = "4e007a07a24de5ecae94160f141029e9a347282cfe25d1d58d85d845cf3130f1"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"js-sys",
"slotmap",
"wasm-bindgen",
"web-sys",
]
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
[[package]]
name = "governor"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "19775995ee20209163239355bc3ad2f33f83da35d9ef72dea26e5af753552c87"
dependencies = [
"dashmap",
"futures",
"futures-timer",
"no-std-compat",
"nonzero_ext",
"parking_lot 0.12.1",
"quanta",
cargo update
2023-01-16 07:48:20 +03:00
"rand",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"smallvec",
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "gpu-alloc"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7fc59e5f710e310e76e6707f86c561dd646f69a8876da9131703b2f717de818d"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"gpu-alloc-types",
]
[[package]]
name = "gpu-alloc-types"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "54804d0d6bc9d7f26db4eaec1ad10def69b599315f487d32c334a80d1efe67a5"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
]
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
[[package]]
name = "gpu-allocator"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.22.0"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "ce95f9e2e11c2c6fadfce42b5af60005db06576f231f5c92550fdded43c423e8"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
dependencies = [
"backtrace",
"log",
"thiserror",
"winapi",
cargo update
2023-02-17 21:30:15 +03:00
"windows 0.44.0",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "gpu-descriptor"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0b0c02e1ba0bdb14e965058ca34e09c020f8e507a760df1121728e0aef68d57a"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"gpu-descriptor-types",
"hashbrown 0.12.3",
]
[[package]]
name = "gpu-descriptor-types"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "363e3677e55ad168fef68cf9de3a4a310b53124c5e784c53a1d70e92d23f2126"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +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 = "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",
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "h2"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.3.16"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "5be7b54589b581f624f566bf5d8eb2bab1db736c51528720b6bd36b96b55924d"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
"bytes",
"fnv",
"futures-core",
"futures-sink",
"futures-util",
"http",
"indexmap",
"slab",
"tokio",
"tokio-util",
"tracing",
]
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"
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "half"
cargo update
2023-01-16 07:48:20 +03:00
version = "2.2.1"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-16 07:48:20 +03:00
checksum = "02b4af3693f1b705df946e9fe5631932443781d0aabb423b62fcd4d73f6d2fd0"
cargo update
2022-10-10 06:26:07 +03:00
dependencies = [
"crunchy",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
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 = [
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"ahash 0.7.6",
cargo update
2021-08-02 04:40:25 +03:00
]
cargo update
2021-07-07 23:27:08 +03:00
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
[[package]]
name = "hashbrown"
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
version = "0.12.3"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
checksum = "8a9ee70c43aaf417c914396645a0fa852624801b24ebb7ae78fe8272889ac888"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
dependencies = [
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"ahash 0.7.6",
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
]
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "hashlink"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7249a3129cbc1ffccd74857f81464a323a152173cdb134e0fd81bc803b29facf"
dependencies = [
"hashbrown 0.11.2",
]
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
[[package]]
name = "hassle-rs"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90601c6189668c7345fc53842cb3f3a3d872203d523be1b3cb44a36a3e62fb85"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"com-rs",
"libc",
"libloading 0.7.4",
"thiserror",
"widestring",
"winapi",
]
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
[[package]]
name = "hdrhistogram"
cargo update
2022-09-19 06:00:54 +03:00
version = "7.5.2"
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-09-19 06:00:54 +03:00
checksum = "7f19b9f54f7c7f55e31401bb647626ce0cf0f67b0004982ce815b3ee72a02aa8"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
dependencies = [
deps: update base64 closes: https://github.com/wez/wezterm/pull/2855
2022-12-12 19:14:42 +03:00
"base64 0.13.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
"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",
cargo update
2023-01-16 07:48:20 +03:00
"nom 7.1.3",
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
2023-02-06 07:53:11 +03:00
version = "0.4.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
2023-02-06 07:53:11 +03:00
checksum = "95505c38b4572b2d910cecb0281560f54b440a19336cbbcb27bf6ce6adc6f5a8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
cargo update
2022-11-28 07:32:51 +03:00
[[package]]
name = "hermit-abi"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ee512640fe35acbfb4bb779db6f0d80704c2cacfa2e39b601ef3e3f47d1ae4c7"
dependencies = [
"libc",
]
cargo update
2023-02-06 07:53:11 +03:00
[[package]]
name = "hermit-abi"
cargo update
2023-02-09 07:25:41 +03:00
version = "0.3.1"
cargo update
2023-02-06 07:53:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-09 07:25:41 +03:00
checksum = "fed44880c466736ef9a5c5b5facefb5ed0785676d0c02d612db14e54f0d84286"
cargo update
2023-02-06 07:53:11 +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"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "hexf-parse"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "dfa686283ad6dd069f105e5ab091b04c62850d3e4cf5d67debad1933f55023df"
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "http"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.2.9"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "bd6effc99afb63425aff9b05836f029929e345a6148a14b7ecd5ab67af944482"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
"bytes",
"fnv",
cargo update
2023-02-17 21:30:15 +03:00
"itoa",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
]
[[package]]
name = "http-body"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d5f38f16d184e36f2408a55281cd658ecbd3ca05cce6d6510a176eca393e26d1"
dependencies = [
"bytes",
"http",
"pin-project-lite",
]
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"
deps: http_req -> 0.9
2023-02-05 17:38:55 +03:00
version = "0.9.0"
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: http_req -> 0.9
2023-02-05 17:38:55 +03:00
checksum = "ba2b47a95070b135fd0e17a307ab18af91e15d4df99cc59e046fafb904404926"
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",
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "httparse"
cargo update
2022-09-04 04:54:36 +03:00
version = "1.8.0"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-09-04 04:54:36 +03:00
checksum = "d897f394bad6a705d5f4104762e116a75639e470d80901eed05a860a95cb1904"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "httpdate"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c4a1e36c821dbe04574f602848a19f742f4fb3c98d40449f11bcad18d6b17421"
term: improve readability of error message for oversized image refs: https://github.com/wez/wezterm/issues/3264
2023-03-17 08:41:52 +03:00
[[package]]
name = "humansize"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6cb51c9a029ddc91b07a787f1d86b53ccfa49b0e86688c946ebe8d3555685dd7"
dependencies = [
"libm",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "hyper"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.14.25"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "cc5e554ff619822309ffd57d8734d77cd5ce6238bc956f037ea06c58238c9899"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
"bytes",
"futures-channel",
"futures-core",
"futures-util",
"h2",
"http",
"http-body",
"httparse",
"httpdate",
cargo update
2023-02-17 21:30:15 +03:00
"itoa",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"pin-project-lite",
cargo update
2023-03-06 08:18:33 +03:00
"socket2 0.4.9",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"tokio",
"tower-service",
"tracing",
"want",
]
[[package]]
name = "hyper-tls"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d6183ddfa99b85da61a140bea0efc93fdf56ceaa041b37d553518030827f9905"
dependencies = [
"bytes",
"hyper",
"native-tls",
"tokio",
"tokio-native-tls",
]
cargo update
2022-08-15 08:27:23 +03:00
[[package]]
name = "iana-time-zone"
deps: cargo update
2022-11-01 17:09:37 +03:00
version = "0.1.53"
cargo update
2022-08-15 08:27:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-11-01 17:09:37 +03:00
checksum = "64c122667b287044802d6ce17ee2ddf13207ed924c712de9a66a5814d5b64765"
cargo update
2022-08-15 08:27:23 +03:00
dependencies = [
"android_system_properties",
"core-foundation-sys 0.8.3",
cargo update
2022-10-10 06:26:07 +03:00
"iana-time-zone-haiku",
cargo update
2022-08-15 08:27:23 +03:00
"js-sys",
"wasm-bindgen",
"winapi",
]
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "iana-time-zone-haiku"
cargo update
2022-10-17 06:57:48 +03:00
version = "0.1.1"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-10-17 06:57:48 +03:00
checksum = "0703ae284fc167426161c2e3f1da3ea71d94b21bedbcc9494e92b28e334e3dca"
cargo update
2022-10-10 06:26:07 +03:00
dependencies = [
"cxx",
"cxx-build",
]
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
[[package]]
name = "ident_case"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b9e0384b61958566e926dc50660321d12159025e767c18e043daf26b70104c39"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "idna"
cargo update
2022-09-12 16:26:10 +03:00
version = "0.3.0"
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-09-12 16:26:10 +03:00
checksum = "e14ddfc70884202db2244c223200c204c2bda1bc6e0998d11b5e024d657209e6"
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
"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"
cargo update
2023-01-16 07:48:20 +03:00
version = "0.4.20"
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
2023-01-16 07:48:20 +03:00
checksum = "dbe7873dab538a9a44ad79ede1faf5f30d49f9a5c883ddbab48bce81b64b7492"
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 = [
"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-11-14 04:24:31 +03:00
version = "0.24.5"
improve handling of animated webp images Use mainline image crate to avoid an otherwise unavoidable panic in the upstream: https://github.com/image-rs/image/issues/1775 Explicitly operate on the frames from the animation. refs: https://github.com/wez/wezterm/issues/3250
2023-03-15 21:34:47 +03:00
source = "git+https://github.com/image-rs/image.git?rev=fe069785ae245a2c510fd724ef96da283b05a236#fe069785ae245a2c510fd724ef96da283b05a236"
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",
cargo update
2022-06-27 06:40:48 +03:00
"num-rational 0.4.1",
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",
improve handling of animated webp images Use mainline image crate to avoid an otherwise unavoidable panic in the upstream: https://github.com/image-rs/image/issues/1775 Explicitly operate on the frames from the animation. refs: https://github.com/wez/wezterm/issues/3250
2023-03-15 21:34:47 +03:00
"qoi",
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: structopt -> clap 3
2022-05-28 17:07:52 +03:00
[[package]]
name = "indexmap"
cargo update
2022-11-21 08:18:37 +03:00
version = "1.9.2"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-21 08:18:37 +03:00
checksum = "1885e79c1fc4b10f0e172c475f458b7f7b93061064d98c3293e98c5ba0c8b399"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
dependencies = [
"autocfg",
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
"hashbrown 0.12.3",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
"serde",
deps: structopt -> clap 3
2022-05-28 17:07: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 = "inotify"
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
version = "0.9.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"
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
checksum = "f8069d3ec154eb856955c1c0fbffefbf5f3c40a104ec912d4797314c1801abff"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 1.3.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
"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
2023-01-16 07:48:20 +03:00
"cfg-if",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
]
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
[[package]]
name = "intrusive-collections"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "0.9.5"
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "3f4f90afb01281fdeffb0f8e082d230cbe4f888f837cc90759696b858db1a700"
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
dependencies = [
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
"memoffset 0.8.0",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
]
cargo update
2022-11-28 07:32:51 +03:00
[[package]]
name = "io-lifetimes"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.8"
cargo update
2022-11-28 07:32:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "0dd6da19f25979c7270e70fa95ab371ec3b701cd0eefc47667a09785b3c59155"
cargo update
2022-11-28 07:32:51 +03:00
dependencies = [
cargo update
2023-03-17 22:02:21 +03:00
"hermit-abi 0.3.1",
cargo update
2022-11-28 07:32:51 +03:00
"libc",
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.45.0",
cargo update
2022-11-28 07:32: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 = "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
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "ipnet"
update base64, work around another batch of breaking API changes closes: https://github.com/wez/wezterm/pull/2931
2023-01-09 04:49:45 +03:00
version = "2.7.1"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
update base64, work around another batch of breaking API changes closes: https://github.com/wez/wezterm/pull/2931
2023-01-09 04:49:45 +03:00
checksum = "30e22bd8629359895450b59ea7a776c850561b96a3b1d31321c1949d9e6c9146"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
cargo update
2022-11-28 07:32:51 +03:00
[[package]]
name = "is-terminal"
cargo update
2023-03-20 06:20:34 +03:00
version = "0.4.5"
cargo update
2022-11-28 07:32:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "8687c819457e979cc940d09cb16e42a1bf70aa6b60a549de6d3a62a0ee90c69e"
cargo update
2022-11-28 07:32:51 +03:00
dependencies = [
cargo update
2023-02-09 07:25:41 +03:00
"hermit-abi 0.3.1",
cargo update
2022-11-28 07:32:51 +03:00
"io-lifetimes",
"rustix",
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.45.0",
cargo update
2022-11-28 07:32:51 +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
2022-09-27 17:11:12 +03:00
version = "0.10.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-09-27 17:11:12 +03:00
checksum = "b0fd2260e829bddf4cb6ea802289de2f86d6a7a690192fbe91b3f46e0f2c8473"
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
2023-03-06 08:18:33 +03:00
version = "1.0.6"
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
2023-03-06 08:18:33 +03:00
checksum = "453ad9f582a441959e5f0d088b02ce04cfe8d51a8eaf077f12ac6d3e94164ca6"
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
2023-03-06 08:18:33 +03:00
version = "0.1.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
2023-03-06 08:18:33 +03:00
checksum = "936cfd212a0155903bcbc060e316fb6cc7cbf2e1907329391ebadc1fe0ce77c2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2022-11-14 04:24:31 +03:00
version = "0.3.0"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-14 04:24:31 +03:00
checksum = "bc0000e42512c92e31c2252315bda326620a4e034105e900c98ec492fa077b3e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-06 07:53:11 +03:00
version = "0.3.61"
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
2023-02-06 07:53:11 +03:00
checksum = "445dde2150c55e483f3d8416706b97ec8e8237c307e5b7b4b8dd15e6af2a0730"
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",
]
add wezterm.json_parse and wezterm.json_encode
2022-07-10 19:30:54 +03:00
[[package]]
name = "json"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"luahelper",
"serde_json",
]
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
2022-10-17 06:57:48 +03:00
version = "0.11.6"
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
2022-10-17 06:57:48 +03:00
checksum = "32ddb58b0079a063218472916af599f2753ccb40942cdaba9d1f3fefccef17a9"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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",
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "khronos-egl"
version = "4.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8c2352bd1d0bceb871cb9d40f24360c8133c11d7486b68b5381c1dd1a32015e3"
dependencies = [
"libc",
"libloading 0.7.4",
"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]]
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
name = "khronos_api"
version = "3.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e2db585e1d738fc771bf08a151420d3ed193d9d895a36df7f6f8a9456b911ddc"
[[package]]
name = "kqueue"
cargo update
2022-10-17 06:57:48 +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
2022-10-17 06:57:48 +03:00
checksum = "2c8fc60ba15bf51257aa9807a48a61013db043fcf3a78cb0d916e8e396dcad98"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"kqueue-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]]
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
name = "kqueue-sys"
version = "1.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"
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
checksum = "8367585489f01bc55dd27404dcf56b95e6da061a256a666ab23be9ba96a2e587"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +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 wezterm.color module for working with colors wezterm.color.parse() returns a color object that can be assigned in the wezterm color config, and that can be used to adjust hue, saturation and lightness, as well as calculate harmonizing colors (complements, triads, squares) from the RGB/HSL color wheel.
2022-07-11 09:41:18 +03:00
[[package]]
name = "lab"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bf36173d4167ed999940f804952e6b08197cae5ad5d572eb4db150ce8ad5d58f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2022-08-21 18:51:16 +03:00
version = "0.5.2"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-08-21 18:51:16 +03:00
checksum = "03087c2bad5e1034e8cace5926dec053fb3790248370865f5117a7d0213354c8"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
refactor: move lfucache into its own crate
2022-11-14 06:20:15 +03:00
[[package]]
name = "lfucache"
version = "0.1.0"
dependencies = [
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
"ahash 0.8.3",
refactor: move lfucache into its own crate
2022-11-14 06:20:15 +03:00
"config",
"fnv",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"intrusive-collections",
"k9",
refactor: move lfucache into its own crate
2022-11-14 06:20:15 +03:00
"metrics",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-13 06:22:05 +03:00
version = "0.2.140"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-13 06:22:05 +03:00
checksum = "99227334921fae1a979cf0bfdfcc6b3e5ce376ef57e16fb6fb3ea2ed6095f80c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
[[package]]
name = "libflate"
cargo update
2023-02-17 21:30:15 +03:00
version = "1.3.0"
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "97822bf791bd4d5b403713886a5fbe8bf49520fe78e323b0dc480ca1a03e50b0"
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
dependencies = [
"adler32",
"crc32fast",
"libflate_lz77",
]
[[package]]
name = "libflate_lz77"
cargo update
2023-02-17 21:30:15 +03:00
version = "1.2.0"
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "a52d3a8bfc85f250440e4424db7d857e241a3aebbbe301f3eb606ab15c39acbf"
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
dependencies = [
"rle-decode-fast",
]
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
[[package]]
name = "libgit2-sys"
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
version = "0.14.2+1.5.1"
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
checksum = "7f3d95f6b51075fe9810a7ae22c7095f12b98005ab364d8544797a825ce946a4"
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
dependencies = [
"cc",
"libc",
"libz-sys",
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
"openssl-sys",
config: avoid rebuilding when git index changes Focus instead on the head and check whether a commit is made.
2022-05-22 19:01:09 +03:00
"pkg-config",
]
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
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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-11-07 04:51:07 +03:00
version = "0.7.4"
cargo update
2021-03-01 20:02:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-11-07 04:51:07 +03:00
checksum = "b67380fd3b2fbe7527a606e18729d21c6f3951633d0500574c4dc22d2d638b9f"
cargo update
2021-03-01 20:02:05 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
cargo update
2021-03-01 20:02:05 +03:00
]
term: improve readability of error message for oversized image refs: https://github.com/wez/wezterm/issues/3264
2023-03-17 08:41:52 +03:00
[[package]]
name = "libm"
version = "0.2.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "348108ab3fba42ec82ff6e9564fc4ca0247bdccdc68dd8af9764bbc79c3c8ffb"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "libsqlite3-sys"
version = "0.24.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "898745e570c7d0453cc1fbc4a701eb6c662ed54e8fec8b7d14be137ebeeb9d14"
dependencies = [
"cc",
"pkg-config",
"vcpkg",
]
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: detect exit-signal state for channels Need to use a newer version of libssh-rs that can report this state, as the underlying libssh doesn't fold it into the process exit status. refs: https://github.com/wez/wezterm/issues/3095
2023-02-11 20:01:11 +03:00
version = "0.1.5"
cargo update
2023-03-17 22:02:21 +03:00
source = "git+https://github.com/wez/libssh-rs.git#c48876e7027d3c21747a283be631177aad533eff"
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
ssh: introduce wrapper enum This is a pre-cursor step to adding libssh support
2021-10-13 06:50:00 +03:00
"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"
cargo update
2023-03-17 22:02:21 +03:00
source = "git+https://github.com/wez/libssh-rs.git#c48876e7027d3c21747a283be631177aad533eff"
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"
cargo update
2023-01-23 08:02:26 +03:00
version = "0.3.0"
ssh: my openssl+windows ssh2 patch was published upstream So remove my local patch
2021-10-10 17:29:54 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-23 08:02:26 +03:00
checksum = "2dc8a030b787e2119a731f1951d6a773e2280c660f8ec4b0f5e1505a386e71ee"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
x11: subscribe to Present extension configure notify events The hope here is that the nvidia-specific resize issue might have a workaround if it is emitting some other events that we were previously not listening for. This commit optionally enables the Present extension and listens for its version of CONFIGURE_NOTIFY, routing it through the same logic as the base CONFIGURE_NOTIFY event. On my AMD hardware under Gnome, I see something like: ``` 18:04:26.476 TRACE window::os::x11::window > Present::ConfigureNotify: width 1168 -> 1180, height 858 -> 873, dpi 124.7998046875 -> 124.7998046875 18:04:26.478 TRACE window::os::x11::window > Ignoring X::ConfigureNotify (1180x873 dpi=124.7998046875) because width,height,dpi are unchanged ``` with the Present event firing before the X event. Let's see how this goes. refs: #2063 refs: #1992
2022-06-04 04:08:51 +03:00
version = "1.1.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
source = "registry+https://github.com/rust-lang/crates.io-index"
x11: subscribe to Present extension configure notify events The hope here is that the nvidia-specific resize issue might have a workaround if it is emitting some other events that we were previously not listening for. This commit optionally enables the Present extension and listens for its version of CONFIGURE_NOTIFY, routing it through the same logic as the base CONFIGURE_NOTIFY event. On my AMD hardware under Gnome, I see something like: ``` 18:04:26.476 TRACE window::os::x11::window > Present::ConfigureNotify: width 1168 -> 1180, height 858 -> 873, dpi 124.7998046875 -> 124.7998046875 18:04:26.478 TRACE window::os::x11::window > Ignoring X::ConfigureNotify (1180x873 dpi=124.7998046875) because width,height,dpi are unchanged ``` with the Present event firing before the X event. Let's see how this goes. refs: #2063 refs: #1992
2022-06-04 04:08:51 +03:00
checksum = "9702761c3935f8cc2f101793272e202c72b99da8f4224a19ddcf1279a6450bbf"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
[[package]]
name = "line-wrap"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f30344350a2a51da54c1d53be93fade8a237e545dbcc4bdbe635413f2117cab9"
dependencies = [
"safemem",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "link-cplusplus"
cargo update
2022-12-19 21:13:02 +03:00
version = "1.0.8"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-19 21:13:02 +03:00
checksum = "ecd207c9c713c34f95a097a5b029ac2ce6010530c7b49d7fea24d977dede04f5"
cargo update
2022-10-10 06:26:07 +03:00
dependencies = [
"cc",
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "linked-hash-map"
version = "0.5.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0717cef1bc8b636c6e1c1bbdefc09e6322da8a9321966e8928ef80d20f7f770f"
cargo update
2022-11-28 07:32:51 +03:00
[[package]]
name = "linux-raw-sys"
cargo update
2022-12-19 21:13:02 +03:00
version = "0.1.4"
cargo update
2022-11-28 07:32:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-19 21:13:02 +03:00
checksum = "f051f77a7c8e6957c0696eac88f26b0117e54f52d3fc682ab19397a8812846a4"
cargo update
2022-11-28 07:32:51 +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-09-27 17:11:12 +03:00
version = "0.4.9"
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-09-27 17:11:12 +03:00
checksum = "435011366fe56583b16cf956f9df0095b405b82d76425bc8981c0e22e60ec4df"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
version = "0.7.8"
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"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
checksum = "e999beba7b6e8345721bd280141ed958096a2e4abdf74f67ff4ce49b4b54e47a"
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 = [
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
"hashbrown 0.12.3",
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
2023-01-16 07:48:20 +03:00
version = "210.4.5+resty2cf5186"
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
2023-01-16 07:48:20 +03:00
checksum = "27b7992a40e602786272d84c6f2beca44a588ededcfd57b48ec6f82008a7cb97"
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",
]
add wezterm-blob-leases crate
2023-03-18 22:21:30 +03:00
[[package]]
name = "mac_address"
version = "1.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b238e3235c8382b7653c6408ed1b08dd379bdb9fdf990fb0bbae3db2cc0ae963"
dependencies = [
"nix 0.23.2",
"winapi",
]
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"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
[[package]]
name = "memmap2"
cargo update
2023-02-27 08:32:52 +03:00
version = "0.5.10"
window: update smithay-client deps
2021-12-28 17:28:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-27 08:32:52 +03:00
checksum = "83faa42c0a078c393f6b29d5db232d8be22776a891f8f56e5284faee4a20b327"
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
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
[[package]]
name = "memoffset"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "0.6.5"
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "5aa361d4faea93603064a027415f07bd8e1d5c88c9fbf68bf56a285428fd79ce"
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
dependencies = [
"autocfg",
]
cargo update
2023-03-13 06:22:05 +03:00
[[package]]
name = "memoffset"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5de893c32cde5f383baa4c04c5d6dbdd735cfd4a794b0debdb2bb1b421da5ff4"
dependencies = [
"autocfg",
]
cargo update
2022-11-21 08:18:37 +03:00
[[package]]
name = "memoffset"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "0.8.0"
cargo update
2022-11-21 08:18:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "d61c719bcfbcf5d62b3a09efa6088de8c54bc0bfcd3ea7ae39fcc186108b8de1"
cargo update
2022-11-21 08:18:37 +03:00
dependencies = [
"autocfg",
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "metal"
version = "0.24.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "de11355d1f6781482d027a3b4d4de7825dcedb197bf573e0596d00008402d060"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"block",
"core-graphics-types",
"foreign-types",
"log",
"objc",
]
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 = [
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"ahash 0.7.6",
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "mime"
version = "0.3.16"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2a60c7ce501c71e03a9c9c0d35b861413ae925bd979cc7a4e30d060069aaac8d"
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-10-10 06:26:07 +03:00
[[package]]
name = "miniz_oxide"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b275950c28b37e794e8c55d88aeb5e139d0ce23fdbbeda68f8d7174abdf9e8fa"
dependencies = [
"adler",
]
Add support for heap profiling using dhat refs: https://github.com/wez/wezterm/issues/2626
2022-11-14 23:26:02 +03:00
[[package]]
name = "mintex"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fd7c5ba1c3b5a23418d7bbf98c71c3d4946a0125002129231da8d6b723d559cb"
dependencies = [
"once_cell",
"sys-info",
]
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +03:00
[[package]]
name = "mio"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.8.6"
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
2023-02-17 21:30:15 +03:00
checksum = "5b9d9a46eff5b4ff64b45a9e316a6d1e0bc719ef429cbec4dc630684212bfdf9"
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
2023-02-17 21:30:15 +03:00
"windows-sys 0.45.0",
deps: upgrade to mio 0.8
2022-05-05 05:19:14 +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"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.8.8"
cargo update
2022-08-21 18:51:16 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "ea8ce6788556a67d90567809c7de94dfef2ff1f47ff897aeee935bcfbcdf5735"
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",
update base64, work around another batch of breaking API changes closes: https://github.com/wez/wezterm/pull/2931
2023-01-09 04:49:45 +03:00
"base64 0.21.0",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"bintree",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
"finl_unicode",
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",
cargo update
2022-12-05 05:40:53 +03:00
"nix 0.25.1",
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",
mux: Pane is now required to be Send+Sync. Use Arc<dyn Pane>
2022-11-23 19:05:30 +03:00
"parking_lot 0.12.1",
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.16 closes: https://github.com/wez/wezterm/pull/2664
2022-10-24 06:50:47 +03:00
"textwrap 0.16.0",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"thiserror",
"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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
move mux to its own crate
2020-10-03 03:42:49 +03:00
]
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
[[package]]
name = "mux-lua"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
lua: add tostring impls for window, tab and pane objects
2022-07-16 18:22:10 +03:00
"libc",
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
"log",
"luahelper",
"mux",
mux: switch RefCell to RwLock internally This is a step towards making it Send+Sync. I'm a little cagey about this in the long term, as there are some mux operations that may technically require multiple fields to be locked for their duration: allowing free-threaded access may introduce some subtle (or not so subtle!) interleaving conditions where the overall mux state is not yet consistent. I'm thinking of prune_dead_windows kicking in while the mux is in the middle of being manipulated. I did try an initial pass of just moving everything under one lock, but there is already quite a lot of mixed read/write access to different aspects of the mux. We'll see what bubbles up later!
2022-11-24 19:19:32 +03:00
"parking_lot 0.12.1",
lua mux: add a couple of window methods
2022-06-17 19:27:28 +03:00
"portable-pty",
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
"smol",
Add ResetTerminal and pane:inject_output method refs: https://github.com/wez/wezterm/discussions/2606
2022-10-08 20:21:43 +03:00
"termwiz",
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
"wezterm-dynamic",
lua mux: add a couple of window methods
2022-06-17 19:27:28 +03:00
"wezterm-term",
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "naga"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
version = "0.11.0"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
checksum = "5eafe22a23b797c9bc227c6c896419b26b5bb88fa903417a3adaed08778850d5"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"bit-set",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"codespan-reporting",
"hexf-parse",
"indexmap",
"log",
"num-traits",
"rustc-hash",
"spirv",
"termcolor",
"thiserror",
"unicode-xid",
]
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
2023-01-16 07:48:20 +03:00
"rand",
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
2023-01-16 07:48:20 +03:00
"getrandom",
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"
deps: cargo update for openssl
2022-11-02 04:09:23 +03:00
version = "0.2.11"
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 for openssl
2022-11-02 04:09:23 +03:00
checksum = "07226173c32f2926027b63cce4bcd8076c3552846cbe7925f3aaffeac0a3b92e"
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",
]
cargo update
2021-03-01 20:02:05 +03:00
[[package]]
name = "nix"
cargo update
2022-12-05 05:40:53 +03:00
version = "0.23.2"
cargo update
2021-03-01 20:02:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-05 05:40:53 +03:00
checksum = "8f3790c00a0150112de0f4cd161e3d7fc4b2d8a5542ffc35f099a2562aecb35c"
cargo update
2021-03-01 20:02:05 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
cargo update
2021-03-01 20:02:05 +03:00
"cc",
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
cargo update
2021-03-01 20:02:05 +03:00
"libc",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"memoffset 0.6.5",
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"
cargo update
2022-12-05 05:40:53 +03:00
version = "0.24.3"
deps: nix -> 0.24
2022-05-05 04:55:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-05 05:40:53 +03:00
checksum = "fa52e972a9a719cecb6864fb88568781eb706bac2cd1d4f04a648542dbf78069"
deps: nix -> 0.24
2022-05-05 04:55:56 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: nix -> 0.24
2022-05-05 04:55:56 +03:00
"libc",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"memoffset 0.6.5",
deps: nix -> 0.24
2022-05-05 04:55:56 +03:00
]
change text cursor to fa_lock when entering passwords There are caveats to determining this, but when we think password entry is enabled, switch the cursor to the font-awesome lock glyph instead of the normal cursor sprite. fa_lock is used because it is monochrome and can thus be tinted to the configured cursor color, and it respects blinking/easing. refs: https://github.com/wez/wezterm/issues/2460
2022-09-02 19:00:28 +03:00
[[package]]
name = "nix"
cargo update
2022-12-05 05:40:53 +03:00
version = "0.25.1"
change text cursor to fa_lock when entering passwords There are caveats to determining this, but when we think password entry is enabled, switch the cursor to the font-awesome lock glyph instead of the normal cursor sprite. fa_lock is used because it is monochrome and can thus be tinted to the configured cursor color, and it respects blinking/easing. refs: https://github.com/wez/wezterm/issues/2460
2022-09-02 19:00:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-05 05:40:53 +03:00
checksum = "f346ff70e7dbfd675fe90590b92d59ef2de15a8779ae305ebcbfd3f0caf59be4"
change text cursor to fa_lock when entering passwords There are caveats to determining this, but when we think password entry is enabled, switch the cursor to the font-awesome lock glyph instead of the normal cursor sprite. fa_lock is used because it is monochrome and can thus be tinted to the configured cursor color, and it respects blinking/easing. refs: https://github.com/wez/wezterm/issues/2460
2022-09-02 19:00:28 +03:00
dependencies = [
"autocfg",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
change text cursor to fa_lock when entering passwords There are caveats to determining this, but when we think password entry is enabled, switch the cursor to the font-awesome lock glyph instead of the normal cursor sprite. fa_lock is used because it is monochrome and can thus be tinted to the configured cursor color, and it respects blinking/easing. refs: https://github.com/wez/wezterm/issues/2460
2022-09-02 19:00:28 +03:00
"libc",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"memoffset 0.6.5",
change text cursor to fa_lock when entering passwords There are caveats to determining this, but when we think password entry is enabled, switch the cursor to the font-awesome lock glyph instead of the normal cursor sprite. fa_lock is used because it is monochrome and can thus be tinted to the configured cursor color, and it respects blinking/easing. refs: https://github.com/wez/wezterm/issues/2460
2022-09-02 19:00:28 +03:00
"pin-utils",
]
cargo update
2023-03-13 06:22:05 +03:00
[[package]]
name = "nix"
version = "0.26.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bfdda3d196821d6af13126e40375cdf7da646a96114af134d5f417a9a1dc8e1a"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
cargo update
2023-03-13 06:22:05 +03:00
"cfg-if",
"libc",
"memoffset 0.7.1",
"pin-utils",
"static_assertions",
]
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
[[package]]
name = "no-std-compat"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b93853da6d84c2e3c7d730d6473e8817692dd89be387eb01b94d7f108ecb5b8c"
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"
cargo update
2023-01-16 07:48:20 +03:00
version = "7.1.3"
cargo update
2021-08-23 17:33:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-16 07:48:20 +03:00
checksum = "d273983c5a657a70a3e8f2a01329822f3b8c8172b73826411a55751e404a0a4a"
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"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +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
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
checksum = "38bf9645c8b145698bb0b18a4637dcacbc421ea49bef2317e4fd8065a387cf21"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "5.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: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "58ea850aa68a06e48fdb069c0ec44d0d64c8dbffa49bf3b6f7f0a901fdea1ba9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +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
"filetime",
"fsevent-sys",
"inotify",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"kqueue",
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: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"mio",
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
"walkdir",
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.42.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
]
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"
deps: update ntapi to 0.4 Avoids: ``` warning: the following packages contain code that will be rejected by a future version of Rust: ntapi v0.3.7 note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 36` ```
2022-12-20 01:23:11 +03:00
version = "0.4.0"
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"
deps: update ntapi to 0.4 Avoids: ``` warning: the following packages contain code that will be rejected by a future version of Rust: ntapi v0.3.7 note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 36` ```
2022-12-20 01:23:11 +03:00
checksum = "bc51db7b362b205941f71232e56c625156eb9a929f8cf74a428fd5bc094a4afc"
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 = [
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2022-06-27 06:40:48 +03:00
version = "0.4.1"
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-06-27 06:40:48 +03:00
checksum = "0638a1c9d0a3c0914158145bc76cff373a75a627e6ecbfb71cbe6f453a5a19b0"
deps: image -> 0.24
2022-02-07 04:51:32 +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-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"
cargo update
2022-12-26 09:30:13 +03:00
version = "1.15.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-12-26 09:30:13 +03:00
checksum = "0fac9e2da13b5eb447a6ce3d392f23a29d8694bff781bf03a16cd9ac8697593b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-12-26 09:30:13 +03:00
"hermit-abi 0.2.6",
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 = "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",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"objc_exception",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "objc_exception"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ad970fb455818ad6cba4c122ad012fae53ae8b4795f86378bce65e4f6bab2ca4"
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]]
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"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "0.30.3"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "ea86265d3d3dcb6a27fc51bd29a4bf387fae9d2986b823079d4986af253eb439"
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
2023-02-17 21:30:15 +03:00
version = "1.17.1"
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
2023-02-17 21:30:15 +03:00
checksum = "b7e5500299e16ebb147ae15a00a942af264cf3688f47923b8fc2cd5858f23ad3"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "oorandom"
version = "11.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0ab1bc2a289d34bd04a330323ac98a1b4bc82c9d9fcb1e66b63caa84da26b575"
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 = "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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
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
2023-02-09 07:25:41 +03:00
version = "300.0.12+3.0.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-09 07:25:41 +03:00
checksum = "4d974055736373bab35bdb25e578fd477e1e195611744c42373294ac8897068d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2022-11-07 04:51:07 +03:00
version = "3.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
2022-11-07 04:51:07 +03:00
checksum = "d84eb1409416d254e4a9c8fa56cc24701755025b458f0fcd8e59e1f5f40c23bf"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.2.0"
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
2023-02-17 21:30:15 +03:00
checksum = "9aa2b01e1d916879f73a53d01d1d6cee68adbb31d6d9177a8cfce093cced1d50"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
dependencies = [
"futures-core",
"pin-project-lite",
]
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
[[package]]
name = "os_str_bytes"
cargo update
2023-03-20 06:20:34 +03:00
version = "6.5.0"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "ceedf44fb00f2d1984b0bc98102627ce622e083e49a5bacdb3e514fa4238e267"
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
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"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
version = "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
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
checksum = "7d17b78036a60663b797adeaee46f5c9dfebb86948d1255007a1d6be0271ff99"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"instant",
"lock_api",
cargo update
2022-12-19 21:13:02 +03:00
"parking_lot_core 0.8.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
]
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
[[package]]
name = "parking_lot"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
version = "0.12.1"
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"
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
checksum = "3742b2c103b9f06bc9fff0a37ff4912935851bee6d36f3c02bcc755bcfec228f"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
dependencies = [
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"lock_api",
cargo update
2023-02-06 07:53:11 +03:00
"parking_lot_core 0.9.7",
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"
cargo update
2022-12-19 21:13:02 +03:00
version = "0.8.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-12-19 21:13:02 +03:00
checksum = "60a2cfe6f0ad2bfc16aefa463b497d5c7a5ecd44a23efa72aa342d90177356dc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"instant",
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: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"redox_syscall",
"smallvec",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-06 07:53:11 +03:00
version = "0.9.7"
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
2023-02-06 07:53:11 +03:00
checksum = "9069cbb9f99e3a5083476ccb29ceb1de18b9118cafa53e90c9551235de2b9521"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
"libc",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"redox_syscall",
"smallvec",
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.45.0",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +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
2023-01-16 07:48:20 +03:00
version = "1.1.1"
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
2023-01-16 07:48:20 +03:00
checksum = "a8835c273a76a90455d7344889b0964598e3316e2a79ede8e36f16bdcf2228b8"
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: update base64 closes: https://github.com/wez/wezterm/pull/2855
2022-12-12 19:14:42 +03:00
"base64 0.13.1",
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"
cargo update
2022-09-12 16:26:10 +03:00
version = "2.2.0"
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-09-12 16:26:10 +03:00
checksum = "478c572c3d73181ff3c2539045f6eb99e5491218eae919370993b890cdbdd98e"
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"
cargo update
2023-03-06 08:18:33 +03:00
version = "2.5.6"
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
2023-03-06 08:18:33 +03:00
checksum = "8cbd939b234e95d72bc393d51788aec68aeeb5d51e748ca08ff3aad58cb722f7"
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 = [
cargo update
2022-08-01 06:14:19 +03:00
"thiserror",
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
"ucd-trie",
]
[[package]]
name = "pest_derive"
cargo update
2023-03-06 08:18:33 +03:00
version = "2.5.6"
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
2023-03-06 08:18:33 +03:00
checksum = "a81186863f3d0a27340815be8f2078dd8050b14cd71913db9fbda795e5f707d7"
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 = [
"pest",
"pest_generator",
]
[[package]]
name = "pest_generator"
cargo update
2023-03-06 08:18:33 +03:00
version = "2.5.6"
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
2023-03-06 08:18:33 +03:00
checksum = "75a1ef20bf3193c15ac345acb32e26b3dc3223aff4d77ae4fc5359567683796b"
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 = [
"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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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"
cargo update
2023-03-06 08:18:33 +03:00
version = "2.5.6"
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
2023-03-06 08:18:33 +03:00
checksum = "5e3b284b1f13a20dc5ebc90aff59a51b8d7137c221131b52a7260c08cbc1cc80"
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 = [
cargo update
2022-08-01 06:14:19 +03:00
"once_cell",
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
"pest",
cargo update
2023-01-16 07:48:20 +03:00
"sha2 0.10.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
]
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",
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
]
[[package]]
name = "phf"
cargo update
2022-08-15 08:27:23 +03:00
version = "0.11.1"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-08-15 08:27:23 +03:00
checksum = "928c6535de93548188ef63bb7c4036bd415cd8f36ad25af44b9789b2ee72a48c"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
dependencies = [
"phf_macros",
cargo update
2022-08-15 08:27:23 +03:00
"phf_shared 0.11.1",
termwiz: use perfect hashing for emoji variation sequences
2022-04-27 05:10: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 = "phf_codegen"
cargo update
2023-01-16 07:48:20 +03:00
version = "0.11.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
2023-01-16 07:48:20 +03:00
checksum = "a56ac890c5e3ca598bbdeaa99964edb5b0258a583a9eb6ef4e89fc85d9224770"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +03:00
"phf_generator",
"phf_shared 0.11.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
]
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
[[package]]
name = "phf_generator"
cargo update
2022-08-15 08:27:23 +03:00
version = "0.11.1"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-08-15 08:27:23 +03:00
checksum = "b1181c94580fa345f50f19d738aaa39c0ed30a600d95cb2d3e23f94266f14fbf"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
dependencies = [
cargo update
2022-08-15 08:27:23 +03:00
"phf_shared 0.11.1",
cargo update
2023-01-16 07:48:20 +03:00
"rand",
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
]
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
[[package]]
name = "phf_macros"
cargo update
2022-08-15 08:27:23 +03:00
version = "0.11.1"
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"
cargo update
2022-08-15 08:27:23 +03:00
checksum = "92aacdc5f16768709a569e913f7451034034178b05bdc8acda226659a3dccc66"
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"phf_generator",
cargo update
2022-08-15 08:27:23 +03:00
"phf_shared 0.11.1",
added new window_background_gradient config option
2021-08-13 09:08:38 +03:00
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
added new window_background_gradient config option
2021-08-13 09:08:38 +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",
]
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "phf_shared"
cargo update
2022-08-15 08:27:23 +03:00
version = "0.11.1"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-08-15 08:27:23 +03:00
checksum = "e1fb5f6f826b772a8d4c0394209441e7d37cbbb967ae9c7e0e8134365c9ee676"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
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-08-21 18:51:16 +03:00
version = "1.0.12"
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-08-21 18:51:16 +03:00
checksum = "ad29a609b6bcd67fee905812e544992d216af9d755757c05ed2d0e15a74c6ecc"
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-08-21 18:51:16 +03:00
version = "1.0.12"
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-08-21 18:51:16 +03:00
checksum = "069bdb1e05adc7a8990dce9cc75370895fbe4e3d58b9b73bf1aee56359344a55"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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"
deps: cargo update
2022-11-01 17:09:37 +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"
deps: cargo update
2022-11-01 17:09:37 +03:00
checksum = "6ac9a59f73473f1b8d852421e59e64809f025994837ef743615c6d0c5b305160"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
[[package]]
name = "plist"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.4.3"
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "9bd9647b268a3d3e14ff09c23201133a62589c658db02bb7388c7246aafe0590"
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
dependencies = [
cargo update
2023-02-27 08:32:52 +03:00
"base64 0.21.0",
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
"indexmap",
"line-wrap",
cargo update
2023-03-20 06:20:34 +03:00
"quick-xml 0.28.1",
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
"serde",
cargo update
2023-02-27 08:32:52 +03:00
"time 0.3.20",
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
]
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "plotters"
cargo update
2022-09-12 16:26:10 +03:00
version = "0.3.4"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-09-12 16:26:10 +03:00
checksum = "2538b639e642295546c50fcd545198c9d64ee2a38620a628724a3b266d5fbf97"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
dependencies = [
"num-traits",
"plotters-backend",
"plotters-svg",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "plotters-backend"
version = "0.3.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "193228616381fecdc1224c62e96946dfbc73ff4384fba576e052ff8c1bea8142"
[[package]]
name = "plotters-svg"
cargo update
2022-08-21 18:51:16 +03:00
version = "0.3.3"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-08-21 18:51:16 +03:00
checksum = "f9a81d2759aae1dae668f783c308bc5c8ebd191ff4184aaa1b37f65a6ae5a56f"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
dependencies = [
"plotters-backend",
]
Add wezterm.plugin module, allows loading modules from git Brief usage notes here: ```lua local wezterm = require 'wezterm' local a_plugin = wezterm.plugin.require "https://github.com/owner/repo" local config = wezterm.config_builder() a_plugin.apply_to_config(config) return config ``` The referenced repo is expected to have a `plugin/init.lua` file, and by convention, return a module that exports an `apply_to_config` function that accepts at least a config builder parameter, but may pass other parameters, or a lua table with a `config` field that maps to a config build parameter. `wezterm.plugin.require` will clone the repo if it doesn't already exist and store it in the runtime dir under `plugins/NAME` where `NAME` is derived from the repo URL. Once cloned, the repo is NOT automatically updated. Only HTTP (or local filesystem) repos are allowed for the git URL; we cannot currently use ssh for this due to conflicting version requirements that I'll take a look at later. `wezterm.plugin.require` will then perform `require "NAME"`, and since the default `package.path` now includes the appropriate location from the runtime dir, the module should load. Two other functions are available: `wezterm.plugin.list()` will list the plugin repos. `wezterm.plugin.update_all()` will attempt to fast-forward or `pull --rebase` each of the repos it finds. It doesn't currently do anything proactive to reload the configuration afterwards; the user will need to do that themselves.
2023-01-31 23:36:18 +03:00
[[package]]
name = "plugin"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"git2",
"log",
"luahelper",
"tempfile",
"wezterm-dynamic",
]
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
[[package]]
name = "png"
deps: cargo update
2022-11-01 17:09:37 +03:00
version = "0.17.7"
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-11-01 17:09:37 +03:00
checksum = "5d708eaf860a19b19ce538740d2b4bdeeb8337fa53f7738455e706623ad5c638"
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
deps: tiny-skia -> 0.6
2021-08-23 17:48:13 +03:00
"crc32fast",
cargo update
2022-09-12 16:26:10 +03:00
"flate2",
deps: cargo update
2022-11-01 17:09:37 +03:00
"miniz_oxide 0.6.2",
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
2023-03-13 06:22:05 +03:00
version = "2.6.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "7e1f879b2998099c2d69ab9605d145d5b661195627eccc680002c4918a7fb6fa"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
cargo update
2022-08-21 18:51:16 +03:00
"autocfg",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
cargo update
2023-03-13 06:22:05 +03:00
"concurrent-queue",
cargo update
2020-09-09 19:31:37 +03:00
"libc",
"log",
cargo update
2023-03-13 06:22:05 +03:00
"pin-project-lite",
"windows-sys 0.45.0",
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 = "portable-pty"
build(pty): don't use `std::os::fd::RawFd` symbol directly For whatever reason, `portable-pty` doesn't build until Rust v1.66 due to a failure to import `std::os::fd::RawFd`. According to `cargo-msrv`: ``` $ cargo msrv --linear Fetching index Determining the Minimum Supported Rust Version (MSRV) for toolchain aarch64-apple-darwin Using check command cargo check ⠲ Checking 1.68.0 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ⠴ Checking 1.68.0 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ Check for toolchain '1.68.0-aarch64-apple-darwin' succeeded Check for toolchain '1.67.1-aarch64-apple-darwin' succeeded Check for toolchain '1.66.1-aarch64-apple-darwin' succeeded Check for toolchain '1.65.0-aarch64-apple-darwin' failed with: ┌───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Compiling libc v0.2.139 │ │ Compiling autocfg v1.1.0 │ │ Checking cfg-if v1.0.0 │ │ Compiling proc-macro2 v1.0.51 │ │ Compiling quote v1.0.23 │ │ Compiling syn v1.0.109 │ │ Compiling unicode-ident v1.0.8 │ │ Compiling version_check v0.9.4 │ │ Compiling pkg-config v0.3.26 │ │ Compiling memchr v2.5.0 │ │ Checking bitflags v1.3.2 │ │ Checking once_cell v1.17.1 │ │ Compiling log v0.4.17 │ │ Compiling num-traits v0.2.15 │ │ Compiling futures-core v0.3.26 │ │ Compiling crossbeam-utils v0.8.15 │ │ Compiling serde_derive v1.0.152 │ │ Compiling thiserror v1.0.39 │ │ Compiling serde v1.0.152 │ │ Compiling jobserver v0.1.26 │ │ Checking pin-project-lite v0.2.9 │ │ Compiling cc v1.0.79 │ │ Checking getrandom v0.2.8 │ │ Checking scopeguard v1.1.0 │ │ Compiling ahash v0.7.6 │ │ Checking futures-sink v0.3.26 │ │ Checking futures-io v0.3.26 │ │ Compiling slab v0.4.8 │ │ Checking lazy_static v1.4.0 │ │ Compiling lock_api v0.4.9 │ │ Checking smallvec v1.10.0 │ │ Checking num_cpus v1.15.0 │ │ Compiling num-integer v0.1.45 │ │ Compiling siphasher v0.3.10 │ │ Compiling rand_core v0.6.4 │ │ Checking fastrand v1.9.0 │ │ Compiling rand v0.8.5 │ │ Compiling phf_shared v0.11.1 │ │ Compiling memoffset v0.8.0 │ │ Checking adler v1.0.2 │ │ Checking pin-utils v0.1.0 │ │ Compiling indexmap v1.9.2 │ │ Compiling futures-channel v0.3.26 │ │ Compiling libz-sys v1.1.8 │ │ Compiling anyhow v1.0.69 │ │ Checking hashbrown v0.12.3 │ │ Compiling phf_generator v0.11.1 │ │ Compiling futures-task v0.3.26 │ │ Checking miniz_oxide v0.6.2 │ │ Checking socket2 v0.4.9 │ │ Compiling crossbeam-epoch v0.9.14 │ │ Compiling futures-util v0.3.26 │ │ Compiling crc32fast v1.3.2 │ │ Checking strsim v0.10.0 │ │ Checking crossbeam-channel v0.5.7 │ │ Checking fnv v1.0.7 │ │ Compiling typenum v1.16.0 │ │ Compiling memoffset v0.6.5 │ │ Checking event-listener v2.5.3 │ │ Checking byteorder v1.4.3 │ │ Checking concurrent-queue v2.1.0 │ │ Checking parking v2.0.0 │ │ Compiling rayon-core v1.11.0 │ │ Checking waker-fn v1.1.0 │ │ Checking async-lock v2.7.0 │ │ Checking futures-lite v1.12.0 │ │ Checking signal-hook-registry v1.4.1 │ │ Checking crossbeam-deque v0.8.3 │ │ Compiling generic-array v0.14.6 │ │ Checking flate2 v1.0.25 │ │ Checking spin v0.9.5 │ │ Checking nanorand v0.7.0 │ │ Checking aho-corasick v0.7.20 │ │ Compiling polling v2.5.2 │ │ Checking regex-syntax v0.6.28 │ │ Compiling ucd-trie v0.1.5 │ │ Checking either v1.8.1 │ │ Compiling phf_codegen v0.11.1 │ │ Compiling lua-src v544.0.1 │ │ Compiling luajit-src v210.4.5+resty2cf5186 │ │ Compiling nom v5.1.2 │ │ Compiling num-rational v0.4.1 │ │ Checking rayon v1.7.0 │ │ Compiling async-io v1.12.0 │ │ Checking weezl v0.1.7 │ │ Checking regex-automata v0.1.10 │ │ Checking async-task v4.3.0 │ │ Checking simd-adler32 v0.3.4 │ │ Compiling core-foundation-sys v0.8.3 │ │ Checking base64 v0.21.0 │ │ Checking tinyvec_macros v0.1.1 │ │ Checking rustc-hash v1.1.0 │ │ Checking lab v0.11.0 │ │ Compiling tinyvec v1.6.0 │ │ Checking zune-inflate v0.2.50 │ │ Compiling mlua v0.8.8 │ │ Checking regex v1.7.1 │ │ Compiling terminfo v0.7.5 │ │ Checking png v0.17.7 │ │ Checking threadpool v1.8.1 │ │ Checking dirs-sys v0.3.7 │ │ Checking percent-encoding v2.2.0 │ │ Checking half v2.2.1 │ │ Checking lebe v0.5.2 │ │ Checking color_quant v1.1.0 │ │ Checking bit_field v0.10.2 │ │ Checking form_urlencoded v1.1.0 │ │ Checking gif v0.11.4 │ │ Checking unicode-normalization v0.1.22 │ │ Checking dirs v4.0.0 │ │ Checking jpeg-decoder v0.3.0 │ │ Checking block-buffer v0.9.0 │ │ Checking digest v0.9.0 │ │ Checking async-channel v1.8.0 │ │ Checking phf_shared v0.10.0 │ │ Compiling libgit2-sys v0.14.2+1.5.1 │ │ Checking cpufeatures v0.2.5 │ │ Checking unicode-bidi v0.3.10 │ │ Checking utf8parse v0.2.0 │ │ Checking opaque-debug v0.3.0 │ │ Compiling thiserror-impl v1.0.39 │ │ Compiling futures-macro v0.3.26 │ │ Compiling wezterm-dynamic-derive v0.1.0 (/Users/waleed/Workspace/wezterm/wezterm-dynamic/derive) │ │ Compiling bytemuck_derive v1.4.0 │ │ Compiling phf_macros v0.11.1 │ │ Compiling pin-project-internal v1.0.12 │ │ Checking tiff v0.8.1 │ │ Compiling signal-hook v0.3.15 │ │ Checking deltae v0.3.0 │ │ Checking scoped_threadpool v0.1.9 │ │ Checking atomic-waker v1.1.0 │ │ Checking blocking v1.3.0 │ │ Checking bytemuck v1.13.1 │ │ Checking phf v0.11.1 │ │ Compiling idna v0.3.0 │ │ Checking csscolorparser v0.6.2 │ │ Checking pin-project v1.0.12 │ │ Checking filedescriptor v0.8.2 (/Users/waleed/Workspace/wezterm/filedescriptor) │ │ Compiling pest v2.5.6 │ │ Checking flume v0.10.14 │ │ Checking sha2 v0.9.9 │ │ Checking exr v1.5.3 │ │ Checking vtparse v0.6.2 (/Users/waleed/Workspace/wezterm/vtparse) │ │ Compiling num-derive v0.3.3 │ │ Checking phf v0.10.1 │ │ Checking nix v0.24.3 │ │ Checking signal-hook v0.1.17 │ │ Checking termios v0.3.3 │ │ Checking serial-core v0.4.0 │ │ Checking ioctl-rs v0.1.6 │ │ Checking termios v0.2.2 │ │ Compiling async-net v1.7.0 │ │ Checking semver-parser v0.10.2 │ │ Compiling async-process v1.6.0 │ │ Compiling pest_meta v2.5.6 │ │ Compiling async-fs v1.6.0 │ │ Checking semver v0.11.0 │ │ Checking memmem v0.1.1 │ │ Checking unicode-segmentation v1.10.1 │ │ Checking finl_unicode v1.2.0 │ │ Checking fixedbitset v0.4.2 │ │ Checking hex v0.4.3 │ │ Checking same-file v1.0.6 │ │ Checking walkdir v2.3.2 │ │ Checking serial-unix v0.4.0 │ │ Compiling pest_generator v2.5.6 │ │ Checking url v2.3.1 │ │ Checking image v0.24.5 │ │ Checking async-executor v1.5.0 │ │ Checking bstr v0.2.17 │ │ Compiling miniz_oxide v0.4.4 │ │ Checking serial v0.4.0 │ │ Checking nix v0.25.1 │ │ Checking euclid v0.22.7 │ │ Checking dirs-sys-next v0.1.2 │ │ Checking filetime v0.2.20 │ │ Checking winnow v0.3.4 │ │ Checking downcast-rs v1.2.0 │ │ Checking shell-words v1.1.0 │ │ Checking dirs-next v2.0.0 │ │ Checking smol v1.3.0 │ │ Checking lru v0.7.8 │ │ Checking fsevent-sys v4.1.0 │ │ Checking match_cfg v0.1.0 │ │ Compiling pest_derive v2.5.6 │ │ Checking promise v0.2.0 (/Users/waleed/Workspace/wezterm/promise) │ │ Checking hostname v0.3.1 │ │ Checking notify v5.1.0 │ │ Checking colorgrad v0.6.2 │ │ Compiling enum-display-derive v0.1.1 │ │ Compiling wezterm-config-derive v0.1.0 (/Users/waleed/Workspace/wezterm/config/derive) │ │ Checking umask v0.1.0 (/Users/waleed/Workspace/wezterm/umask) │ │ Checking shlex v1.1.0 │ │ Compiling openssl-src v300.0.12+3.0.8 │ │ Checking foreign-types-shared v0.1.1 │ │ Checking itoa v1.0.6 │ │ Checking foreign-types v0.3.2 │ │ Compiling io-lifetimes v1.0.5 │ │ Compiling rustix v0.36.9 │ │ Checking errno v0.2.8 │ │ Compiling openssl-sys v0.9.71 │ │ Checking ordered-float v3.4.0 │ │ Checking toml_datetime v0.6.1 │ │ Checking serde_spanned v0.6.1 │ │ Compiling objc_exception v0.1.2 │ │ Checking wezterm-dynamic v0.1.0 (/Users/waleed/Workspace/wezterm/wezterm-dynamic) │ │ Checking toml_edit v0.19.4 │ │ Checking portable-pty v0.8.0 (/Users/waleed/Workspace/wezterm/pty) │ │ error[E0412]: cannot find type `RawFd` in `std::os::fd` │ │ --> pty/src/unix.rs:326:48 │ │ | │ │ 326 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { │ │ | ^^^^^ not found in `std::os::fd` │ │ | │ │ help: consider importing this type alias │ │ | │ │ 3 | use std::os::unix::prelude::RawFd; │ │ | │ │ help: if you import `RawFd`, refer to it directly │ │ | │ │ 326 - fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { │ │ 326 + fn as_raw_fd(&self) -> Option<RawFd> { │ │ | │ │ │ │ error[E0412]: cannot find type `RawFd` in `std::os::fd` │ │ --> pty/src/serial.rs:245:48 │ │ | │ │ 245 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { │ │ | ^^^^^ not found in `std::os::fd` │ │ | │ │ help: consider importing this type alias │ │ | │ │ 8 | use std::os::unix::prelude::RawFd; │ │ | │ │ help: if you import `RawFd`, refer to it directly │ │ | │ │ 245 - fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { │ │ 245 + fn as_raw_fd(&self) -> Option<RawFd> { │ │ | │ │ │ │ error[E0412]: cannot find type `RawFd` in `std::os::fd` │ │ --> pty/src/lib.rs:114:48 │ │ | │ │ 114 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd>; │ │ | ^^^^^ not found in `std::os::fd` │ │ | │ │ help: consider importing this type alias │ │ | │ │ 40 | use std::os::unix::prelude::RawFd; │ │ | │ │ help: if you import `RawFd`, refer to it directly │ │ | │ │ 114 - fn as_raw_fd(&self) -> Option<std::os::fd::RawFd>; │ │ 114 + fn as_raw_fd(&self) -> Option<RawFd>; │ │ | │ │ │ │ error[E0603]: module `fd` is private │ │ --> pty/src/unix.rs:326:44 │ │ | │ │ 326 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { │ │ | ^^ private module │ │ | │ │ note: the module `fd` is defined here │ │ │ │ error[E0603]: module `fd` is private │ │ --> pty/src/serial.rs:245:44 │ │ | │ │ 245 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { │ │ | ^^ private module │ │ | │ │ note: the module `fd` is defined here │ │ │ │ error[E0603]: module `fd` is private │ │ --> pty/src/lib.rs:114:44 │ │ | │ │ 114 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd>; │ │ | ^^ private module │ │ | │ │ note: the module `fd` is defined here │ │ │ │ Checking wezterm-color-types v0.2.0 (/Users/waleed/Workspace/wezterm/color-types) │ │ Checking wezterm-bidi v0.2.2 (/Users/waleed/Workspace/wezterm/bidi) │ │ Some errors have detailed explanations: E0412, E0603. │ │ For more information about an error, try `rustc --explain E0412`. │ │ error: could not compile `portable-pty` due to 6 previous errors │ │ warning: build failed, waiting for other jobs to finish... │ └───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘ Finished The MSRV is: 1.66.1 ██████████████████████████████████████████████████████████████████████████████████████████████ 00:05:30 ``` However, the issue is simple to work around: just don't use the symbol `std::os::fd::RawFd` directly. This commit: 1) changes the interface to use a new exported symbol `RawFd` from the `crate::unix` module; 2) imports `std::os::unix::io::RawFd` instead of `std::os::fd::RawFd` as the symbol exported from `crate::unix`. Doing so fixes the build in earlier versions of Rust: ``` $ cargo +1.63.0 check -p portable-pty --all-targets Checking portable-pty v0.8.0 (/Users/waleed/Workspace/wezterm/pty) error[E0412]: cannot find type `RawFd` in `std::os::fd` --> pty/src/unix.rs:326:48 | 326 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { | ^^^^^ not found in `std::os::fd` | help: consider importing this type alias | 3 | use std::os::unix::prelude::RawFd; | help: if you import `RawFd`, refer to it directly | 326 - fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { 326 + fn as_raw_fd(&self) -> Option<RawFd> { | error[E0412]: cannot find type `RawFd` in `std::os::fd` --> pty/src/serial.rs:245:48 | 245 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { | ^^^^^ not found in `std::os::fd` | help: consider importing this type alias | 8 | use std::os::unix::prelude::RawFd; | help: if you import `RawFd`, refer to it directly | 245 - fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { 245 + fn as_raw_fd(&self) -> Option<RawFd> { | error[E0412]: cannot find type `RawFd` in `std::os::fd` --> pty/src/lib.rs:114:48 | 114 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd>; | ^^^^^ not found in `std::os::fd` | help: consider importing this type alias | 40 | use std::os::unix::prelude::RawFd; | help: if you import `RawFd`, refer to it directly | 114 - fn as_raw_fd(&self) -> Option<std::os::fd::RawFd>; 114 + fn as_raw_fd(&self) -> Option<RawFd>; | error[E0603]: module `fd` is private --> pty/src/unix.rs:326:44 | 326 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { | ^^ private module | note: the module `fd` is defined here error[E0603]: module `fd` is private --> pty/src/serial.rs:245:44 | 245 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd> { | ^^ private module | note: the module `fd` is defined here error[E0603]: module `fd` is private --> pty/src/lib.rs:114:44 | 114 | fn as_raw_fd(&self) -> Option<std::os::fd::RawFd>; | ^^ private module | note: the module `fd` is defined here Some errors have detailed explanations: E0412, E0603. For more information about an error, try `rustc --explain E0412`. error: could not compile `portable-pty` due to 6 previous errors warning: build failed, waiting for other jobs to finish... error: could not compile `portable-pty` due to 6 previous errors $ cargo +1.63.0 check -p portable-pty --all-targets Finished dev [unoptimized + debuginfo] target(s) in 0.17s ```
2023-03-13 00:19:58 +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
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",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
cargo update
2022-12-05 05:40:53 +03:00
"nix 0.25.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
"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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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-11-07 04:51:07 +03:00
version = "0.2.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
2022-11-07 04:51:07 +03:00
checksum = "5b40af805b3121feab8a3c29f04d8ad262fa8e0561883e7653e024ae4479e6de"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-12-30 18:50:10 +03:00
version = "2.1.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-12-30 18:50:10 +03:00
checksum = "59230a63c37f3e18569bdb90e4a89cbf5bf8b06fea0b84e65ea10cc4df47addd"
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",
]
cargo update
2023-03-17 22:02:21 +03:00
[[package]]
name = "predicates"
version = "3.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1ba7d6ead3e3966038f68caa9fc1f860185d95a793180bbcfe0d0da47b3961ed"
dependencies = [
"anstyle",
"difflib",
"itertools",
"predicates-core",
]
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-core"
cargo update
2023-03-17 22:02:21 +03:00
version = "1.0.6"
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
2023-03-17 22:02:21 +03:00
checksum = "b794032607612e7abeb4db69adb4e33590fa6cf1149e95fd7cb00e634b92f174"
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
2023-03-17 22:02:21 +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
2023-03-17 22:02:21 +03:00
checksum = "368ba315fb8c5052ab692e68a0eefec6ec57b23a36959c14496f0b0df2c0cecf"
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"
cargo update
2023-03-06 08:18:33 +03:00
version = "1.3.1"
cargo update
2021-06-14 09:36:22 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "7f4c021e1093a56626774e81216a4ce732a735e5bad4868a03f3ed65ca0c3919"
cargo update
2021-06-14 09:36:22 +03:00
dependencies = [
cargo update
2022-08-08 05:31:29 +03:00
"once_cell",
cargo update
2023-03-06 08:18:33 +03:00
"toml_edit",
cargo update
2021-06-14 09:36:22 +03:00
]
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-13 06:22:05 +03:00
version = "1.0.52"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-13 06:22:05 +03:00
checksum = "1d0e1ae9e836cc3beddd63db0df682593d7e2d3d891ae8c9083d2113e1744224"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-05-23 18:18:06 +03:00
"unicode-ident",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
move procinfo bits into own crate
2022-01-01 05:30:52 +03:00
]
lua: add wezterm.procinfo module
2022-07-16 18:49:58 +03:00
[[package]]
name = "procinfo-funcs"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"libc",
"luahelper",
"procinfo",
"wezterm-dynamic",
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "profiling"
version = "1.0.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "74605f360ce573babfe43964cbe520294dcb081afbf8c108fc6e23036b4da2df"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
deps: remove async-std dep We were only using block_on from it, which we can call from the underlying async_io crate. Notably, removing async_std from the deps avoids async-global-executor being pulled in and spawning nproc threads that are never used by wezterm.
2022-11-01 17:05:33 +03:00
"async-io",
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-08-01 06:14:19 +03:00
version = "0.9.2"
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-08-01 06:14:19 +03:00
checksum = "2d9cc634bc78768157b5cbfe988ffcd1dcba95cd2b2f03a88316c08c6d00ed63"
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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
improve handling of animated webp images Use mainline image crate to avoid an otherwise unavoidable panic in the upstream: https://github.com/image-rs/image/issues/1775 Explicitly operate on the frames from the animation. refs: https://github.com/wez/wezterm/issues/3250
2023-03-15 21:34:47 +03:00
[[package]]
name = "qoi"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7f6d64c71eb498fe9eae14ce4ec935c555749aef511cca85b5568910d6e48001"
dependencies = [
"bytemuck",
]
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
[[package]]
name = "quanta"
version = "0.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "20afe714292d5e879d8b12740aa223c6a88f118af41870e8b6196e39a02238a8"
dependencies = [
"crossbeam-utils",
"libc",
"mach",
"once_cell",
"raw-cpuid",
"wasi 0.10.2+wasi-snapshot-preview1",
"web-sys",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +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",
]
cargo update
2023-01-21 06:04:49 +03:00
[[package]]
name = "quick-xml"
cargo update
2023-03-20 06:20:34 +03:00
version = "0.28.1"
cargo update
2023-01-21 06:04:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "e5c1a97b1bc42b1d550bfb48d4262153fe400a12bab1511821736f7eac76d7e2"
cargo update
2023-01-21 06:04:49 +03:00
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"
cargo update
2023-03-17 22:02:21 +03:00
version = "1.0.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
2023-03-17 22:02:21 +03:00
checksum = "4424af4bf778aae2051a77b60283332f386554255d722233d09fbfc7e30da2fc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
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",
cargo update
2023-01-16 07:48:20 +03:00
"rand_chacha",
"rand_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
]
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",
cargo update
2023-01-16 07:48:20 +03:00
"rand_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
]
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"
deps: cargo update
2022-09-16 17:48:12 +03:00
version = "0.6.4"
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-09-16 17:48:12 +03:00
checksum = "ec0be4795e2f6a28069bec0b5ff3e2ac9bafc99e6a9a7dc3547996c5c816922c"
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 = [
cargo update
2023-01-16 07:48:20 +03:00
"getrandom",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "range-alloc"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.1.3"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "9c8a99fddc9f0ba0a85884b8d14e3592853e787d581ca1816c91349b10e4eeab"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +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 = [
rangeset: fix accidentally quadratic complexity When adding sparse ranges the cartesian product of range combinations was explored to find intersections, which is pretty awful if there are 1 million entries to be inserted. This commit employs binary search to reduce the complexity, at the expense of requiring that the internal range array is sorted.
2022-07-24 22:48:02 +03:00
"criterion",
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",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"governor",
move ratelim to its own crate
2020-10-03 03:31: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]]
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
name = "raw-cpuid"
cargo update
2023-03-06 08:18:33 +03:00
version = "10.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"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "6c297679cb867470fa8c9f67dbba74a78d78e3e98d7cf2b08d6d71540f797332"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 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
]
add raw-window-handle impls
2021-05-06 08:59:52 +03:00
[[package]]
name = "raw-window-handle"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.5.1"
cargo update
2021-11-29 05:09:45 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "4f851a03551ceefd30132e447f07f96cb7011d6b658374f3aed847333adb5559"
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
2023-03-06 08:18:33 +03:00
version = "1.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"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "1d2df5196e37bcc87abebc0053e20787d73847bb33134a69841207dd0a47f03b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"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
2023-03-06 08:18:33 +03:00
version = "1.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"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "4b8f95bd6966f5c87776639160a66bd8ab9895d9d4ab01ddba9fc60661aebe8d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
version = "0.9.3"
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 and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
checksum = "6413f3de1edee53342e6138e75b56d32e7bc6e332b3bd62d497b1929d4cfbcdd"
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",
cargo update
2023-02-27 08:32:52 +03:00
"time 0.3.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
"yasna",
]
cargo update
2021-01-11 19:43:32 +03:00
[[package]]
name = "redox_syscall"
cargo update
2022-08-01 06:14:19 +03:00
version = "0.2.16"
cargo update
2021-01-11 19:43:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-08-01 06:14:19 +03:00
checksum = "fb5a58c1855b4b6819d59012155603f0b22ad30cad752600aadfcb695265519a"
cargo update
2021-01-11 19:43:32 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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
2023-01-16 07:48:20 +03:00
"getrandom",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"redox_syscall",
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
2023-01-16 07:48:20 +03:00
version = "1.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
2023-01-16 07:48:20 +03:00
checksum = "48aaa5748ba571fb95cd2c85c09f629215d3a6ece942baa100950af03a34f733"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2022-11-07 04:51:07 +03:00
version = "0.6.28"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-11-07 04:51:07 +03:00
checksum = "456c603be3e8d448b072f410900c09faf164fbce2d480456f50eea6e25f9c848"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "renderdoc-sys"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f1382d1f0a252c4bf97dc20d979a2fdd05b024acd7c2ed0f7595d7817666a157"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "reqwest"
cargo update
2023-01-21 06:04:49 +03:00
version = "0.11.14"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-21 06:04:49 +03:00
checksum = "21eed90ec8570952d53b772ecf8f206aa1ec9a3d76b2521c56c42973f2d91ee9"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
cargo update
2023-01-21 06:04:49 +03:00
"base64 0.21.0",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"bytes",
"encoding_rs",
"futures-core",
"futures-util",
"h2",
"http",
"http-body",
"hyper",
"hyper-tls",
"ipnet",
"js-sys",
"log",
"mime",
"native-tls",
cargo update
2022-09-27 17:11:12 +03:00
"once_cell",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"percent-encoding",
"pin-project-lite",
"serde",
"serde_json",
"serde_urlencoded",
"tokio",
"tokio-native-tls",
"tower-service",
"url",
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
"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 = "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"
cargo update
2023-02-27 08:32:52 +03:00
version = "0.8.36"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-27 08:32:52 +03:00
checksum = "20ec2d3e3fc7a92ced357df9cebd5a10b6fb2aa1ee797bf7e9ce2f17dffc8f59"
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
[[package]]
name = "rle-decode-fast"
version = "1.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3582f63211428f83597b51b2ddb88e2a91a9d52d12831f9d08f5e624e8977422"
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"
build(deps): bump rstest from 0.15.0 to 0.16.0 Bumps [rstest](https://github.com/la10736/rstest) from 0.15.0 to 0.16.0. - [Release notes](https://github.com/la10736/rstest/releases) - [Changelog](https://github.com/la10736/rstest/blob/master/CHANGELOG.md) - [Commits](https://github.com/la10736/rstest/compare/0.15.0...0.16.0) --- updated-dependencies: - dependency-name: rstest dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-28 07:40:05 +03:00
version = "0.16.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"
build(deps): bump rstest from 0.15.0 to 0.16.0 Bumps [rstest](https://github.com/la10736/rstest) from 0.15.0 to 0.16.0. - [Release notes](https://github.com/la10736/rstest/releases) - [Changelog](https://github.com/la10736/rstest/blob/master/CHANGELOG.md) - [Commits](https://github.com/la10736/rstest/compare/0.15.0...0.16.0) --- updated-dependencies: - dependency-name: rstest dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-28 07:40:05 +03:00
checksum = "b07f2d176c472198ec1e6551dc7da28f1c089652f66a7b722676c2238ebc0edf"
cargo update
2022-05-16 05:44:27 +03:00
dependencies = [
"futures",
"futures-timer",
"rstest_macros",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"rustc_version",
cargo update
2022-05-16 05:44:27 +03:00
]
[[package]]
name = "rstest_macros"
build(deps): bump rstest from 0.15.0 to 0.16.0 Bumps [rstest](https://github.com/la10736/rstest) from 0.15.0 to 0.16.0. - [Release notes](https://github.com/la10736/rstest/releases) - [Changelog](https://github.com/la10736/rstest/blob/master/CHANGELOG.md) - [Commits](https://github.com/la10736/rstest/compare/0.15.0...0.16.0) --- updated-dependencies: - dependency-name: rstest dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-28 07:40:05 +03:00
version = "0.16.0"
cargo update
2022-05-16 05:44:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
build(deps): bump rstest from 0.15.0 to 0.16.0 Bumps [rstest](https://github.com/la10736/rstest) from 0.15.0 to 0.16.0. - [Release notes](https://github.com/la10736/rstest/releases) - [Changelog](https://github.com/la10736/rstest/blob/master/CHANGELOG.md) - [Commits](https://github.com/la10736/rstest/compare/0.15.0...0.16.0) --- updated-dependencies: - dependency-name: rstest dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-28 07:40:05 +03:00
checksum = "7229b505ae0706e64f37ffc54a9c163e11022a6636d58fe1f3f52018257ff9f7"
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 = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
"proc-macro2",
"quote",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"rustc_version",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
build(deps): bump rstest from 0.15.0 to 0.16.0 Bumps [rstest](https://github.com/la10736/rstest) from 0.15.0 to 0.16.0. - [Release notes](https://github.com/la10736/rstest/releases) - [Changelog](https://github.com/la10736/rstest/blob/master/CHANGELOG.md) - [Commits](https://github.com/la10736/rstest/compare/0.15.0...0.16.0) --- updated-dependencies: - dependency-name: rstest dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
2022-11-28 07:40:05 +03:00
"unicode-ident",
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +03:00
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "rusqlite"
version = "0.27.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85127183a999f7db96d1a976a309eebbfb6ea3b0b400ddd8340190129de6eb7a"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"fallible-iterator",
"fallible-streaming-iterator",
"hashlink",
"libsqlite3-sys",
"memchr",
"smallvec",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
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
2023-03-13 06:22:05 +03:00
"semver 1.0.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
]
cargo update
2022-11-28 07:32:51 +03:00
[[package]]
name = "rustix"
cargo update
2023-03-20 06:20:34 +03:00
version = "0.36.10"
cargo update
2022-11-28 07:32:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "2fe885c3a125aa45213b68cc1472a49880cb5923dc23f522ad2791b882228778"
cargo update
2022-11-28 07:32:51 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
cargo update
2022-11-28 07:32:51 +03:00
"errno",
"io-lifetimes",
"libc",
"linux-raw-sys",
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.45.0",
cargo update
2022-11-28 07:32:51 +03:00
]
bump some versions
2020-01-10 09:39:34 +03:00
[[package]]
name = "ryu"
cargo update
2023-03-06 08:18:33 +03:00
version = "1.0.13"
bump some versions
2020-01-10 09:39:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "f91339c0467de62360649f8d3e185ca8de4224ff281f66000de5eb2a77a79041"
bump some versions
2020-01-10 09:39:34 +03:00
colors: refine importer Adjust importer to read directly from the source .itermcolors files in the upstream repo. Extract some author information from the comments in those files. All data is now fetched (and cached!) via relatively minimal http requests rather than requiring a git repo locally. Also search for .yml files in base16 repos; found another couple of schemes this way. The toml files under assets/colors are no longer read by anything in the repo. I plan to remove them, but since the docs reference them as examples, I will first ensure that there are docs and tooling that explains how to write and share your own scheme files.
2022-07-14 09:56:45 +03:00
[[package]]
name = "safemem"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ef703b7cb59335eae2eb93ceb664c0eb7ea6bf567079d843e09420219668e072"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2023-01-16 07:48:20 +03:00
version = "0.1.21"
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
2023-01-16 07:48:20 +03:00
checksum = "713cfb06c7059f3588fb8044c0fad1d09e3c01d225e25b9220dbfdcf16dbb1b3"
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 = [
cargo update
2023-02-06 07:53:11 +03:00
"windows-sys 0.42.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
]
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"
deps: cargo update
2022-11-01 17:09:37 +03:00
version = "1.0.1"
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-11-01 17:09:37 +03:00
checksum = "e1cf6437eb19a8f4a6cc0f7dca544973b0b78843adbfeb3683d1a94a0024a294"
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 = "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
cargo update
2022-10-10 06:26:07 +03:00
[[package]]
name = "scratch"
cargo update
2023-03-06 08:18:33 +03:00
version = "1.0.5"
cargo update
2022-10-10 06:26:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "1792db035ce95be60c3f8853017b3999209281c24e2ba5bc8e59bf97a0c590c1"
cargo update
2022-10-10 06:26:07 +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: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
version = "2.8.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"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
checksum = "a332be01508d814fed64bf28f798a146d73792121129962fdf335bb3c49a4254"
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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"
cargo update
2023-01-21 06:04:49 +03:00
version = "2.8.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
2023-01-21 06:04:49 +03:00
checksum = "31c9bb296072e961fcbd8853511dd39c2d8be2deb1e17c6860b1d30732b323b4"
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
]
deps: misc updates
2020-12-29 20:21:50 +03:00
[[package]]
name = "semver"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f301af10236f6df4160f7c3f04eec6dbc70ace82d23326abad5edee88801c6b6"
dependencies = [
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"semver-parser",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-13 06:22:05 +03:00
version = "1.0.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "bebd363326d05ec3e2f532ab7660680f3b02130d780c299bca73469d521bc0ed"
Add some initial tests to wezterm-ssh, ignoring read/write of file as those are hanging
2021-09-24 21:57:05 +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
2023-03-20 06:20:34 +03:00
version = "1.0.157"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
checksum = "707de5fcf5df2b5788fca98dd7eab490bc2fd9b7ef1404defc462833b83f25ca"
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
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "serde_cbor"
version = "0.11.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2bef2ebfde456fb76bbcf9f59315333decc4fda0b2b44b420243c11e0f5ec1f5"
dependencies = [
cargo update
2022-10-10 06:26:07 +03:00
"half 1.8.2",
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +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
[[package]]
name = "serde_derive"
cargo update
2023-03-20 06:20:34 +03:00
version = "1.0.157"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
checksum = "78997f4555c22a7971214540c4a661291970619afd56de19f77e0de86296e1e5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 2.0.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
]
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
2023-03-06 08:18:33 +03:00
version = "1.0.94"
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
2023-03-06 08:18:33 +03:00
checksum = "1c533a59c9d8a93a09c6ab31f0fd5e5f4dd1b8fc9434804029839884765d04ea"
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 = [
cargo update
2023-02-17 21:30:15 +03:00
"itoa",
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
"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
2023-03-20 06:20:34 +03:00
version = "0.1.12"
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
2023-03-20 06:20:34 +03:00
checksum = "bcec881020c684085e55a25f7fd888954d56609ef363479dc5a1305eb0d40cab"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 2.0.2",
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 toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
[[package]]
name = "serde_spanned"
cargo update
2023-02-06 07:53:11 +03:00
version = "0.6.1"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-06 07:53:11 +03:00
checksum = "0efd8caf556a6cebd3b285caf480045fcc1ac04f6bd786b09a6f11af30c4fcf4"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
dependencies = [
"serde",
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "serde_urlencoded"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3491c14715ca2294c4d6a88f15e84739788c1d030eed8c110436aafdaa2f3fd"
dependencies = [
"form_urlencoded",
cargo update
2023-02-17 21:30:15 +03:00
"itoa",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"ryu",
"serde",
]
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
[[package]]
name = "serde_with"
cargo update
2023-03-13 06:22:05 +03:00
version = "2.3.1"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "85456ffac572dc8826334164f2fb6fb40a7c766aebe195a2a21ee69ee2885ecf"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
dependencies = [
deps: update base64 closes: https://github.com/wez/wezterm/pull/2855
2022-12-12 19:14:42 +03:00
"base64 0.13.1",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
"chrono",
"hex",
"indexmap",
"serde",
"serde_json",
"serde_with_macros",
cargo update
2023-02-27 08:32:52 +03:00
"time 0.3.20",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
]
[[package]]
name = "serde_with_macros"
cargo update
2023-03-13 06:22:05 +03:00
version = "2.3.1"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "7cbcd6104f8a4ab6af7f6be2a0da6be86b9de3c401f6e86bb856ab2af739232f"
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
dependencies = [
"darling",
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
]
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
[[package]]
name = "serde_yaml"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.9.19"
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "f82e6c8c047aa50a7328632d067bcae6ef38772a79e28daf32f735e0e4f3dd10"
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
dependencies = [
"indexmap",
cargo update
2023-02-17 21:30:15 +03:00
"itoa",
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
"ryu",
"serde",
deps: update serde_yaml
2022-08-01 06:37:19 +03:00
"unsafe-libyaml",
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +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
]
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
[[package]]
name = "sha1"
deps: cargo update
2022-09-16 17:48:12 +03:00
version = "0.10.5"
cargo update
2022-01-17 04:46:30 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: cargo update
2022-09-16 17:48:12 +03:00
checksum = "f04293dc80c3993519f2d7f6f511707ee7094fe0c6d3406feb330cdb3540eba3"
cargo update
2022-01-17 04:46:30 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
cargo update
2022-09-12 16:26:10 +03:00
"cpufeatures",
cargo update
2022-11-21 08:18:37 +03:00
"digest 0.10.6",
cargo update
2022-01-17 04:46:30 +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
2023-01-16 07:48:20 +03:00
"cfg-if",
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",
cargo update
2022-08-01 06:14:19 +03:00
"opaque-debug",
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
2023-01-16 07:48:20 +03:00
[[package]]
name = "sha2"
version = "0.10.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "82e6b795fe2e3b1e845bafcb27aa35405c4d47cdfc92af5fc8d3002f76cebdc0"
dependencies = [
"cfg-if",
"cpufeatures",
"digest 0.10.6",
]
lua: add wezterm.GLOBAL
2022-06-19 07:31:53 +03:00
[[package]]
name = "share-data"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"lazy_static",
"luahelper",
wezterm.GLOBAL now returns references to stored data This smoothes out a rough edge and makes things work more naturally. refs: https://github.com/wez/wezterm/discussions/2983
2023-01-25 04:26:14 +03:00
"ordered-float",
lua: add wezterm.GLOBAL
2022-06-19 07:31:53 +03:00
"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 = "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"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.3.15"
cargo update
2021-02-08 09:51:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "732768f1176d21d09e076c23a93123d40bba92d50c4058da34d45c8de8e682b9"
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
2023-02-17 21:30:15 +03:00
version = "1.4.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
2023-02-17 21:30:15 +03:00
checksum = "d8229b473baa5980ac72ef434c4415e70c4b5e71b423043adb4ba059f89c99a1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-06 07:53:11 +03:00
[[package]]
name = "simd-adler32"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.3.5"
cargo update
2023-02-06 07:53:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "238abfbb77c1915110ad968465608b68e869e0772622c9656714e73e5a1a522f"
cargo update
2023-02-06 07:53:11 +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 = "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
2023-02-27 08:32:52 +03:00
version = "0.4.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-27 08:32:52 +03:00
checksum = "6528351c9bc8ab22353f9d776db39a20288e8d6c37ef8cfe3317cf875eecfc2d"
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
dependencies = [
"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
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "slotmap"
version = "1.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e1e08e261d0e8f5c43123b7adf3e4ca1690d655377ac93a03b2c9d3e98de1342"
dependencies = [
"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 = "smallvec"
cargo update
2022-10-04 17:44:55 +03:00
version = "1.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-10-04 17:44:55 +03:00
checksum = "a507befe795404456341dfab10cef66ead4c041f62b8b11bbb92bffe5d0953e0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
deps: sctk -> 0.16
2023-02-04 17:49:30 +03:00
version = "0.16.0"
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"
deps: sctk -> 0.16
2023-02-04 17:49:30 +03:00
checksum = "f307c47d32d2715eb2e0ece5589057820e0e5e70d07c247d1063e844e107f454"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
cargo update
2023-02-27 08:32:52 +03:00
"memmap2 0.5.10",
deps: sctk -> 0.16
2023-02-04 17:49:30 +03:00
"nix 0.24.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
2022-12-05 05:40:53 +03:00
version = "1.3.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
2022-12-05 05:40:53 +03:00
checksum = "13f2b548cd8447f8de0fdf1c592929f70f4fc7039a05e47404b0d096ec6987a1"
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
]
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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-02-15 23:14:00 +03:00
[[package]]
name = "socket2"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.4.9"
cargo update
2021-02-15 23:14:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "64a4a911eed85daf18834cfaa86a79b7d266ff93ff5ba14005426219480ed662"
cargo update
2021-02-15 23:14:00 +03:00
dependencies = [
"libc",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
cargo update
2021-02-15 23:14:00 +03:00
]
deps: socket2 -> 0.5
2023-02-27 08:33:28 +03:00
[[package]]
name = "socket2"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc8d618c6641ae355025c449427f9e96b98abf99a772be3cef6708d15c77147a"
dependencies = [
"libc",
"windows-sys 0.45.0",
]
lua: add wezterm.time and Time object Includes a method for determining sunrise/sunset.
2022-07-17 21:38:02 +03:00
[[package]]
name = "spa"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "188e0376df998cb9f953a6d4ceb8556fe9223d1f3386e5c0cdb69aab31d62f1b"
dependencies = [
"chrono",
]
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",
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +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
"luahelper",
"smol",
"wezterm-dynamic",
add own open_url crate The upstream open crate keeps making stuff async/blocking/not-working on windows, so this is a step towards removing this dependency. refs: https://github.com/wez/wezterm/issues/3288
2023-03-19 22:44:12 +03:00
"wezterm-open-url",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.9.6"
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
2023-03-17 22:02:21 +03:00
checksum = "b5d6e0250b93c8427a177b849d144a96d5acc57006149479403d7861ab721e34"
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 = [
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"lock_api",
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
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "spirv"
version = "0.2.0+1.5.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "246bfa38fe3db3f1dfc8ca5a2cdeb7348c78be2112740cc0ec8ef18b6d94f830"
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"num-traits",
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "sqlite-cache"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "012429babedb75518d1b6935abcee30852d1650c05c6eaf4e29ae335ae6e173b"
dependencies = [
"data-encoding",
"futures",
"rusqlite",
"tracing",
]
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"
cargo update
2023-01-23 08:02:26 +03:00
version = "0.9.4"
ssh: my openssl+windows ssh2 patch was published upstream So remove my local patch
2021-10-10 17:29:54 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-23 08:02:26 +03:00
checksum = "e7fe461910559f6d5604c3731d00d2aafc4a83d1665922e280f42f9a168d5455"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 1.3.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
"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 = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
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
"core-foundation 0.7.0",
"lazycell",
"libc",
"mach",
cargo update
2022-12-05 05:40:53 +03:00
"nix 0.23.2",
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
"num-traits",
"uom",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
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"
deps: tiny-skia 0.7 -> 0.8
2022-08-29 06:50:27 +03:00
[[package]]
name = "strict-num"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9df65f20698aeed245efdde3628a6b559ea1239bbb871af1b6e3b58c413b2bd1"
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
move strip-ansi-escapes into its own crate
2020-10-03 09:54:54 +03:00
"termwiz",
]
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"
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
2023-02-27 08:32:52 +03:00
version = "1.0.109"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-27 08:32:52 +03:00
checksum = "72b64191b275b66ffe2469e8af2c1cfe3bafa67b529ead792a6d0160888b4237"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
cargo update
2022-05-23 18:18:06 +03:00
"unicode-ident",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
[[package]]
name = "syn"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "59d3276aee1fa0c33612917969b5172b5be2db051232a6e4826f1a1a9191b045"
dependencies = [
"proc-macro2",
"quote",
"unicode-ident",
]
colorschemes: expand to include Gogh color schemes This commit expands the toml file definition to include metadata for the origin url, author and name. A new sync utility fills out that metadata when it pulls from the iterm2 color schemes repo. The utility also pulls down the scheme data json maintained by the Gogh project: https://gogh-co.github.io/Gogh/ and converts it to wezterm's format. About 50% of Gogh overlaps with iterm2; we take the iterm2 versions of those schemes by default because the iterm2 data has more info about things like cursor and selection colors. The sync utility is responsible for compiling the de-duplicated set of scheme data into a form that is used by wezterm and its docs.
2022-07-10 23:26:33 +03:00
[[package]]
name = "sync-color-schemes"
version = "0.1.0"
dependencies = [
"anyhow",
color schemes: move other color scheme format code to color-funcs I want to add lua funcs for importing schemes; this is a step towards that.
2022-07-14 07:29:51 +03:00
"color-funcs",
colorschemes: expand to include Gogh color schemes This commit expands the toml file definition to include metadata for the origin url, author and name. A new sync utility fills out that metadata when it pulls from the iterm2 color schemes repo. The utility also pulls down the scheme data json maintained by the Gogh project: https://gogh-co.github.io/Gogh/ and converts it to wezterm's format. About 50% of Gogh overlaps with iterm2; we take the iterm2 versions of those schemes by default because the iterm2 data has more info about things like cursor and selection colors. The sync utility is responsible for compiling the de-duplicated set of scheme data into a form that is used by wezterm and its docs.
2022-07-10 23:26:33 +03:00
"config",
color schemes: add alias concept Various color schemes have been duplicated as they have been added to different scheme collections. They don't always have identical names (eg: some remove spaces) and sometimes they have very different names (eg: _bash vs. nightfox, or Miu vs. Blazer). We already detected duplicates from different collections but previously we would omit those dupes. This commit allows us to track those duplicates by recording their aliases. When we write out our data, we only include "interesting" alias names; those where the name isn't trivially identical. Some scheme collections (eg: iterm2 color schemes) have duplicates (eg: zenbones and zenbones_light are identical) and we have previously shipped with both of those names, so we special case to emit dupes for which we have prior version information in order to avoid breaking backwards compatibility for our users. In the doc generation we can generate links to the aliases if we included them, but also note about the other names and how we don't include them. That is so that someone searching the docs for say "_bash" can discover that it is actually a duplicate of "nightfox" and use nightfox instead.
2022-07-20 17:32:46 +03:00
"env_logger",
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
"futures",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"lazy_static",
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
"libflate",
color schemes: add alias concept Various color schemes have been duplicated as they have been added to different scheme collections. They don't always have identical names (eg: some remove spaces) and sometimes they have very different names (eg: _bash vs. nightfox, or Miu vs. Blazer). We already detected duplicates from different collections but previously we would omit those dupes. This commit allows us to track those duplicates by recording their aliases. When we write out our data, we only include "interesting" alias names; those where the name isn't trivially identical. Some scheme collections (eg: iterm2 color schemes) have duplicates (eg: zenbones and zenbones_light are identical) and we have previously shipped with both of those names, so we special case to emit dupes for which we have prior version information in order to avoid breaking backwards compatibility for our users. In the doc generation we can generate links to the aliases if we included them, but also note about the other names and how we don't include them. That is so that someone searching the docs for say "_bash" can discover that it is actually a duplicate of "nightfox" and use nightfox instead.
2022-07-20 17:32:46 +03:00
"log",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"reqwest",
"rusqlite",
colorschemes: expand to include Gogh color schemes This commit expands the toml file definition to include metadata for the origin url, author and name. A new sync utility fills out that metadata when it pulls from the iterm2 color schemes repo. The utility also pulls down the scheme data json maintained by the Gogh project: https://gogh-co.github.io/Gogh/ and converts it to wezterm's format. About 50% of Gogh overlaps with iterm2; we take the iterm2 versions of those schemes by default because the iterm2 data has more info about things like cursor and selection colors. The sync utility is responsible for compiling the de-duplicated set of scheme data into a form that is used by wezterm and its docs.
2022-07-10 23:26:33 +03:00
"serde",
"serde_json",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"sqlite-cache",
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
"tar",
"tempfile",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"tokio",
cargo update
2023-03-17 22:02:21 +03:00
"toml 0.7.3",
colorschemes: expand to include Gogh color schemes This commit expands the toml file definition to include metadata for the origin url, author and name. A new sync utility fills out that metadata when it pulls from the iterm2 color schemes repo. The utility also pulls down the scheme data json maintained by the Gogh project: https://gogh-co.github.io/Gogh/ and converts it to wezterm's format. About 50% of Gogh overlaps with iterm2; we take the iterm2 versions of those schemes by default because the iterm2 data has more info about things like cursor and selection colors. The sync utility is responsible for compiling the de-duplicated set of scheme data into a form that is used by wezterm and its docs.
2022-07-10 23:26:33 +03:00
"wezterm-dynamic",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"yaml-rust",
colorschemes: expand to include Gogh color schemes This commit expands the toml file definition to include metadata for the origin url, author and name. A new sync utility fills out that metadata when it pulls from the iterm2 color schemes repo. The utility also pulls down the scheme data json maintained by the Gogh project: https://gogh-co.github.io/Gogh/ and converts it to wezterm's format. About 50% of Gogh overlaps with iterm2; we take the iterm2 versions of those schemes by default because the iterm2 data has more info about things like cursor and selection colors. The sync utility is responsible for compiling the de-duplicated set of scheme data into a form that is used by wezterm and its docs.
2022-07-10 23:26:33 +03:00
]
Add support for heap profiling using dhat refs: https://github.com/wez/wezterm/issues/2626
2022-11-14 23:26:02 +03:00
[[package]]
name = "sys-info"
version = "0.9.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0b3a0d0aba8bf96a0e1ddfdc352fc53b3df7f39318c71854910c3c4b024ae52c"
dependencies = [
"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 = "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
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
[[package]]
name = "tar"
version = "0.4.38"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4b55807c0344e1e6c04d7c965f5289c39a8d94ae23ed5c0b57aabac549f871c6"
dependencies = [
"filetime",
"libc",
"xattr",
]
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
2023-02-27 08:32:52 +03:00
version = "3.4.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
2023-02-27 08:32:52 +03:00
checksum = "af18f7ae1acd354b992402e9ec5864359d693cd8a79dcbef59f76891701c1e95"
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 = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
cargo update, including updating zbus to 2.0.0 stable
2022-01-10 05:29:29 +03:00
"fastrand",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"redox_syscall",
cargo update
2023-02-27 08:32:52 +03:00
"rustix",
"windows-sys 0.42.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
]
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +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
2023-01-16 07:48:20 +03:00
checksum = "be55cf8942feac5c765c2c993422806843c9a9a45d4d5c407ad6dd2ea95eb9b6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +03:00
version = "0.7.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
2023-01-16 07:48:20 +03:00
checksum = "da31aef70da0f6352dbcb462683eb4dd2bfad01cf3fc96cf204547b9a839a585"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-16 07:48:20 +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",
cargo update
2023-01-16 07:48:20 +03:00
"phf 0.11.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
"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
2023-03-17 22:02:21 +03:00
version = "0.4.1"
cargo update
2021-10-11 05:15:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "3369f5ac52d5eb6ab48c6b4ffdc8efbcad6b89c765749064ba298f2c68a16a76"
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"
Image decoding is now done in a bg thread Continuing from the previous commit, this shifts: * In-memory data -> temporary file * Image decoding -> background thread The background thread asynchronously decodes frames and sends them to the render thread via a bounded channel. While decoding frames, it writes them, uncompressed, to a scratch file so that when the animation loops, it is a very cheap operation to rewind and pull that data from the file, without having to burn CPU to re-decode the data from the start. Memory usage is bounded to 4 uncompressed frames while decoding, then 3 uncompressed frames (triple buffered) while looping over the rest. However, disk usage is N uncompressed frames. refs: https://github.com/wez/wezterm/issues/3263
2023-03-17 21:11:46 +03:00
version = "0.21.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",
update base64, work around another batch of breaking API changes closes: https://github.com/wez/wezterm/pull/2931
2023-01-09 04:49:45 +03:00
"base64 0.21.0",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.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
"cassowary",
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
"criterion",
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",
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
"finl_unicode",
termwiz: add clustered line storage for line Adds the option to use an alternative clusted line storage for the cells component of the line. This structure is not optimal for mutation, but is better structured for: * matching/extracting textual content * using less memory than the prior simple vector For some contrast: the line "hello" occupies 5 Cells in the cell based storage; that 5 discrete Cells each with their own tiny string and a copy of their attributes. The clustered version of the line stores one copy of the cell attributes, the string "hello" and some small (almost constant size) overhead for some metadata. For simple lines of ascii text, the clustered version is smaller as there are fewer copies of the cell attributes. Over the span of a large scrollback and typical terminal display composition, this saving is anticipated to be significant. The clustered version is also cheaper to search as it doesn't require building a copy of the search text for each line (provided the line is already in clustered form). This commit introduces the capability: none of the internals request the new form yet, and there are likely a few call sites that need to be tweaked to avoid coersion from clustered to vector form.
2022-07-23 21:51:55 +03:00
"fixedbitset",
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",
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",
cargo update
2022-12-05 05:40:53 +03:00
"nix 0.24.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
"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",
cargo update
2023-01-16 07:48:20 +03:00
"sha2 0.9.9",
cargo update
2021-02-08 09:51:28 +03:00
"signal-hook 0.1.17",
Adjust render caching; switch to LFU caches from LRU
2022-08-28 20:27:50 +03:00
"siphasher",
Image decoding is now done in a bg thread Continuing from the previous commit, this shifts: * In-memory data -> temporary file * Image decoding -> background thread The background thread asynchronously decodes frames and sends them to the render thread via a bounded channel. While decoding frames, it writes them, uncompressed, to a scratch file so that when the animation loops, it is a very cheap operation to rewind and pull that data from the file, without having to burn CPU to re-decode the data from the start. Memory usage is bounded to 4 uncompressed frames while decoding, then 3 uncompressed frames (triple buffered) while looping over the rest. However, disk usage is N uncompressed frames. refs: https://github.com/wez/wezterm/issues/3263
2023-03-17 21:11:46 +03:00
"tempfile",
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",
ImageDataType::File -> EncodedLease Adopt the new blob lease layer to storing and referencing image files. This reduces the number of open files needed when images are being displayed in the terminal. refs: https://github.com/wez/wezterm/issues/3263
2023-03-19 06:32:49 +03:00
"wezterm-blob-leases",
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
"finl_unicode",
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
"lazy_static",
"luahelper",
"terminfo",
"termwiz",
"wezterm-dynamic",
]
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
dependencies = [
"unicode-width",
]
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
[[package]]
name = "textwrap"
deps: textwrap -> 0.16 closes: https://github.com/wez/wezterm/pull/2664
2022-10-24 06:50:47 +03:00
version = "0.16.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.16 closes: https://github.com/wez/wezterm/pull/2664
2022-10-24 06:50:47 +03:00
checksum = "222a222a5bfe1bba4a77b45ec488a741b3cb8872e5e499451fd7d0129c9c7c3d"
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
2023-03-20 06:20:34 +03:00
version = "1.0.40"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
checksum = "978c9a314bd8dc99be594bc3c175faaa9794be04a5a5e153caba6915336cebac"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
version = "1.0.40"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
checksum = "f9456a42c5b0d803c8cd86e73dd7cc9edd429499f37a3550d286d5e86720569f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 2.0.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 support for heap profiling using dhat refs: https://github.com/wez/wezterm/issues/2626
2022-11-14 23:26:02 +03:00
[[package]]
name = "thousands"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3bf63baf9f5039dadc247375c29eb13706706cfde997d0330d05aa63a77d8820"
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
2023-02-17 21:30:15 +03:00
version = "1.1.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
2023-02-17 21:30:15 +03:00
checksum = "3fdd6f064ccff2d6567adcb3873ca630700f00b5ad3f060c25b5dcfd9a4ce152"
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 = [
cargo update
2023-02-17 21:30:15 +03:00
"cfg-if",
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: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "tiff"
cargo update
2022-12-12 19:02:19 +03:00
version = "0.8.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-12-12 19:02:19 +03:00
checksum = "7449334f9ff2baf290d55d73983a7d6fa15e01198faef72af07e2a8db851e471"
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2023-02-27 08:32:52 +03:00
version = "0.3.20"
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-27 08:32:52 +03:00
checksum = "cd0cbfecb4d19b5ea75bb31ad904eb5b9fa13f21079c3b92017ebdf4999a5890"
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
dependencies = [
cargo update
2023-02-17 21:30:15 +03:00
"itoa",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
"serde",
deps: cargo update
2022-11-01 17:09:37 +03:00
"time-core",
"time-macros",
deps: update to rcgen 0.9
2022-05-05 05:33:17 +03:00
]
deps: cargo update
2022-11-01 17:09:37 +03:00
[[package]]
name = "time-core"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2e153e1f1acaef8acc537e68b44906d2db6436e2b35ac2c6b42640fff91f00fd"
lua: add wezterm.time and Time object Includes a method for determining sunrise/sunset.
2022-07-17 21:38:02 +03:00
[[package]]
name = "time-funcs"
version = "0.1.0"
dependencies = [
"anyhow",
"chrono",
"config",
lua: add wezterm.time.call_after and wezterm.reload_configuration These allow setting up some basic timers and constructing time-dependent config files. Needs to be used respsonsibly!
2022-07-18 16:38:36 +03:00
"lazy_static",
lua: add wezterm.time and Time object Includes a method for determining sunrise/sunset.
2022-07-17 21:38:02 +03:00
"luahelper",
lua: add wezterm.time.call_after and wezterm.reload_configuration These allow setting up some basic timers and constructing time-dependent config files. Needs to be used respsonsibly!
2022-07-18 16:38:36 +03:00
"promise",
"smol",
lua: add wezterm.time and Time object Includes a method for determining sunrise/sunset.
2022-07-17 21:38:02 +03:00
"spa",
"wezterm-dynamic",
]
deps: cargo update
2022-11-01 17:09:37 +03:00
[[package]]
name = "time-macros"
cargo update
2023-02-27 08:32:52 +03:00
version = "0.2.8"
deps: cargo update
2022-11-01 17:09:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-27 08:32:52 +03:00
checksum = "fd80a657e71da814b8e5d60d3374fc6d35045062245d80224748ae522dd76f36"
deps: cargo update
2022-11-01 17:09:37 +03:00
dependencies = [
"time-core",
]
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"
cargo update
2023-02-06 07:53:11 +03:00
version = "0.8.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"
cargo update
2023-02-06 07:53:11 +03:00
checksum = "bfef3412c6975196fdfac41ef232f910be2bb37b9dd3313a49a1a6bc815a5bdb"
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",
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: image -> 0.24
2022-02-07 04:51:32 +03:00
"png",
deps: tiny-skia -> 0.7 closes: #2219
2022-07-04 16:30:34 +03:00
"tiny-skia-path",
]
[[package]]
name = "tiny-skia-path"
cargo update
2023-02-06 07:53:11 +03:00
version = "0.8.3"
deps: tiny-skia -> 0.7 closes: #2219
2022-07-04 16:30:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-06 07:53:11 +03:00
checksum = "a4b5edac058fc98f51c935daea4d805b695b38e2f151241cad125ade2a2ac20d"
deps: tiny-skia -> 0.7 closes: #2219
2022-07-04 16:30:34 +03:00
dependencies = [
"arrayref",
"bytemuck",
deps: tiny-skia 0.7 -> 0.8
2022-08-29 06:50:27 +03:00
"strict-num",
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
]
termwiz: add criterion benches for wcwidth
2022-04-30 01:14:02 +03:00
[[package]]
name = "tinytemplate"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "be4d6b5f19ff7664e8c98d03e2139cb510db9b0a60b55f8e8709b689d939b6bc"
dependencies = [
"serde",
"serde_json",
]
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"
cargo update
2023-02-06 07:53:11 +03:00
version = "0.1.1"
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
2023-02-06 07:53:11 +03:00
checksum = "1f3ccbac311fea05f86f61904b462b55fb3df8837a366dfc601a0161d0532f20"
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
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "tokio"
cargo update
2023-03-06 08:18:33 +03:00
version = "1.26.0"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "03201d01c3c27a29c8a5cee5b55a93ddae1ccf6f08f65365c2c918f8c1b76f64"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
"autocfg",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"bytes",
"libc",
"memchr",
"mio",
"num_cpus",
"pin-project-lite",
cargo update
2023-03-06 08:18:33 +03:00
"socket2 0.4.9",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
"tokio-macros",
cargo update
2023-03-06 08:18:33 +03:00
"windows-sys 0.45.0",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
]
[[package]]
name = "tokio-macros"
cargo update
2022-12-05 05:40:53 +03:00
version = "1.8.2"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-12-05 05:40:53 +03:00
checksum = "d266c00fde287f55d3f1c3e96c500c362a2b8c695076ec180f27918820bc6df8"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
]
[[package]]
name = "tokio-native-tls"
cargo update
2023-02-09 07:25:41 +03:00
version = "0.3.1"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-09 07:25:41 +03:00
checksum = "bbae76ab933c85776efabc971569dd6119c580d8f5d448769dec1764bf796ef2"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
"native-tls",
"tokio",
]
[[package]]
name = "tokio-util"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.7.7"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "5427d89453009325de0d8f342c9490009f76e999cb7672d77e46267448f7e6b2"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
dependencies = [
"bytes",
"futures-core",
"futures-sink",
"pin-project-lite",
"tokio",
"tracing",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2023-01-21 06:04:49 +03:00
version = "0.5.11"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-01-21 06:04:49 +03:00
checksum = "f4f7f0dd8d50a853a531c426359045b1998f04219d88799810762cd4ad314234"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
[[package]]
name = "toml"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.7.3"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "b403acf6f2bb0859c93c7f0d967cb4a75a7ac552100f9322faf64dc047669b21"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
dependencies = [
"serde",
"serde_spanned",
cargo update
2023-03-06 08:18:33 +03:00
"toml_datetime",
"toml_edit",
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
]
[[package]]
name = "toml_datetime"
cargo update
2023-02-06 07:53:11 +03:00
version = "0.6.1"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-06 07:53:11 +03:00
checksum = "3ab8ed2edee10b50132aed5f331333428b011c99402b5a534154ed15746f9622"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
dependencies = [
"serde",
]
[[package]]
name = "toml_edit"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.19.7"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "dc18466501acd8ac6a3f615dd29a3438f8ca6bb3b19537138b3106e575621274"
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
dependencies = [
"indexmap",
"serde",
"serde_spanned",
cargo update
2023-03-06 08:18:33 +03:00
"toml_datetime",
cargo update
2023-02-27 08:32:52 +03:00
"winnow",
deps: update toml -> 0.7, cargo update
2023-01-30 07:08:25 +03:00
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "tower-service"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b6bc1c9ce2b5135ac7f93c72918fc37feb872bdc6a5533a8b85eb4b86bfdae52"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
[[package]]
name = "tracing"
cargo update
2022-10-10 06:26:07 +03:00
version = "0.1.37"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-10-10 06:26:07 +03:00
checksum = "8ce8c33a8d48bd45d624a6e523445fd21ec13d3653cd51f681abf67418f54eb8"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
"pin-project-lite",
"tracing-attributes",
"tracing-core",
]
[[package]]
name = "tracing-attributes"
cargo update
2022-10-10 06:26:07 +03:00
version = "0.1.23"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-10-10 06:26:07 +03:00
checksum = "4017f8f45139870ca7e672686113917c71c7a6e02d4924eda67186083c03081a"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
dependencies = [
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
]
[[package]]
name = "tracing-core"
cargo update
2022-10-10 06:26:07 +03:00
version = "0.1.30"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-10-10 06:26:07 +03:00
checksum = "24eb03ba0eab1fd845050058ce5e616558e8f8d8fca633e6b163fe25c797213a"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
dependencies = [
"once_cell",
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "try-lock"
cargo update
2023-01-08 17:46:31 +03:00
version = "0.2.4"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-01-08 17:46:31 +03:00
checksum = "3528ecfd12c466c6f163363caf2d02a71161dd5e1cc6ae7b34207ea2d42d81ed"
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +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"
cargo update
2022-12-12 19:02:19 +03:00
version = "1.16.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"
cargo update
2022-12-12 19:02:19 +03:00
checksum = "497961ef93d974e23eb6f433eb5fe1b7930b659f06d12dec6fc44a8f554c0bba"
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"
cargo update
2022-09-04 04:54:36 +03:00
version = "0.1.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-09-04 04:54:36 +03:00
checksum = "9e79c4d996edb816c91e4308506774452e55e95c3c9de07b6729e17e15a5ef81"
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
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2022-05-23 18:18:06 +03:00
version = "1.0.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-23 18:18:06 +03:00
checksum = "ce65604324d3cce9b966701489fbd0cf318cb1f7bd9dd07ac9a4ee6fb791930d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-05-23 18:18:06 +03:00
"tempfile",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-17 22:02:21 +03:00
version = "0.3.12"
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
2023-03-17 22:02:21 +03:00
checksum = "7d502c968c6a838ead8e69b2ee18ec708802f99db92a0d156705ec9ef801993b"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
cargo update
2022-05-23 18:18:06 +03:00
[[package]]
name = "unicode-ident"
cargo update
2023-03-06 08:18:33 +03:00
version = "1.0.8"
cargo update
2022-05-23 18:18:06 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "e5464a87b239f13a63a501f2701565754bae92d243d4bb7eb12f6d57d2269bf4"
cargo update
2022-05-23 18:18:06 +03:00
cargo update
2021-06-07 18:32:05 +03:00
[[package]]
name = "unicode-linebreak"
cargo update
2022-10-04 17:44:55 +03:00
version = "0.1.4"
cargo update
2021-06-07 18:32:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2022-10-04 17:44:55 +03:00
checksum = "c5faade31a542b8b35855fff6e8def199853b2da8da256da52f52f1316ee3137"
cargo update
2021-06-07 18:32:05 +03:00
dependencies = [
cargo update
2022-09-19 06:00:54 +03:00
"hashbrown 0.12.3",
cargo update
2021-06-07 18:32:05 +03:00
"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
2022-09-19 06:00:54 +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"
cargo update
2022-09-19 06:00:54 +03:00
checksum = "5c5713f0fc4b5db668a2ac63cdb7bb4469d8c9fed047b1d0292cc7b0ce2ba921"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-06 07:53:11 +03:00
version = "1.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
2023-02-06 07:53:11 +03:00
checksum = "1dd624098567895118886609431a7c3b8f516e41d30e0643f03d94592a147e36"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
deps: cargo update
2022-09-16 17:48:12 +03:00
version = "0.1.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"
deps: cargo update
2022-09-16 17:48:12 +03:00
checksum = "c0edd1e5b14653f783770bce4a4dabb4a5108a5370a5f5d8cfe8710c361f6c8b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "unicode-xid"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f962df74c8c05a667b5ee8bcf162993134c104e96440b663c8daa176dc772d8c"
deps: update serde_yaml
2022-08-01 06:37:19 +03:00
[[package]]
name = "unsafe-libyaml"
cargo update
2023-03-06 08:18:33 +03:00
version = "0.2.7"
deps: update serde_yaml
2022-08-01 06:37:19 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-06 08:18:33 +03:00
checksum = "ad2024452afd3874bf539695e04af6732ba06517424dbf958fdb16a01f3bef6c"
deps: update serde_yaml
2022-08-01 06:37:19 +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
2022-09-12 16:26:10 +03:00
version = "2.3.1"
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-09-12 16:26:10 +03:00
checksum = "0d68c799ae75762b8c3fe375feb6600ef5602c883c5d21eb51c09f22b83c4643"
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",
"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"
cargo update
2023-03-13 06:22:05 +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
2023-03-13 06:22:05 +03:00
checksum = "711b9620af191e0cdc7468a8d14e709c3dcdb115b36f838e601583af800a370a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 wezterm-blob-leases crate
2023-03-18 22:21:30 +03:00
[[package]]
name = "uuid"
version = "1.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1674845326ee10d37ca60470760d4288a6f80f304007d92e5c53bab78c9cfd79"
dependencies = [
"atomic",
"getrandom",
"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 = "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
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-12-05 05:40:53 +03:00
version = "0.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-12-05 05:40:53 +03:00
checksum = "d3b17ae1f6c8a2b28506cd96d412eebf83b4a0ff2cbefeeb952f2f9dfa44ba18"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
termwiz: ensure ST sequence is grouped with OSC When `parse_first_as_vec` is parsing an OSC sequence (e.g. `SetHyperlink`) that is terminated by the escaped form of ST (`ESC \`), ensure that the ST sequence is included in the returned vector. This is achieved by ensuring the VTParser has returned to the "ground" state: i.e. the stored state after the `ESC` is processed is not enough for `parse_first_as_vec` to terminate. We must also parse the `\` to ensure that we return a complete span to the caller. Fixes https://github.com/markbt/streampager/issues/57
2022-08-01 23:29:19 +03:00
version = "0.6.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 = [
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
2023-03-17 22:02:21 +03:00
version = "2.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
2023-03-17 22:02:21 +03:00
checksum = "36df944cda56c7d8d8b7496af378e6b16de9284591917d307c9b4d313c44e698"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
"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
]
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "want"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1ce8a968cb1cd110d136ff8b819a556d6fb6d919363c61534f6860c7eb172ba0"
dependencies = [
"log",
"try-lock",
]
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
2023-02-06 07:53:11 +03:00
version = "0.2.84"
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
2023-02-06 07:53:11 +03:00
checksum = "31f8dcbc21f30d9b8f2ea926ecb58f6b91192c17e9d33594b3df58b2007ca53b"
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
2023-01-16 07:48:20 +03:00
"cfg-if",
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
2023-02-06 07:53:11 +03:00
version = "0.2.84"
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
2023-02-06 07:53:11 +03:00
checksum = "95ce90fd5bcc06af55a641a86428ee4229e44e07033963a2290a8e241607ccb9"
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",
"log",
cargo update
2022-08-01 06:14:19 +03:00
"once_cell",
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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
2023-02-06 07:53:11 +03:00
version = "0.4.34"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-06 07:53:11 +03:00
checksum = "f219e0d211ba40266969f6dbdd90636da12f75bee4fc9d6c23d1260dadb51454"
cargo update
2020-05-26 08:25:39 +03:00
dependencies = [
cargo update
2023-01-16 07:48:20 +03:00
"cfg-if",
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
2023-02-06 07:53:11 +03:00
version = "0.2.84"
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
2023-02-06 07:53:11 +03:00
checksum = "4c21f77c0bedc37fd5dc21f897894a5ca01e7bb159884559461862ae90c0b4c5"
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
2023-02-06 07:53:11 +03:00
version = "0.2.84"
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
2023-02-06 07:53:11 +03:00
checksum = "2aff81306fcac3c7515ad4e177f521b5c9a15f2b08f4e32d823066102f35a5f6"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
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
2023-02-06 07:53:11 +03:00
version = "0.2.84"
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
2023-02-06 07:53:11 +03:00
checksum = "0046fef7e28c3804e5e38bfa31ea2a0f73905319b677e57ebe37e49358989b5d"
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
2022-08-29 06:48:33 +03:00
version = "0.29.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-08-29 06:48:33 +03:00
checksum = "3f3b068c05a039c9f755f881dc50f01732214f5685e379829759088967c46715"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 1.3.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
"downcast-rs",
"libc",
cargo update
2022-12-05 05:40:53 +03:00
"nix 0.24.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
2022-08-29 06:48:33 +03:00
version = "0.29.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-08-29 06:48:33 +03:00
checksum = "8691f134d584a33a6606d9d717b95c4fa20065605f798a3f350d78dced02a902"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-12-05 05:40:53 +03:00
"nix 0.24.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",
deps: migrate from ratelimit_meter -> governor This appeases some dependabot warnings regarding the use of an old version of parking_lot that has some unsoundness issues. ratelimit_meter is frozen and is succeeded by governor which has a mostly similar API.
2022-06-08 08:55:01 +03:00
"smallvec",
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
2022-08-29 06:48:33 +03:00
version = "0.29.5"
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
2022-08-29 06:48:33 +03:00
checksum = "6865c6b66f13d6257bef1cd40cbfe8ef2f150fb8ebbdb1e8e873455931377661"
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-12-05 05:40:53 +03:00
"nix 0.24.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
2022-08-29 06:48:33 +03:00
version = "0.29.5"
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
2022-08-29 06:48:33 +03:00
checksum = "402de949f81a012926d821a2d659f930694257e76dd92b6e0042ceb27be4107d"
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
2022-08-29 06:48:33 +03:00
version = "0.29.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-08-29 06:48:33 +03:00
checksum = "b950621f9354b322ee817a23474e479b34be96c2e909c14f7bc0100e9a970bc6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-03-20 06:20:34 +03:00
"bitflags 1.3.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
"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
2022-08-29 06:48:33 +03:00
version = "0.29.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-08-29 06:48:33 +03:00
checksum = "8f4303d8fa22ab852f789e75a967f0a2cdc430a607751c0499bada3e451cbd53"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2022-08-29 06:48:33 +03:00
version = "0.29.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-08-29 06:48:33 +03:00
checksum = "be12ce1a3c39ec7dba25594b97b42cb3195d54953ddb9d3d95a7c3902bc6e9d4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-06 07:53:11 +03:00
version = "0.3.61"
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
2023-02-06 07:53:11 +03:00
checksum = "e33b99f4b23ba3eec1a53ac264e35a755f00e966e0065077d6027c0f575b0b97"
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"
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
version = "0.1.7"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update and address deprecation warnings for csscolorparser
2022-07-18 07:14:47 +03:00
checksum = "9193164d4de03a926d909d3bc7c30543cecb35400c02114792c2cae20d5e2dbb"
cargo update
2020-10-02 17:16:20 +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]]
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",
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
add `wezterm shell-completion` subcommand to generate shell completions
2022-05-28 17:43:28 +03:00
"clap_complete",
Add `fig` to shells for shell completion
2022-08-21 09:48:04 +03:00
"clap_complete_fig",
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
"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",
add `wezterm cli get-text` command closes: https://github.com/wez/wezterm/pull/2729
2023-02-05 19:05:48 +03:00
"termwiz-funcs",
deps: textwrap -> 0.16 closes: https://github.com/wez/wezterm/pull/2664
2022-10-24 06:50:47 +03:00
"textwrap 0.16.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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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"
update cargo.lock for bidi release
2022-10-22 07:46:50 +03:00
version = "0.2.2"
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
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
]
add wezterm-blob-leases crate
2023-03-18 22:21:30 +03:00
[[package]]
name = "wezterm-blob-leases"
version = "0.1.0"
dependencies = [
"getrandom",
"mac_address",
"once_cell",
"serde",
"sha2 0.9.9",
ImageDataType::File -> EncodedLease Adopt the new blob lease layer to storing and referencing image files. This reduces the number of open files needed when images are being displayed in the terminal. refs: https://github.com/wez/wezterm/issues/3263
2023-03-19 06:32:49 +03:00
"tempfile",
add wezterm-blob-leases crate
2023-03-18 22:21:30 +03:00
"thiserror",
"uuid",
]
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",
mux: Pane is now required to be Send+Sync. Use Arc<dyn Pane>
2022-11-23 19:05:30 +03:00
"parking_lot 0.12.1",
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
"portable-pty",
"promise",
"rangeset",
"ratelim",
"smol",
"termwiz",
deps: textwrap -> 0.16 closes: https://github.com/wez/wezterm/pull/2664
2022-10-24 06:50:47 +03:00
"textwrap 0.16.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",
add Pane::get_metadata The idea here is that different kinds of panes may want to expose additional metadata to lua scripts. It would be a bit weird to add a Pane method for each of those and plumb it all the way through the various APIs, so just allowing a pane impl to return a dynamic value (likely an Object) allows a bunch of flexibility. This commit exposes the clientpane is_tardy boolean and the time since the last data was recevied (since_last_response_ms) from the mux client pane implementation: these are used to show the tardiness indicator in the client pane. Exposing this data enables the user to add that info to their status bar if they wish.
2022-09-02 07:27:49 +03:00
"wezterm-dynamic",
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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"
color types version bump for crates.io
2022-08-02 04:41:52 +03:00
version = "0.2.0"
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
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",
lua: add wezterm.color.extract_colors_from_image This function can be used to extra distinct colors from an image to be fed into eg: color scheme generation.
2022-07-11 21:03:06 +03:00
"deltae",
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",
termwiz: ColorSpec now allows for alpha to be tracked This doesn't really change any behavior, but adjusts the types such that CSIs that set colors have the potential to track the alpha channel and that can make it through to the GUI/render layer.
2022-07-27 05:39:53 +03:00
"wezterm-dynamic",
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
]
config: derive some metadata about the config This isn't used by anything yet, but will enable some runtime config editing functions that I have planeed for the future.
2022-09-22 03:42:43 +03:00
[[package]]
name = "wezterm-config-derive"
version = "0.1.0"
dependencies = [
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
config: derive some metadata about the config This isn't used by anything yet, but will enable some runtime config editing functions that I have planeed for the future.
2022-09-22 03:42:43 +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",
deps: structopt -> clap 3
2022-05-28 17:07:52 +03:00
"strsim",
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
add wezterm-dynamic crate
2022-05-11 18:19:00 +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-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",
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
"finl_unicode",
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",
lfucache: improve LFU algorithm and structure Do it "more properly": use intrusive list linkage to manage three indices: * hash lookup * recency * frequency eviction is frequency based, but in order to avoid things that were super hot in the past and that are no longer hot clogging up the cache, eviction will incrementally age out least recently used entries that haven't been active in the span of some number of get/put operations. Aging scales down the frequency value to reduce its strength, so an aged item isn't necessarily immediately a candidate for removal, it just makes it more likely to be picked up by the frequency based removal as it goes unused for an extended period.
2022-11-14 17:34:38 +03:00
"lfucache",
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",
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",
"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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"bytemuck",
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",
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
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",
Add support for heap profiling using dhat refs: https://github.com/wez/wezterm/issues/2626
2022-11-14 23:26:02 +03:00
"dhat",
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",
Add CharSelect modal for emoji/nerdfont/unicode input CTRL-SHIFT-U is a new default key assignment for this new modal. It opens up a fuzzy searchable browser that defaults to showing emoji/emoticons. The category can by cycled through the suggested emoji categories using CTRL-r. Unlike the system emoji palette, wezterm includes a category for nerdfont symbols, and another that is a list of all unicode codepoint names, so you should be able to browse for pretty much any codepoint you can think of. The modal also allows fuzzy searching based on: * The official unicode name * The github shortcode * codepoint value in hex so if you know the codepoint value but not the name, you can still find a way to input what you're looking for. Pressing Enter will copy the selected item to the clipboard send it to the active pane, and cancel the modal. You can therefore repeat the insert by simply pasting. I plan to add frecency to this in a later commit: that way the frequently/recently used selections will show in a category of their own and make it easier to re-input them. refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 04:15:28 +03:00
"emojis",
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",
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
"finl_unicode",
char selector: track recently selected emoji and use frecency to show it refs: https://github.com/wez/wezterm/issues/2163
2022-09-01 08:56:58 +03:00
"frecency",
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
"futures",
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",
refactor: move lfucache into its own crate
2022-11-14 06:20:15 +03:00
"lfucache",
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",
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",
lua: add window:mux_window() and pane:mux_window() methods These allow converting the gui versions of these objects to the mux versions. refs: https://github.com/wez/wezterm/issues/225
2022-06-28 06:28:26 +03:00
"mux-lua",
use blob leases for decoded animation frames This allows the decoder thread to live only long enough to decode the full set of frames; we can then store the leases in memory and pull them in only when there is a cache miss. refs: https://github.com/wez/wezterm/issues/3263
2023-03-19 07:52:53 +03:00
"once_cell",
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",
mux: Pane is now required to be Send+Sync. Use Arc<dyn Pane>
2022-11-23 19:05:30 +03:00
"parking_lot 0.12.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
"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",
macos: use interactive shell for .command scripts This is primarily so that the user's environment is set up prior to invoking the script. refs: #2871
2022-12-20 18:30:07 +03:00
"shlex",
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
"tabout",
Image decoding is now done in a bg thread Continuing from the previous commit, this shifts: * In-memory data -> temporary file * Image decoding -> background thread The background thread asynchronously decodes frames and sends them to the render thread via a bounded channel. While decoding frames, it writes them, uncompressed, to a scratch file so that when the animation loops, it is a very cheap operation to rewind and pull that data from the file, without having to burn CPU to re-decode the data from the start. Memory usage is bounded to 4 uncompressed frames while decoding, then 3 uncompressed frames (triple buffered) while looping over the rest. However, disk usage is N uncompressed frames. refs: https://github.com/wez/wezterm/issues/3263
2023-03-17 21:11:46 +03:00
"tempfile",
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.16 closes: https://github.com/wez/wezterm/pull/2664
2022-10-24 06:50:47 +03:00
"textwrap 0.16.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",
ImageDataType::File -> EncodedLease Adopt the new blob lease layer to storing and referencing image files. This reduces the number of open files needed when images are being displayed in the terminal. refs: https://github.com/wez/wezterm/issues/3263
2023-03-19 06:32:49 +03:00
"wezterm-blob-leases",
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",
add own open_url crate The upstream open crate keeps making stuff async/blocking/not-working on windows, so this is a step towards removing this dependency. refs: https://github.com/wez/wezterm/issues/3288
2023-03-19 22:44:12 +03:00
"wezterm-open-url",
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",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"wgpu",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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",
lua: add wezterm.window.screens() Currently implemented on X11 only, this function returns information about the geometry of the screen(s). This is taken from the same source of information we use for the `--position` CLI argument to `wezterm start`. ``` > wezterm.window.screens() { "by_name": { "DisplayPort-1": { "height": 2160, "name": "DisplayPort-1", "width": 3840, "x": 0, "y": 0, }, }, "main": { "height": 2160, "name": "DisplayPort-1", "width": 3840, "x": 0, "y": 0, }, "origin_x": 0, "origin_y": 0, "virtual_height": 2160, "virtual_width": 3840, } ```
2022-07-06 18:32:13 +03:00
"window-funcs",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"windows 0.33.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
]
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",
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
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",
]
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
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",
add gui-startup and mux-startup events Using the newly exposed-to-lua mux apis, you may now run some lua code at GUI startup and/or mux startup, just prior to any default windows being created. If you happen to spawn any panes as a result of this, wezterm will skip creating the default program. ```lua local wezterm = require 'wezterm' local mux = wezterm.mux -- This produces a window split horizontally into three equal parts wezterm.on("gui-startup", function() wezterm.log_info("doing gui startup") local tab, pane, window = mux.spawn_window{} mux.split_pane(pane, {size=0.3}) mux.split_pane(pane, {size=0.5}) end) wezterm.on("mux-startup", function() wezterm.log_info("doing mux startup") local tab, pane, window = mux.spawn_window{} mux.split_pane(pane, {size=0.5, direction="Top"}) end) return { unix_domains = { {name="unix"} }, } ``` refs: #674 refs: #1949
2022-06-17 22:37:19 +03:00
"mlua",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"mux",
"openssl",
"portable-pty",
"promise",
"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",
track dpi in mux and terminal model refs: https://github.com/wez/wezterm/issues/2085
2022-06-16 04:54:51 +03:00
"wezterm-term",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
]
add own open_url crate The upstream open crate keeps making stuff async/blocking/not-working on windows, so this is a step towards removing this dependency. refs: https://github.com/wez/wezterm/issues/3288
2023-03-19 22:44:12 +03:00
[[package]]
name = "wezterm-open-url"
version = "0.1.0"
dependencies = [
"winapi",
]
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",
update base64, work around another batch of breaking API changes closes: https://github.com/wez/wezterm/pull/2931
2023-01-09 04:49:45 +03:00
"base64 0.21.0",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Switch to camino::{Utf8PathBuf, Utf8Path}
2021-10-04 04:36:30 +03:00
"camino",
cargo update
2023-03-20 06:20:34 +03:00
"clap 4.1.11",
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",
ssh: support %l and %L in config files We also log a warning when an unsupported token is used. refs: https://github.com/wez/wezterm/issues/3176
2023-03-02 04:44:11 +03:00
"gethostname",
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",
cargo update
2023-03-17 22:02:21 +03:00
"predicates 2.1.5",
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",
deps: socket2 -> 0.5
2023-02-27 08:33:28 +03:00
"socket2 0.5.1",
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",
"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",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
Switch to finl_unicode for grapheme clustering According to its benchmarks, it's almost 2x faster than unicode_segmentation. It doesn't appear to make a visible difference to `time cat bigfile`, but I'll take anything that gives more headroom for such little effort of switching.
2022-09-10 02:38:47 +03:00
"finl_unicode",
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",
term: improve readability of error message for oversized image refs: https://github.com/wez/wezterm/issues/3264
2023-03-17 08:41:52 +03:00
"humansize",
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
"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 = [
deps: remove async-std dep We were only using block_on from it, which we can call from the underlying async_io crate. Notably, removing async_std from the deps avoids async-global-executor being pulled in and spawning nproc threads that are never used by wezterm.
2022-11-01 17:05:33 +03:00
"async-io",
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",
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",
add own open_url crate The upstream open crate keeps making stuff async/blocking/not-working on windows, so this is a step towards removing this dependency. refs: https://github.com/wez/wezterm/issues/3288
2023-03-19 22:44:12 +03:00
"wezterm-open-url",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"windows 0.33.0",
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
]
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
[[package]]
name = "wgpu"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.15.1"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "d745a1b6d91d85c33defbb29f0eee0450e1d2614d987e14bf6baf26009d132d7"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"arrayvec",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"cfg-if",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"js-sys",
"log",
"naga",
"parking_lot 0.12.1",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"profiling",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"raw-window-handle",
"smallvec",
"static_assertions",
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
"wgpu-core",
"wgpu-hal",
"wgpu-types",
]
[[package]]
name = "wgpu-core"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.15.1"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "7131408d940e335792645a98f03639573b0480e9e2e7cddbbab74f7c6d9f3fff"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"arrayvec",
"bit-vec",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"codespan-reporting",
"fxhash",
"log",
"naga",
"parking_lot 0.12.1",
"profiling",
"raw-window-handle",
"smallvec",
"thiserror",
"web-sys",
"wgpu-hal",
"wgpu-types",
]
[[package]]
name = "wgpu-hal"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.15.3"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "7762ae7fcc06943c1b5d4987ab0194e82aaba7767fbfb75d3458844c5b82cc45"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
"android_system_properties",
"arrayvec",
"ash",
"bit-set",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"block",
"core-graphics-types",
"d3d12",
"foreign-types",
"fxhash",
"glow",
"gpu-alloc",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"gpu-allocator",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"gpu-descriptor",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"hassle-rs",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"js-sys",
"khronos-egl",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"libc",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
"libloading 0.7.4",
"log",
"metal",
"naga",
"objc",
"parking_lot 0.12.1",
"profiling",
"range-alloc",
"raw-window-handle",
"renderdoc-sys",
"smallvec",
"thiserror",
"wasm-bindgen",
"web-sys",
"wgpu-types",
"winapi",
]
[[package]]
name = "wgpu-types"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.15.2"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "32444e121b0bd00cb02c0de32fde457a9491bd44e03e7a5db6df9b1da2f6f110"
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +03:00
dependencies = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"js-sys",
"web-sys",
Basic useless wgpu based rendering foundation
2022-11-16 04:19:48 +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
2023-03-13 06:22:05 +03:00
version = "1.4.0"
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
2023-03-13 06:22:05 +03:00
checksum = "2c70234412ca409cc04e864e89523cb0fc37f5e1344ebed5a3ebf4192b6b9f68"
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",
]
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
[[package]]
name = "widestring"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "17882f045410753661207383517a6f62ec3dbeb6a4ed2acce01f0728238d1983"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-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 = [
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
erase generic T from Atlas, Sprite, CachedGlyph etc. This will make it easier to use the same impl for webgpu and opengl for a bunch of this stuff.
2022-11-16 17:40:56 +03:00
"downcast-rs",
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: use a shorter timeout for xdg portal reads A user reported this: 08:47:13.372 DEBUG window::os::x11::connection > Unable to resolve appearance using xdg-desktop-portal: Read: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.portal.Desktop': timed out (service_start_timeout=120000ms) which is an issue with their xdg-portal service. Rather than have wezterm block for 2 minutes on startup, we give it 1 second, and log the issue as a warning.
2023-02-08 18:26:20 +03:00
"futures-lite",
x11/wayland: use xdg desktop portal settings interface to get dark mode There are some other settings in there that could also help with things like the cursor theme on Wayland. Note that we don't currently subscribe to the settings changed signal: that can be done in a follow up. refs: https://github.com/wez/wezterm/issues/2258 refs: https://github.com/wez/wezterm/issues/1742
2022-07-13 18:54:24 +03:00
"futures-util",
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"mio",
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",
macos: add version info to system name
2023-01-11 04:58:35 +03:00
"plist",
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
"promise",
deps: update raw-window-handle
2022-10-28 06:38:02 +03:00
"raw-window-handle",
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",
support drag and drop files for wayland
2022-06-20 14:41:25 +03:00
"url",
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",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
"windows 0.33.0",
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",
x11/wayland: use xdg desktop portal settings interface to get dark mode There are some other settings in there that could also help with things like the cursor theme on Wayland. Note that we don't currently subscribe to the settings changed signal: that can be done in a follow up. refs: https://github.com/wez/wezterm/issues/2258 refs: https://github.com/wez/wezterm/issues/1742
2022-07-13 18:54:24 +03:00
"zbus",
"zvariant",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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.window.screens() Currently implemented on X11 only, this function returns information about the geometry of the screen(s). This is taken from the same source of information we use for the `--position` CLI argument to `wezterm start`. ``` > wezterm.window.screens() { "by_name": { "DisplayPort-1": { "height": 2160, "name": "DisplayPort-1", "width": 3840, "x": 0, "y": 0, }, }, "main": { "height": 2160, "name": "DisplayPort-1", "width": 3840, "x": 0, "y": 0, }, "origin_x": 0, "origin_y": 0, "virtual_height": 2160, "virtual_width": 3840, } ```
2022-07-06 18:32:13 +03:00
[[package]]
name = "window-funcs"
version = "0.1.0"
dependencies = [
"anyhow",
"config",
"luahelper",
"wezterm-dynamic",
"window",
]
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",
]
ssh: support %l and %L in config files We also log a warning when an unsupported token is used. refs: https://github.com/wez/wezterm/issues/3176
2023-03-02 04:44:11 +03:00
[[package]]
name = "windows"
version = "0.43.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "04662ed0e3e5630dfa9b26e4cb823b817f1a9addda855d973a9458c236556244"
dependencies = [
"windows_aarch64_gnullvm",
cargo update
2023-03-17 22:02:21 +03:00
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
ssh: support %l and %L in config files We also log a warning when an unsupported token is used. refs: https://github.com/wez/wezterm/issues/3176
2023-03-02 04:44:11 +03:00
"windows_x86_64_gnullvm",
cargo update
2023-03-17 22:02:21 +03:00
"windows_x86_64_msvc 0.42.2",
ssh: support %l and %L in config files We also log a warning when an unsupported token is used. refs: https://github.com/wez/wezterm/issues/3176
2023-03-02 04:44:11 +03:00
]
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
[[package]]
name = "windows"
cargo update
2023-02-17 21:30:15 +03:00
version = "0.44.0"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-02-17 21:30:15 +03:00
checksum = "9e745dab35a0c4c77aa3ce42d595e13d2003d6902d6b08c9ef5fc326d08da12b"
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
dependencies = [
cargo update
2023-02-17 21:30:15 +03:00
"windows-targets",
deps: wgpu -> 0.15 This might help with https://github.com/wez/wezterm/issues/3032
2023-02-06 17:19:31 +03:00
]
cargo update
2022-10-23 22:08:11 +03:00
[[package]]
name = "windows-sys"
version = "0.42.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5a3e1820f08b8513f676f7ab6c1f99ff312fb97b553d30ff4dd86f9f15728aa7"
dependencies = [
"windows_aarch64_gnullvm",
cargo update
2023-03-17 22:02:21 +03:00
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
cargo update
2022-10-23 22:08:11 +03:00
"windows_x86_64_gnullvm",
cargo update
2023-03-17 22:02:21 +03:00
"windows_x86_64_msvc 0.42.2",
cargo update
2022-10-23 22:08:11 +03:00
]
cargo update
2023-02-06 07:53:11 +03:00
[[package]]
name = "windows-sys"
version = "0.45.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "75283be5efb2831d37ea142365f009c02ec203cd29a3ebecbc093d52315b66d0"
dependencies = [
"windows-targets",
]
[[package]]
name = "windows-targets"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
cargo update
2023-02-06 07:53:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "8e5180c00cd44c9b1c88adb3693291f1cd93605ded80c250a75d472756b4d071"
cargo update
2023-02-06 07:53:11 +03:00
dependencies = [
"windows_aarch64_gnullvm",
cargo update
2023-03-17 22:02:21 +03:00
"windows_aarch64_msvc 0.42.2",
"windows_i686_gnu 0.42.2",
"windows_i686_msvc 0.42.2",
"windows_x86_64_gnu 0.42.2",
cargo update
2023-02-06 07:53:11 +03:00
"windows_x86_64_gnullvm",
cargo update
2023-03-17 22:02:21 +03:00
"windows_x86_64_msvc 0.42.2",
cargo update
2023-02-06 07:53:11 +03:00
]
cargo update
2022-10-23 22:08:11 +03:00
[[package]]
name = "windows_aarch64_gnullvm"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
cargo update
2022-10-23 22:08:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "597a5118570b68bc08d8d59125332c54f1ba9d9adeedeef5b99b02ba2b0698f8"
cargo update
2022-10-23 22:08:11 +03:00
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"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
cargo update
2022-10-23 22:08:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "e08e8864a60f06ef0d0ff4ba04124db8b0fb3be5776a5cd47641e942e58c4d43"
cargo update
2022-10-23 22:08:11 +03:00
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"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "c61d927d8da41da96a81f029489353e68739737d3beca43145c8afec9a31a84f"
cargo update
2022-10-23 22:08:11 +03:00
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"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
cargo update
2022-10-23 22:08:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "44d840b6ec649f480a41c8d80f9c65108b92d89345dd94027bfe06ac444d1060"
cargo update
2022-10-23 22:08:11 +03:00
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"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "8de912b8b8feb55c064867cf047dda097f92d51efad5b491dfb98f6bbb70cb36"
cargo update
2022-10-23 22:08:11 +03:00
[[package]]
name = "windows_x86_64_gnullvm"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
cargo update
2022-10-23 22:08:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "26d41b46a36d453748aedef1486d5c7a85db22e56aff34643984ea85514e94a3"
cargo update
2022-10-23 22:08:11 +03:00
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"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.42.2"
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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "9aec5da331524158c6d1a4ac0ab1541149c0b9505fde06423b02f5ef0106b9f0"
cargo update
2022-10-23 22:08:11 +03:00
cargo update
2023-02-27 08:32:52 +03:00
[[package]]
name = "winnow"
cargo update
2023-03-17 22:02:21 +03:00
version = "0.3.6"
cargo update
2023-02-27 08:32:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-17 22:02:21 +03:00
checksum = "23d020b441f92996c80d94ae9166e8501e59c7bb56121189dc9eab3bd8216966"
cargo update
2023-02-27 08:32:52 +03:00
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]]
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 = [
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = [
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2023-01-21 06:04:49 +03:00
version = "2.21.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
2023-01-21 06:04:49 +03:00
checksum = "502da5464ccd04011667b11c435cb992822c2c0dbde1770c988480d312a0db2e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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]]
color schemes: import all official base16 schemes
2022-07-12 21:51:19 +03:00
name = "xattr"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d1526bbe5aaeb5eb06885f4d987bcdfa5e23187055de9b83fe00156a821fabc"
dependencies = [
"libc",
]
[[package]]
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
name = "xcb"
x11: potential fix for hanging IME refs: https://github.com/H-M-H/xcb-imdkit-rs/issues/5 refs: https://github.com/wez/wezterm/issues/2819
2022-12-19 22:23:04 +03:00
version = "1.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0faeb4d7e2d54fff4a0584f61297e86b106914af2029778de7b427f72564d6c5"
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
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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",
cargo update
2023-01-21 06:04:49 +03:00
"quick-xml 0.22.0",
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"
x11: potential fix for hanging IME refs: https://github.com/H-M-H/xcb-imdkit-rs/issues/5 refs: https://github.com/wez/wezterm/issues/2819
2022-12-19 22:23:04 +03:00
source = "git+https://github.com/wez/xcb-imdkit-rs.git?branch=hangfix#c6859ab2b8a233ca5dda5e8e4f1634d34ce9c85c"
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 = [
cargo update
2023-03-20 06:20:34 +03:00
"bitflags 1.3.2",
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
"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 = [
cargo update
2023-01-16 07:48:20 +03:00
"nom 7.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
]
[[package]]
name = "xkbcommon"
deps: xkbcommon-rs released 0.5 can stop using my git repo for this
2022-09-02 00:33:02 +03:00
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "acbee136714379ab22da0280207fdb7f47e0bb940adea97731b65598b8c7a92e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-27 08:32:52 +03:00
"memmap2 0.5.10",
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
sync-color-schemes: refactor caching and fetching
2022-07-12 20:08:49 +03:00
[[package]]
name = "yaml-rust"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56c1936c4cc7a1c9ab21a1ebb602eb942ba868cbd44a99cb7cdc5892335e1c85"
dependencies = [
"linked-hash-map",
]
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"
cargo update
2022-12-19 21:13:02 +03:00
version = "0.5.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
2022-12-19 21:13:02 +03:00
checksum = "aed2e7a52e3744ab4d0c05c20aa065258e84c49fd4226f5191b2ed29712710b4"
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
2023-02-27 08:32:52 +03:00
"time 0.3.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
]
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
2023-03-20 06:20:34 +03:00
version = "3.11.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "3dc29e76f558b2cb94190e8605ecfe77dd40f5df8c072951714b4b71a97f5848"
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-executor",
cargo update
2023-03-13 06:22:05 +03:00
"async-fs",
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",
cargo update
2023-01-16 07:48:20 +03:00
"dirs",
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
"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",
cargo update
2023-03-13 06:22:05 +03:00
"nix 0.26.2",
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
2023-01-16 07:48:20 +03:00
"rand",
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",
cargo update
2022-11-07 04:51:07 +03:00
"sha1",
Enable toast notifications on freebsd refs: https://github.com/wez/wezterm/issues/489
2021-05-30 21:51:57 +03:00
"static_assertions",
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
"tracing",
cargo update
2022-05-02 07:21:14 +03:00
"uds_windows",
deps: notify -> 5.0.0-pre.15 This allows moving past a number of outdated deps, but importantly, allows updating miow to a version that has the correct memory layout for SocketAddr, and satisfies a dependabot alert.
2022-06-08 09:34:58 +03:00
"winapi",
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
2023-03-20 06:20:34 +03:00
version = "3.11.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-20 06:20:34 +03:00
checksum = "62a80fd82c011cd08459eaaf1fd83d3090c1b61e6d5284360074a7475af3a85d"
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",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
cargo update
2023-03-13 06:22:05 +03:00
"zvariant_utils",
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
2023-01-08 17:46:31 +03:00
version = "2.5.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
2023-01-08 17:46:31 +03:00
checksum = "f34f314916bd89bdb9934154627fab152f4f28acdda03e7c4c68181b214fe7e3"
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"
deps: zstd 0.6 -> 0.11
2022-07-26 07:29:43 +03:00
version = "0.11.2+zstd.1.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"
deps: zstd 0.6 -> 0.11
2022-07-26 07:29:43 +03:00
checksum = "20cc960326ece64f010d2d2107537f26dc589a6573a316bd5b1dba685fa5fde4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
deps: zstd 0.6 -> 0.11
2022-07-26 07:29:43 +03:00
version = "5.0.2+zstd.1.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"
deps: zstd 0.6 -> 0.11
2022-07-26 07:29:43 +03:00
checksum = "1d2a5585e04f9eea4b2a3d1eca508c4dee9592a89ef6f450c11719da0726f4db"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2023-02-17 21:30:15 +03:00
version = "2.0.7+zstd.1.5.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
2023-02-17 21:30:15 +03:00
checksum = "94509c3ba2fe55294d752b79842c530ccfab760192521df74a081a78d2b3c7f5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
cargo update
2023-01-16 07:48:20 +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
]
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
cargo update
2023-02-06 07:53:11 +03:00
[[package]]
name = "zune-inflate"
cargo update
2023-03-13 06:22:05 +03:00
version = "0.2.51"
cargo update
2023-02-06 07:53:11 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2023-03-13 06:22:05 +03:00
checksum = "a01728b79fb9b7e28a8c11f715e1cd8dc2cda7416a007d66cac55cebb3a8ac6b"
cargo update
2023-02-06 07:53:11 +03:00
dependencies = [
"simd-adler32",
]
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
[[package]]
name = "zvariant"
cargo update
2023-03-13 06:22:05 +03:00
version = "3.12.0"
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
2023-03-13 06:22:05 +03:00
checksum = "46fe4914a985446d6fd287019b5fceccce38303d71407d9e6e711d44954a05d8"
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
2023-03-13 06:22:05 +03:00
version = "3.12.0"
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
2023-03-13 06:22:05 +03:00
checksum = "34c20260af4b28b3275d6676c7e2a6be0d4332e8e0aba4616d34007fd84e462a"
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
dependencies = [
"proc-macro-crate",
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
cargo update
2023-03-13 06:22:05 +03:00
"zvariant_utils",
]
[[package]]
name = "zvariant_utils"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "53b22993dbc4d128a17a3b6c92f1c63872dd67198537ee728d8b5d7c40640a8b"
dependencies = [
"proc-macro2",
"quote",
cargo update
2023-03-20 06:20:34 +03:00
"syn 1.0.109",
deps: update pulldown_cmark, cargo update
2021-12-27 19:49:22 +03:00
]
Reference in New Issue Copy Permalink