wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-11-27 12:23:46 +03:00
Code Issues Projects Releases Wiki Activity
1cbaf55640
wezterm/Cargo.lock

5446 lines
125 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
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
[[package]]
name = "ab_glyph_rasterizer"
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.1.4"
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "d9fe5e32de01730eb1f6b7f5b51c17e03e2325bf40a74f754f04f130043affff"
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
cargo update
2020-05-26 08:25:39 +03:00
[[package]]
name = "addr2line"
cargo update
2021-01-06 11:28:11 +03:00
version = "0.14.1"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-06 11:28:11 +03:00
checksum = "a55f82cfe485775d02112886f4169bde0c5894d75e79ead7eafe7e40a25e45f7"
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
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 = "ahash"
deps: cargo update
2020-12-11 10:50:10 +03:00
version = "0.4.7"
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"
deps: cargo update
2020-12-11 10:50:10 +03:00
checksum = "739f4a8db6605981345c5654f3a85b056ce52f37a39d34da03f25bf2151ea16e"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "aho-corasick"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.7.18"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "1e37cfd5e7657ada45f742d6e99ca5788580b5c529dc78faf11ece6dc702656f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"memchr",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "alloc-no-stdlib"
version = "2.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "5192ec435945d87bc2f70992b4d818154b5feede43c09fb7592146374eac90a6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "alloc-stdlib"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "697ed7edc0f1711de49ce108c541623a0af97c6c60b2f6e2b65229847ac843c2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"alloc-no-stdlib",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "allsorts"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
version = "0.4.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 = "git+https://github.com/yeslogic/allsorts.git?rev=3947164a201ab5e15d5f23204faaaaaad52531aa#3947164a201ab5e15d5f23204faaaaaad52531aa"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wezterm: 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
"bitreader",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"brotli-decompressor",
"byteorder",
"encoding_rs",
"flate2",
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
"glyph-names",
cargo update
2021-03-08 10:18:21 +03:00
"itertools",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 0.2.14",
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
"rental",
"rustc-hash",
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",
wezterm: fixup some allsorts shaping cases * Fixes `keycap 0` by plucking out the prior character for an EnclosingMark * Fixes lookahead for VariationSelector refs: #66
2020-11-21 05:44:28 +03:00
"unicode-general-category 0.1.0",
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
"unicode-joining-type",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "andrew"
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.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "8c4afb09dd642feec8408e33f92f3ffc4052946f6b20f32fb99c1f58cd4fa7cf"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
"rusttype",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
"xdg",
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 = "ansi_term"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "ee49baf6cb617b853aa8d93bf420db2383fab46d314482ca2803b40d5fde979b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "anyhow"
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
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"
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
checksum = "28b2cd92db5cbd74e8e5028f7e27dd7aa3090e89e4f2a197cc7c8dfb69c7063b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "approx"
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 = "f0e60b75072ecd4168020818c0107f2857bb6c4e64252d8d3983f6263b40a5c3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"num-traits 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
]
[[package]]
name = "arrayvec"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.5.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "23b62fc65de8e4e7f52534fb52b0f3ed04746ae267519eef2a83941e8085068b"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "ash"
version = "0.32.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "06063a002a77d2734631db74e8f4ce7148b77fe522e6bca46f2ae7774fd48112"
dependencies = [
"libloading 0.7.0",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "async-channel"
cargo update
2021-02-22 11:09:01 +03:00
version = "1.6.1"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-22 11:09:01 +03:00
checksum = "2114d64672151c0c5eaa5e131ec84a74f06e1e559830dabba01ca30605d66319"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"concurrent-queue",
"event-listener",
"futures-core",
]
[[package]]
name = "async-executor"
cargo update
2021-04-26 18:34:45 +03:00
version = "1.4.1"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "871f9bb5e0a22eeb7e8cf16641feb87c9dc67032ccf8ff49e772eb9941d3a965"
cargo update
2020-10-02 17:16:20 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
cargo update
2020-10-02 17:16:20 +03:00
"concurrent-queue",
"fastrand",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-10-02 17:16:20 +03:00
"once_cell",
cargo update
2021-04-26 18:34:45 +03:00
"slab",
cargo update
2020-10-02 17:16:20 +03:00
]
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
[[package]]
name = "async-fs"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.5.0"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "8b3ca4f8ff117c37c278a2f7415ce9be55560b846b5bc4412aaa5d29c1c3dae2"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"async-lock",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"blocking",
"futures-lite",
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "async-global-executor"
cargo update
2021-01-18 10:38:11 +03:00
version = "2.0.2"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-18 10:38:11 +03:00
checksum = "9586ec52317f36de58453159d48351bc244bc24ced3effc1fce22f3d48664af6"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
cargo update
2021-01-18 10:38:11 +03:00
"async-channel",
cargo update
2020-10-02 17:16:20 +03:00
"async-executor",
cargo update
2020-09-09 19:31:37 +03:00
"async-io",
cargo update
2021-01-18 10:38:11 +03:00
"async-mutex",
"blocking",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-10-02 17:16:20 +03:00
"num_cpus",
"once_cell",
cargo update
2020-09-09 19:31:37 +03:00
]
[[package]]
name = "async-io"
cargo update
2021-04-26 18:34:45 +03:00
version = "1.4.1"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "4bbfd5cf2794b1e908ea8457e6c45f8f8f1f6ec5f74617bf4662623f47503c3b"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"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",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"libc",
cargo update
2020-10-02 17:16:20 +03:00
"log",
cargo update
2020-09-09 19:31:37 +03:00
"once_cell",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"parking",
cargo update
2020-09-09 19:31:37 +03:00
"polling",
cargo update
2021-04-26 18:34:45 +03:00
"slab",
cargo update
2021-04-19 19:23:33 +03:00
"socket2",
cargo update
2020-10-02 17:16:20 +03:00
"waker-fn",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"winapi 0.3.9",
cargo update
2020-09-09 19:31:37 +03:00
]
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
[[package]]
name = "async-lock"
cargo update
2021-04-19 19:23:33 +03:00
version = "2.4.0"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "e6a8ea61bf9947a1007c5cada31e647dbc77b103c679858150003ba697ea798b"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"event-listener",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "async-mutex"
cargo update
2020-10-02 17:16:20 +03:00
version = "1.4.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-10-02 17:16:20 +03:00
checksum = "479db852db25d9dbf6204e6cb6253698f175c15726470f78af0d918e99d6156e"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"event-listener",
]
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
[[package]]
name = "async-net"
cargo update
2021-04-26 18:34:45 +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
2021-04-26 18:34:45 +03:00
checksum = "69b0a74e7f70af3c8cf1aa539edbd044795706659ac52b78a71dc1a205ecefdf"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
"async-io",
"blocking",
"fastrand",
"futures-lite",
]
[[package]]
name = "async-process"
cargo update
2021-04-26 18:34:45 +03:00
version = "1.1.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
2021-04-26 18:34:45 +03:00
checksum = "a8f38756dd9ac84671c428afbf7c9f7495feff9ec5b0710f17100098e5b354ac"
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
dependencies = [
"async-io",
"blocking",
cargo update
2021-02-08 09:51:28 +03:00
"cfg-if 1.0.0",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"event-listener",
"futures-lite",
cargo update
2021-04-26 18:34:45 +03:00
"libc",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"once_cell",
cargo update
2021-04-05 18:46:55 +03:00
"signal-hook 0.3.8",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"winapi 0.3.9",
]
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "async-std"
cargo update
2021-01-18 10:38:11 +03:00
version = "1.9.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
2021-01-18 10:38:11 +03:00
checksum = "d9f06685bad74e0570f5213741bea82158279a4103d988e57bfada11ad230341"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
dependencies = [
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
"async-channel",
cargo update
2020-10-02 17:16:20 +03:00
"async-global-executor",
cargo update
2020-09-09 19:31:37 +03:00
"async-io",
cargo update
2021-01-18 10:38:11 +03:00
"async-lock",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
cargo update
2020-05-26 08:25:39 +03:00
"futures-channel",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"futures-core",
"futures-io",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-10-02 17:16:20 +03:00
"gloo-timers",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"kv-log-macro",
"log",
"memchr",
"num_cpus",
"once_cell",
cargo update
2020-12-20 03:44:27 +03:00
"pin-project-lite",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"pin-utils",
"slab",
cargo update
2020-05-26 08:25:39 +03:00
"wasm-bindgen-futures",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "async-task"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "4.0.3"
cargo update
2020-10-02 17:16:20 +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 = "e91831deabf0d6d7ec49552e489aed63b7456a7a3c46cff62adad428110b0af0"
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
2021-04-19 19:23:33 +03:00
version = "0.1.50"
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
2021-04-19 19:23:33 +03:00
checksum = "0b98e84bbb4cbcdd97da190ba0c58a1bb0de2c1fdf67d159e192ed766aeca722"
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
]
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
[[package]]
name = "async_ossl"
version = "0.1.0"
dependencies = [
"openssl",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "atomic-waker"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "065374052e7df7ee4047b1160cca5e1467a12351a40b3da123c870ba0b8eda2a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "atty"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.2.14"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d9b39be18770d11421cdb1b9947a45dd3f37e93092cbf377614828a319d5fee8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hermit-abi",
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
bump some versions
2020-01-10 09:39:34 +03:00
[[package]]
name = "autocfg"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.0.1"
bump some versions
2020-01-10 09:39:34 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "cdb031dd78e28731d87d56cc8ffef4a8f36ca26c38fe2de700543e627f8a464a"
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
2021-05-01 19:42:46 +03:00
version = "0.3.58"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "88fb5a785d6b44fd9d6700935608639af1b8356de1e55d5f7c2740f4faa15d82"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-05-26 08:25:39 +03:00
"addr2line",
cargo update
2021-05-01 19:42:46 +03:00
"cc",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2021-03-01 20:02:05 +03:00
"miniz_oxide 0.4.4",
cargo update
2020-05-26 08:25:39 +03:00
"object",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rustc-demangle",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
[[package]]
name = "base64"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.13.0"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "904dfeac50f3cdaba28fc6f57fdcddb75f49ed61346676a78c4ffe55877802fd"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "base91"
version = "0.1.0"
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 = "battery"
version = "0.7.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b4b624268937c0e0a3edb7c27843f9e547c320d730c610d3b8e6e8e95b2026e4"
dependencies = [
"cfg-if 1.0.0",
"core-foundation 0.7.0",
"lazycell",
"libc",
"mach",
"nix 0.19.1",
"num-traits 0.2.14",
"uom",
"winapi 0.3.9",
]
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"
version = "0.4.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ea52a394d9a85bf9819ca50382187ece2497501dbd6397fd33388400e512a90e"
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"
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "bit-set"
version = "0.5.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6e11e16035ea35e4e5997b393eacbf6f63983188f7a2ad25bfb13465f5ad59de"
dependencies = [
"bit-vec",
]
[[package]]
name = "bit-vec"
version = "0.6.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "349f9b6a179ed607305526ca489b34ad0a41aed5f7980fa90eb03160b69598fb"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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"
version = "1.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "cf1de2fe8c75bc145a2f577add951f8134889b4795d47466a54a5c846d691693"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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: 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 = "bitreader"
cargo update
2021-01-26 07:51:25 +03:00
version = "0.3.3"
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
2021-01-26 07:51:25 +03:00
checksum = "70a57a98015fc89125fae6054685a2586739fba82c8dbfe550dac9a5a76791a6"
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 = [
cargo update
2021-01-26 07:51:25 +03:00
"cfg-if 1.0.0",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
]
[[package]]
name = "bitvec"
cargo update
2021-03-08 10:18:21 +03:00
version = "0.19.5"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "8942c8d352ae1838c9dda0b0ca2ab657696ef2232a20147cf1b30ae1a9cb4321"
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 = [
"funty",
"radium",
"tap",
"wyz",
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
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "block"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "0d8c1fef690941d3e7788d328517591fecc684c084084702d6ff1641e993699a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "block-buffer"
version = "0.7.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c0940dc441f31689269e10ac70eb1002a3a1d3ad1390e030043662eb7fe4688b"
dependencies = [
"block-padding",
"byte-tools",
"byteorder",
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
"generic-array 0.12.4",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "block-buffer"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4152116fd6e9dadb291ae18fc1ec3575ed6d84c29642d97890f4b4a3417297e4"
dependencies = [
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
"generic-array 0.14.4",
]
[[package]]
name = "block-padding"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa79dedbb091f449f1f39e53edf88d5dbe95f895dae6135a8d7b881fb5af73f5"
dependencies = [
"byte-tools",
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "blocking"
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.0.2"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "c5e170dbede1f740736619b776d7251cb1b9095c435c34d8ca9f57fcd2f335e9"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
"async-channel",
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
cargo update
2020-09-09 19:31:37 +03:00
"atomic-waker",
cargo update
2020-10-02 17:16:20 +03:00
"fastrand",
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"futures-lite",
cargo update
2020-06-30 03:52:14 +03:00
"once_cell",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "brotli-decompressor"
cargo update
2020-06-06 20:08:02 +03:00
version = "2.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"
cargo update
2020-06-06 20:08:02 +03:00
checksum = "1052e1c3b8d4d80eb84a8b94f0a1498797b5fb96314c001156a1c761940ef4ec"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"alloc-no-stdlib",
"alloc-stdlib",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "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"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.2.16"
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
2021-05-01 19:42:46 +03:00
checksum = "90682c8d613ad3373e66de8c6411e0ae2ab2571e879d2efbf73558cc66f21279"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
dependencies = [
lua: add serde-powered to_lua_value function This will help in implementing lua helper functions for various config and other structures.
2020-03-01 08:46:59 +03:00
"lazy_static",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
"memchr",
lua: add serde-powered to_lua_value function This will help in implementing lua helper functions for various config and other structures.
2020-03-01 08:46:59 +03:00
"regex-automata",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "bumpalo"
cargo update
2021-02-22 11:09:01 +03:00
version = "3.6.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
2021-02-22 11:09:01 +03:00
checksum = "63396b8a4b9de3f4fdfb320ab6080762242f66a8ef174c49d8e19b674db4cdbe"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "byte-tools"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e3b5ca7a04898ad4bcd41c90c5285445ff5b791899bb1b0abdd2a2aa791211d7"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "bytemuck"
cargo update
2021-02-22 11:09:01 +03:00
version = "1.5.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
2021-02-22 11:09:01 +03:00
checksum = "bed57e2090563b83ba8f83366628ce535a7584c9afa4c9fc0612a03925c6df58"
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
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "cache-padded"
cargo update
2020-07-09 09:54:56 +03:00
version = "1.1.1"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-07-09 09:54:56 +03:00
checksum = "631ae5198c9be5e753e5cc215e1bd73c2b466a3565173db433f52bb9d3e66dba"
promise: add tokio_spawn helper This starts up the tokio runtime on a secondary thread and spawns a future into it.
2020-01-19 20:59:30 +03:00
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 = "calloop"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.6.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "0b036167e76041694579972c28cf4877b4f92da222560ddb49008937b6a6727c"
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 = [
"log",
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
"nix 0.18.0",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "cassowary"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "df8670b8c7b9dae1793364eafadf7239c40d669904660c5960d74cfd80b46a53"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "cc"
cargo update
2021-02-22 11:09:01 +03:00
version = "1.0.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
2021-02-22 11:09:01 +03:00
checksum = "e3c69b077ad434294d3ce9f1f6143a2a4b89a8a2d54ef813d85003a4fd1137fd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"jobserver",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "cfg-if"
version = "0.1.10"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "4785bdd1c96b2a846b2bd7cc02e86b6b3dbf14e7e53446c4f54c92a361040822"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "cfg-if"
version = "1.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "baf1de4339761588bc0619e3cbc0120ee582ebb74b53b4efbf79117bd2da40fd"
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "cfg_aliases"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fd16c4719339c4530435d38e511904438d07cce7950afa3718a84ac36c10e89e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "cgl"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "0ced0551234e87afee12411d535648dd89d2e7f34c78b753395567aff3d447ff"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "chrono"
cargo update
2020-10-02 17:16:20 +03:00
version = "0.4.19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-10-02 17:16:20 +03:00
checksum = "670ad68c9088c2a963aaa298cb369688cf3f9465ce5e2d4ca10e6e0098a1ce73"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-10-02 17:16:20 +03:00
"libc",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"num-integer",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 0.2.14",
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
"pure-rust-locales",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"time",
cargo update
2020-10-02 17:16:20 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "clap"
cargo update
2020-09-09 19:31:37 +03:00
version = "2.33.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "37e58ac78573c40708d45522f0d80fa2f01cc4f9b4e2bf749807255454312002"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"ansi_term",
"atty",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
lua: give a nice error message when using an invalid field name Make a reasonable suggestion to the user based on similarity with possible field names, but don't error out. This facilitates evolving the configuration over time, and makes the config more forgiving of typos.
2020-03-01 20:39:14 +03:00
"strsim 0.8.0",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"textwrap 0.11.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-width",
"vec_map",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "clipboard"
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 = "25a904646c0340239dcf7c51677b33928bf24fdf424b79a57909c0109075b2e7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"clipboard-win",
"objc",
"objc-foundation",
"objc_id",
"x11-clipboard",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "clipboard-win"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "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 = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "cloudabi"
version = "0.0.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "ddfc5b9aa5d4507acaf872de71051dfd0e309860e88966e1051e462a077aac4f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "cocoa"
cargo update
2020-06-30 03:52:14 +03:00
version = "0.20.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "0c49e86fc36d5704151f5996b7b3795385f50ce09e3be0f47a0cfde869681cf8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"block",
"core-foundation 0.7.0",
cargo update
2020-06-30 03:52:14 +03:00
"core-graphics 0.19.2",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
"objc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "cocoa-foundation"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "7ade49b65d560ca58c403a479bb396592b155c0185eada742ee323d1d68d6318"
dependencies = [
"bitflags",
"block",
"core-foundation 0.9.1",
"core-graphics-types",
"foreign-types",
"libc",
"objc",
]
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",
"varbincode",
"wezterm-term",
"zstd",
]
add wgpu example
2021-05-06 19:04:16 +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",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "color_quant"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.1.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "3d7b894f5411737b7867f4827955924d7c254fc9f4d91a6aad6b097804b1018b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "colored"
version = "1.9.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f4ffc801dacf156c5854b9df4f425a626539c3a6ef7893cc0c5084a23f0b6c59"
dependencies = [
"atty",
"lazy_static",
"winapi 0.3.9",
]
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "concurrent-queue"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.2.2"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "30ed07550be01594c6026cff2a1d7fe9c8f683caa798e12b68694ac9e88286a3"
cargo update
2020-06-30 03:52:14 +03:00
dependencies = [
"cache-padded",
]
move config into its own crate
2020-10-02 21:50:50 +03:00
[[package]]
name = "config"
version = "0.1.0"
dependencies = [
"anyhow",
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
"battery",
introduce freetype_load_flags and freetype_load_target config In the earlier times wezterm supported different font rasterizers, and the configuration was a bit vague and generic to accomodate differences in how the rasterizers worked. Since then, we've standardized on freetype. One of the things that's been bothering me for a while is that we have some fiddly logic to transform from the config to the freetype flags. This commit does away with the transformation and simply exposes the two sets of freetype options. The main thing that I expect people to play with is `freetype_load_target` which can have one of the following values: ``` pub enum FreeTypeLoadTarget { /// This corresponds to the default hinting algorithm, optimized for standard gray-level rendering. Normal, /// A lighter hinting algorithm for non-monochrome modes. Many generated glyphs are more fuzzy but better resemble its original shape. A bit like rendering on Mac OS X. This target implies FT_LOAD_FORCE_AUTOHINT. Light, /// Strong hinting algorithm that should only be used for monochrome output. The result is probably unpleasant if the glyph is rendered in non-monochrome modes. Mono, /// A variant of Normal optimized for horizontally decimated LCD displays. HorizontalLcd, /// A variant of Normal optimized for vertically decimated LCD displays. VerticalLcd, } ``` I expect most people will want to set this to one of `Normal`, `Light` or `HorizontalLcd`. `HorizontalLcd` is what `font_antialias=Subpixel` used to select. refs: #491
2021-02-21 00:54:56 +03:00
"bitflags",
cargo update
2021-05-01 19:42:46 +03:00
"bstr 0.2.16",
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
"chrono",
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",
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
"filenamegen",
"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",
"portable-pty",
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
"pretty_env_logger",
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",
add window:set_config_overrides lua method This commit expands on the prior commits to introduce the concept of per-window configuration overrides. Each TermWindow maintains json compatible object value holding a map of config key -> config value overrides. When the window notices that the config has changed, the config file is loaded, the CLI overrides (if any) are applied, and then finally the per-window overrides, before attempting to coerce the resultant lua value into a Config object. This mechanism has some important constraints: * Only data can be assigned to the overrides. Closures or special lua userdata object handles are not permitted. This is because the lifetime of those objects is tied to the lua context in which they were parsed, which doesn't really exist in the context of the window. * Only simple keys are supported for the per-window overrides. That means that trying to override a very specific field of a deeply structured value (eg: something like `font_rules[1].italic = false` isn't able to be expressed in this scheme. Instead, you would need to assign the entire `font_rules` key. I don't anticipate this being a common desire at this time; if more advance manipulations are required, then I have some thoughts on an event where arbitrary lua modifications can be applied. The implementation details are fairly straight-forward, but in testing the two examplary use cases I noticed that some hangovers from supporting overrides for a couple of font related options meant that the window-specific config wasn't being honored. I've removed the code that handled those overrides in favor of the newer more general CLI option override support, and threaded the config through to the font code. closes: #469 closes: #329
2021-02-28 01:53:19 +03:00
"serde_json",
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",
lua: add wezterm.format function The intent is to use this to compose text for a configurable tab bar. refs: https://github.com/wez/wezterm/issues/500
2021-03-02 11:15:37 +03:00
"terminfo",
move config into its own crate
2020-10-02 21:50:50 +03:00
"termwiz",
"toml",
Take care to restore the original umask wezterm sets a more restrictive umask (`0o077`) by default so that any files that it creates (eg: unix domain socket, log files) are more secure by default. However, some environments rely on the more general default of (`0o022`) without checking that it is set. This matters because programs spawned by wezterm inherit its more restricted umask. I hadn't noticed this because I've had `umask 022` in my shell RC files since sometime in the 1990's. This commit adds some plumbing to the pty layer to specify an optional umask for the child process, and some more to our umask saver helper so that any thread can determine the saved umask without needing a reference to the saver itself, which may be in a different crate. The logic in the config crate has been adjusted to connect the saved value to the default command builder arguments. The net result of this is that running `wezterm -n start bash -- --norc` and typing `umask` in the resultant window now prints `0022`. refs: #416
2021-01-07 20:14:51 +03:00
"umask",
add wezterm.truncate_to_width refs: https://github.com/wez/wezterm/issues/647
2021-04-27 08:25:52 +03:00
"unicode-segmentation",
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
"wezterm-input-types",
move config into its own crate
2020-10-02 21:50:50 +03:00
"wezterm-term",
and another speculative diff to fixup windows build
2020-10-05 23:56:11 +03:00
"winapi 0.3.9",
move config into its own crate
2020-10-02 21:50:50 +03:00
]
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
[[package]]
name = "const-sha1"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fb58b6451e8c2a812ad979ed1d83378caa5e927eef2622017a45f251457c2c9d"
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "copyless"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a2df960f5d869b2dd8532793fde43eb5427cceb126c929747a26823ab0eeb536"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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"
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.9.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 = "0a89e2ae426ea83155dccf10c0fa6b1463ef6d5fcb44cee0b224a408fa640a62"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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.8.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",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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"
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.8.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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 = "ea221b5284a47e40033bf9b66f35f984ec0ea2931eb03505246cd27a963f981b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "core-graphics"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
version = "0.19.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
checksum = "b3889374e6ea6ab25dba90bb5d96202f61108058361f6dc72e8b03e6f8bbe923"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
"core-foundation 0.7.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "core-graphics"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
version = "0.22.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 (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
checksum = "269f35f69b542b80e736a20a89a05215c0ce80c2c03c514abb2e318b78379d86"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
"core-foundation 0.9.1",
"core-graphics-types",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
name = "core-graphics-types"
version = "0.1.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: remove font-loader dependency This commit replaces it with the underlying core text calls on macos. refs: #337
2020-11-22 22:19:44 +03:00
checksum = "3a68b68b3446082644c91ac778bf50cd4104bfb002b5a6a7c44cca5a2c70788b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
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.9.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
"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 = [
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.9.1",
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
"core-graphics 0.22.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",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "cpuid-bool"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8aebca1129a03dc6dc2b127edd729435bbc4a37e1d5f4d7513165089ceb02634"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.2.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "81156fece84ab6a9f2afdb109ce3ae577e42b1228441eded99bd77f627953b1a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
ssh: use a single window for authenticating a session This makes it so that we preserve context while showing the connection status and authentication prompts.
2020-01-26 00:00:16 +03:00
[[package]]
name = "crossbeam"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.8.0"
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"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "fd01a6eb3daaafa260f6fc94c3a6c36390abc2080e38e3e34ced87393fb77d80"
ssh: use a single window for authenticating a session This makes it so that we preserve context while showing the connection status and authentication prompts.
2020-01-26 00:00:16 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"cfg-if 1.0.0",
"crossbeam-channel",
"crossbeam-deque",
"crossbeam-epoch",
ssh: use a single window for authenticating a session This makes it so that we preserve context while showing the connection status and authentication prompts.
2020-01-26 00:00:16 +03:00
"crossbeam-queue",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "crossbeam-channel"
cargo update
2021-04-12 17:54:46 +03:00
version = "0.5.1"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "06ed27e177f16d65f0f0c22a213e17c696ace5dd64b14258b52f9417ccb52db4"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
"cfg-if 1.0.0",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "crossbeam-deque"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "94af6efb46fef72616855b036a624cf27ba656ffc9be1b9a3c931cfc7749a9a9"
dependencies = [
"cfg-if 1.0.0",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-epoch",
"crossbeam-utils",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
]
[[package]]
name = "crossbeam-epoch"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.9.4"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "52fb27eab85b17fbb9f6fd667089e07d6a2eb8743d02639ee7f6a7a7729c9c94"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
"cfg-if 1.0.0",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-utils",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"lazy_static",
cargo update
2021-04-05 18:46:55 +03:00
"memoffset 0.6.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
"scopeguard",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "crossbeam-queue"
deps: 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 = "0f6cb3c7f5b8e51bc3ebb73a2327ad4abdbd119dc13223f14f961d2f38486756"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"cfg-if 1.0.0",
"crossbeam-utils",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "crossbeam-utils"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.8.4"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "4feb231f0d4d6af81aed15928e58ecf5816aa62a2393e2c82f46973e92a9a278"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
"lazy_static",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ctor"
cargo update
2021-03-25 20:08:03 +03:00
version = "0.1.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
2021-03-25 20:08:03 +03:00
checksum = "5e98e2ad1a782e33928b96fc3948e7c355e5af34ba4de7670fe8bac2a3b2006d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "d3d12"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "091ed1b25fe47c7ff129fc440c23650b6114f36aa00bc7212cc8041879294428"
dependencies = [
"bitflags",
"libloading 0.7.0",
"winapi 0.3.9",
]
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "deflate"
cargo update
2020-07-09 09:54:56 +03:00
version = "0.8.6"
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
2020-07-09 09:54:56 +03:00
checksum = "73770f8e1fe7d64df17ca66ad28994a0a623ea497fa69486e14984e715c5d174"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
dependencies = [
"adler32",
"byteorder",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "derivative"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fcc3dd5e9e9c0b295d6e1e4d811fb6f157d5ffd784b8d202fc62eac8035a770b"
dependencies = [
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "diff"
version = "0.1.12"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0e25ea47919b1560c4e3b7fe0aaab9becf5b84a10325ddf7db0f0ba5e1026499"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "difference"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "524cbf6897b527295dff137cec09ecf3a05f4fddffd7dfcd1585403449e74198"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "digest"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f3d0c8c8752312f9713efd397ff63acb9f85585afbf179282e720e7704954dd5"
dependencies = [
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
"generic-array 0.12.4",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "digest"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d3dd60d1080a57a05ab032377049e0591415d2b31afd7028356dbf3cc6dcb066"
dependencies = [
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
"generic-array 0.14.4",
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "dirs"
version = "2.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "13aea89a5c93364a98e9b37b2fa237effbb694d5cfe01c5b70941f7eb087d5e3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"dirs-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
[[package]]
name = "dirs-next"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b98cf8ebf19c3d1b223e151f99a4f9f0690dca41414773390fc824184ac833e1"
dependencies = [
"cfg-if 1.0.0",
"dirs-sys-next",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "dirs-sys"
cargo update
2021-04-26 18:34:45 +03:00
version = "0.3.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
2021-04-26 18:34:45 +03:00
checksum = "03d86534ed367a67548dc68113a0f5db55432fdfbb6e6f9d77704397d95d5780"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2021-04-26 18:34:45 +03:00
"redox_users",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
[[package]]
name = "dirs-sys-next"
cargo update
2021-01-11 19:43:32 +03:00
version = "0.1.2"
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-11 19:43:32 +03:00
checksum = "4ebda144c4fe02d1f7ea1a7d9641b6fc6b580adcfa024ae48797ecdeb6825b4d"
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
dependencies = [
"libc",
cargo update
2021-04-26 18:34:45 +03:00
"redox_users",
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "dlib"
cargo update
2020-06-06 20:08:02 +03:00
version = "0.4.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-06 20:08:02 +03:00
checksum = "b11f15d1e3268f140f68d390637d5e76d849782d971ae7063e0da69fe9709a76"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-03-01 20:02:05 +03:00
"libloading 0.6.7",
]
[[package]]
name = "dlib"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ac1b7517328c04c2aa68422fc60a41b92208182142ed04a25879c26c8f878794"
dependencies = [
"libloading 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
]
refine skip_close_confirmation_for_processes_named to look at proc tree That means that we won't be fooled by a shell with a backgrounded editor. refs: https://github.com/wez/wezterm/issues/562
2021-03-23 07:34:10 +03:00
[[package]]
name = "doc-comment"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fea41bba32d969b513997752735605054bc0dfa92b4c56bf1189f2e174be7a10"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "downcast-rs"
cargo update
2020-06-30 03:52:14 +03:00
version = "1.2.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "9ea835d29036a4087793836fa931b08837ad5e957da9e23886b29586fb9b6650"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "dwrote"
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
version = "0.11.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
checksum = "439a1c2ba5611ad3ed731280541d36d2e9c4ac5e7fb818a27b604bdc5a6aa65b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
"serde",
"serde_derive",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
"wio",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "either"
cargo update
2020-10-02 17:16:20 +03:00
version = "1.6.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-10-02 17:16:20 +03:00
checksum = "e78d4f1cc4ae33bbfc157ed5d5a5ef3bc29227303d595861deb238fcec4e9457"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "embed-resource"
cargo update
2021-04-26 18:34:45 +03:00
version = "1.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
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "d0ea6debf1262982d24274dc85f3374b42534df140897c25cea86b81e017d470"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-02-01 18:54:01 +03:00
"cc",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
deps: cargo update
2020-12-14 19:50:45 +03:00
"winreg 0.8.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "encoding_rs"
cargo update
2021-02-08 09:51:28 +03:00
version = "0.8.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
2021-02-08 09:51:28 +03:00
checksum = "80df024fbc5ac80f87dfef0d9f5209a252f2a497f7f42944cff24d8253cac065"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Allow matching font weight and font width in `wezterm.font` refs: https://github.com/wez/wezterm/issues/655
2021-04-09 01:41:07 +03:00
[[package]]
name = "enum-display-derive"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f16ef37b2a9b242295d61a154ee91ae884afff6b8b933b486b12481cc58310ca"
dependencies = [
"proc-macro2",
"quote",
"syn",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "enumflags2"
version = "0.6.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "83c8d82922337cd23a15f88b70d8e4ef5f11da38dd7cdb55e84dd5de99695da0"
dependencies = [
"enumflags2_derive",
"serde",
]
[[package]]
name = "enumflags2_derive"
version = "0.6.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "946ee94e3dbf58fdd324f9ce245c7b238d46a66f00e86a020b71996349e46cce"
dependencies = [
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
[[package]]
name = "env-bootstrap"
version = "0.1.0"
dependencies = [
add debug overlay Adds a `ShowDebugOverlay` key assignment that will create a tab overlay that shows a limited number of recently logged events. refs: https://github.com/wez/wezterm/issues/641
2021-05-03 06:50:01 +03:00
"chrono",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
"cocoa",
"config",
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one.
2020-12-10 21:08:49 +03:00
"dirs-next",
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",
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",
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
"pretty_env_logger",
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"
version = "0.7.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "44533bbbb3bb3c1fa17d9f2e4e38bbbaf8396ba82193c4cb1b6445d711445d36"
dependencies = [
"atty",
"humantime",
"log",
"regex",
"termcolor",
]
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
[[package]]
name = "euclid"
cargo update
2021-04-12 17:54:46 +03:00
version = "0.22.3"
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-04-12 17:54:46 +03:00
checksum = "536d206ede9fae5a338a1576623b04fd2459f6086e551d374ebf10e9b78bb4df"
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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 0.2.14",
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
2020-10-02 17:16:20 +03:00
version = "2.5.1"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-10-02 17:16:20 +03:00
checksum = "f7531096570974c3a9dcf9e4b8e1cede1ec26cf5046219fb3b9d897503b9be59"
cargo update
2020-09-09 19:31:37 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "evmap"
version = "6.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "6fdb60074c9b82c91f8702fa5351b85d22b668dae7f73bf06b44a09bc372380f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hashbrown 0.5.0",
cargo update
2021-01-11 19:43:32 +03:00
"smallvec 0.6.14",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "fake-simd"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e88a8acf291dafb59c2d96e8f59828f3838bb1a70398823ade51a84de6a6deed"
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "fastrand"
cargo update
2021-04-26 18:34:45 +03:00
version = "1.4.1"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "77b705829d1e87f762c2df6da140b26af5839e1033aa84aa5f56bb688e4e1bdb"
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"
fix build for windows
2020-09-11 01:00:43 +03:00
version = "0.7.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
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",
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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
2021-01-26 07:51:25 +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
2021-01-26 07:51:25 +03:00
checksum = "1d34cfa13a63ae058bfa601fe9e313bbdb3746427c1459185464ce0fcf62e1e8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2021-05-01 19:42:46 +03:00
"redox_syscall 0.2.7",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "fixedbitset"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "37ab347416e802de484e4d03c7316c48f1ecb56574dfd4a46a80f173ce1de04d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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
2021-02-01 18:54:01 +03:00
version = "1.0.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
2021-02-01 18:54:01 +03:00
checksum = "cd3aec53de10fe96d7d8c565eb17f2c687bb5518a2ec453b5b1252964526abe0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"crc32fast",
"libc",
"libz-sys",
cargo update
2021-03-01 20:02:05 +03:00
"miniz_oxide 0.4.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
]
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"
cargo update
2021-04-26 18:34:45 +03:00
version = "0.10.5"
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
2021-04-26 18:34:45 +03:00
checksum = "fa9d66b91e902db43baefd8e40c8678ce29db2cf1d88ebd715174368d5fe70a9"
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",
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
"spinning_top",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "fnv"
cargo update
2020-05-26 08:25:39 +03:00
version = "1.0.7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-26 08:25:39 +03:00
checksum = "3f9eec918d3f24069decb9af1554cad7c880e2da24a9afd88aca000531ab82c1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "fontconfig"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"pkg-config",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "foreign-types"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f6f339eb8adc052cd2ca78910fda869aefa38d22d5cb648e6485e4d3fc06f3b1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types-shared",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "foreign-types-shared"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "00b0228411908ca8685dba7fc2cdd70ec9990a6e753e89b6ac91a84c40fbaf4b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "form_urlencoded"
cargo update
2021-02-22 11:09:01 +03:00
version = "1.0.1"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-22 11:09:01 +03:00
checksum = "5fc25a87fa4fd2094bffb06925852034d90a17f0d1e05197d4956d3555752191"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
"matches",
"percent-encoding",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "freetype"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fsevent"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "5ab7d1bd1bd33cc98b0889831b72da23c0aa4df9cec7e0702f46ecea04b35db6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fsevent-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fsevent-sys"
version = "2.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f41b048a94555da0f42f1d632e2e19510084fb8e303b0daa2816e733fb3644a0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fuchsia-cprng"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "a06f77d526c1a601b7c4cdd98f54b5eaabffc14d5f2f0296febdc7f357c6d3ba"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "fuchsia-zircon"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "2e9763c69ebaae630ba35f74888db465e49e259ba1bc0eda7d06f4a067615d82"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fuchsia-zircon-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "fuchsia-zircon-sys"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "3dcaa9ae7725d12cdb85b3ad99a434db70b468c09ded17e012d86b5c1010f7a7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
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 = "funty"
cargo update
2020-12-28 19:23:20 +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
2020-12-28 19:23:20 +03:00
checksum = "fed34cd105917e91daa4da6b3728c47b068749d6a62c59811f06ed2ac71d9da7"
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
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
2021-04-12 17:54:46 +03:00
version = "0.3.14"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "a9d5813545e459ad3ca1bff9915e9ad7f1a47dc6a91b627ce321d5863b7dd253"
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
2021-04-12 17:54:46 +03:00
version = "0.3.14"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "ce79c6a52a299137a6013061e0cf0e688fce5d7f1bc60125f520912fdb29ec25"
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
2021-04-12 17:54:46 +03:00
version = "0.3.14"
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
2021-04-12 17:54:46 +03:00
checksum = "098cd1c6dda6ca01650f1a37a794245eb73181d0d4d4e955e2f3c37db7af1815"
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
2021-04-12 17:54:46 +03:00
version = "0.3.14"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "10f6cb7042eda00f0049b1d2080aa4b93442997ee507eb3828e8bd7577f94c9d"
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
2021-04-12 17:54:46 +03:00
version = "0.3.14"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "365a1a1fb30ea1c03a830fdb2158f5236833ac81fa0ad12fe35b29cddc35cb04"
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
2020-12-20 03:44:27 +03:00
version = "1.11.3"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-12-20 03:44:27 +03:00
checksum = "b4481d0cd0de1d204a4fa55e7d45f07b1d958abcb06714b3446438e2eff695fb"
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
2021-04-12 17:54:46 +03:00
version = "0.3.14"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "668c6733a182cd7deb4f1de7ba3bf2120823835b3bcfbeacf7d2c4a773c1bb8b"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"proc-macro-hack",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
]
[[package]]
name = "futures-sink"
cargo update
2021-04-12 17:54:46 +03:00
version = "0.3.14"
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
2021-04-12 17:54:46 +03:00
checksum = "5c5629433c555de3d82861a7a4e3794a4c40040390907cfbfd7143a92a426c23"
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
2021-04-12 17:54:46 +03:00
version = "0.3.14"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "ba7aa51095076f3ba6d9a1f702f74bd05ec65f555d70d2033d55ba8d69f581bc"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +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-util"
cargo update
2021-04-12 17:54:46 +03:00
version = "0.3.14"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "3c144ad54d60f23927f0a6b6d816e4271278b64f005ad65e4e35291d2de9c025"
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",
"proc-macro-hack",
"proc-macro-nested",
"slab",
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "fxhash"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c31b6d751ae2c7f11320402d34e41349dd1016f8d5d45e48c4312bc8625af50c"
dependencies = [
"byteorder",
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "generic-array"
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
version = "0.12.4"
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
checksum = "ffdf9f34f1447443d37393cc6c2b8313aebddcd96906caf34e54c68d8e57d7bd"
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
dependencies = [
"typenum",
]
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "generic-array"
version = "0.14.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "501466ecc8a30d1d3b7fc9229b122b2ce8ed6e9d9223f1138d4babb253e51817"
dependencies = [
"typenum",
"version_check",
]
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
[[package]]
name = "getopts"
version = "0.2.21"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "14dbbfd5c71d70241ecf9e6f13737f7b5ce823821063188d7e46c41d371eebd5"
dependencies = [
"unicode-width",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "getrandom"
cargo update
2021-01-06 11:28:11 +03:00
version = "0.1.16"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-06 11:28:11 +03:00
checksum = "8fc3cb4d91f53b50155bdcfd23f6a4c39ae1969c2ae85982b135750cccaf5fce"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"cfg-if 1.0.0",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"libc",
"wasi 0.9.0+wasi-snapshot-preview1",
]
[[package]]
name = "getrandom"
cargo update to pick up mlua 5.0.1 and the cross compilation fixes
2021-01-21 07:16:30 +03:00
version = "0.2.2"
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 to pick up mlua 5.0.1 and the cross compilation fixes
2021-01-21 07:16:30 +03:00
checksum = "c9495705279e7140bf035dde1f6e750c162df8b625267cd52cc44e0b156732c8"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"cfg-if 1.0.0",
"js-sys",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2021-02-01 18:54:01 +03:00
"wasi 0.10.2+wasi-snapshot-preview1",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"wasm-bindgen",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "gfx-auxil"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9ccf8711c9994dfa34337466bee3ae1462e172874c432ce4eb120ab2e98d39cf"
dependencies = [
"fxhash",
"gfx-hal",
"spirv_cross",
]
[[package]]
name = "gfx-backend-dx11"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6f839f27f8c8a6dc553ccca7f5b35a42009432bc25db9688bba7061cd394161f"
dependencies = [
"arrayvec",
"bitflags",
"gfx-auxil",
"gfx-hal",
"libloading 0.7.0",
"log",
"parking_lot 0.11.1",
"range-alloc",
"raw-window-handle",
"smallvec 1.6.1",
"spirv_cross",
"thunderdome",
"winapi 0.3.9",
"wio",
]
[[package]]
name = "gfx-backend-dx12"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3937738b0da5839bba4e33980d29f9a06dbce184d04a3a08c9a949e7953700e3"
dependencies = [
"arrayvec",
"bit-set",
"bitflags",
"d3d12",
"gfx-auxil",
"gfx-hal",
"log",
"parking_lot 0.11.1",
"range-alloc",
"raw-window-handle",
"smallvec 1.6.1",
"spirv_cross",
"thunderdome",
"winapi 0.3.9",
]
[[package]]
name = "gfx-backend-empty"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2ac55ada4bfcd35479b3421eea324d36d7da5f724e2f66ecb36d4efdb7041a5e"
dependencies = [
"gfx-hal",
"log",
"raw-window-handle",
]
[[package]]
name = "gfx-backend-gl"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0caa03d6e0b7b4f202aea1f20c3f3288cfa06d92d24cea9d69c9a7627967244a"
dependencies = [
"arrayvec",
"bitflags",
"fxhash",
"gfx-hal",
"glow",
"js-sys",
"khronos-egl",
"libloading 0.7.0",
"log",
"naga",
"parking_lot 0.11.1",
"raw-window-handle",
"wasm-bindgen",
"web-sys",
]
[[package]]
name = "gfx-backend-metal"
version = "0.8.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "96a809b746d8063ade971cfb3f188e2b0d655926979823d80be7590390f4b911"
dependencies = [
"arrayvec",
"bitflags",
"block",
"cocoa-foundation",
"copyless",
"foreign-types",
"fxhash",
"gfx-hal",
"log",
"metal",
"naga",
"objc",
"parking_lot 0.11.1",
"profiling",
"range-alloc",
"raw-window-handle",
"storage-map",
]
[[package]]
name = "gfx-backend-vulkan"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a353fc6fdb42ec646de49bbb74e4870e37a7e680caf33f3ac0615c30b1146d94"
dependencies = [
"arrayvec",
"ash",
"byteorder",
"core-graphics-types",
"gfx-hal",
"inplace_it",
"log",
"naga",
"objc",
"parking_lot 0.11.1",
"raw-window-handle",
"smallvec 1.6.1",
"winapi 0.3.9",
]
[[package]]
name = "gfx-hal"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6d285bfd566f6b9134af908446ca350c0a1047495dfb9bbd826e701e8ee1d259"
dependencies = [
"bitflags",
"naga",
"raw-window-handle",
"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
[[package]]
name = "gif"
cargo update
2021-03-25 20:08:03 +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"
cargo update
2021-03-25 20:08:03 +03:00
checksum = "5a668f699973d0f573d15749b7002a9ac9e1f9c6b220e7b165601334c173d8de"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 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.23.0"
cargo update
2020-05-26 08:25:39 +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 = "f6503fe142514ca4799d4c26297c4248239fe8838d827db6bd6065c6ed29a6ce"
cargo update
2020-05-26 08:25:39 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "gl_generator"
version = "0.14.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "1a95dfc23a2b4a9a2f5ab41d194f8bfda3cabec42af4e39f08c339eb2a0c124d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"khronos_api",
"log",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"xml-rs",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "glium"
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
version = "0.28.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"
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
checksum = "7eeec7b733d14519e2541f4cc8a1230de9143d4ec439dd51b6c048d8ec991759"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"backtrace",
"fnv",
window: glium and gl_generator version bump
2020-06-15 07:24:54 +03:00
"gl_generator",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
window: 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
"memoffset 0.5.6",
cargo update
2021-01-11 19:43:32 +03:00
"smallvec 1.6.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
"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
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "gloo-timers"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "47204a46aaff920a1ea58b11d03dec6f704287d27561724a4631e450654a891f"
dependencies = [
"futures-channel",
"futures-core",
"js-sys",
"wasm-bindgen",
"web-sys",
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "glow"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "4b80b98efaa8a34fce11d60dd2ce2760d5d83c373cbcc73bb87c2a3a84a54108"
dependencies = [
"js-sys",
"slotmap",
"wasm-bindgen",
"web-sys",
]
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
[[package]]
name = "glyph-names"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8050dc1be3880f690a771051d09727d759229d299afffa1488acc3556879039d"
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "gpu-alloc"
version = "0.4.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc76088804bb65a6f3b880bea9306fdaeffb25ebb453105fafa691282ee9fdba"
dependencies = [
"bitflags",
"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 = [
"bitflags",
]
[[package]]
name = "gpu-descriptor"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "e8a70f1e87a3840ed6a3e99e02c2b861e4dbdf26f0d07e38f42ea5aff46cfce2"
dependencies = [
"bitflags",
"gpu-descriptor-types",
"hashbrown 0.9.1",
]
[[package]]
name = "gpu-descriptor-types"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "363e3677e55ad168fef68cf9de3a4a310b53124c5e784c53a1d70e92d23f2126"
dependencies = [
"bitflags",
]
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"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "bc7cccefbf418f663e11e9500326f46a44273dc598210bbedc8bbe95e696531f"
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",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "harfbuzz"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
wezterm-font: remove font-kit dep This wasn't used by anything and the version was getting pretty stale. Upgrading is awkward because newer versions pull in an incompatible freetype library version.
2020-10-25 08:01:00 +03:00
"freetype",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "hashbrown"
version = "0.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "e1de41fb8dba9714efd92241565cdff73f78508c95697dd56787d3cba27e2353"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
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 = "hashbrown"
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
version = "0.9.1"
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"
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
checksum = "d7afe4a420e3fe79967a00898cc1f4db7c8a49a9333a29f8a4bd76a253d5cd04"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
dependencies = [
cargo update
2020-05-26 08:25:39 +03:00
"ahash",
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
]
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
[[package]]
name = "hdrhistogram"
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 = "7.2.0"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "af54a13c410de2b5e2d611475072834b86d7b2f835a2a8f7b1b1248d3e9bfbd8"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"byteorder",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-channel",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"flate2",
cargo update
2021-02-15 23:14:00 +03:00
"nom 6.1.2",
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
"num-traits 0.2.14",
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
2020-12-28 19:23:20 +03:00
version = "0.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
2020-12-28 19:23:20 +03:00
checksum = "87cbf45460356b7deeb5e3415b5563308c0a9b057c85e12b06ad551f98d0a6ac"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-segmentation",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "hermit-abi"
cargo update
2021-01-18 10:38:11 +03:00
version = "0.1.18"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-18 10:38:11 +03:00
checksum = "322f4de77956e22ed0e5032c359a0f1273f1f7f0d79bfa3b8ffbc730d7fbcc5c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "hostname"
cargo update
2020-03-14 19:39:38 +03:00
version = "0.3.1"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-03-14 19:39:38 +03:00
checksum = "3c731c3e10504cc8ed35cfe2f1db4c9274c3d35fa486e3b31df46f068ef3e867"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"libc",
"match_cfg",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
]
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "http_req"
deps: cargo update
2020-12-14 19:50:45 +03:00
version = "0.7.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: cargo update
2020-12-14 19:50:45 +03:00
checksum = "1dab1fb99f5163b9b25805e4c191ea9425ae311442688bfe03c97e8a2ba66e9d"
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 = [
"rustls",
"unicase",
"webpki",
"webpki-roots",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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"
version = "1.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 = "df004cfca50ef23c36850aaaa59ad52cc70d0e90243c3c7737a4dd32dc7a3c4f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"quick-error",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "idna"
cargo update
2021-04-19 19:23:33 +03:00
version = "0.2.3"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "418a0a6fab821475f634efe3ccc45c013f742efe03d853e8d3355d5cb850ecf8"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"matches",
"unicode-bidi",
"unicode-normalization",
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
]
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 primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
version = "0.23.14"
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 primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
checksum = "24ffcb7e7244a9bf19d35bf2883b9c080c4ced3c07a9895572178cdb8f13f6a1"
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",
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
"gif",
"jpeg-decoder",
"num-iter",
deps: misc updates
2020-12-29 20:21:50 +03:00
"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
"num-traits 0.2.14",
cargo update
2020-06-13 20:21:49 +03:00
"png",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"scoped_threadpool",
cargo update
2020-06-13 20:21:49 +03:00
"tiff",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "indexmap"
version = "1.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "824845a0bf897a9042383849b02c1bc219c2383772efcd5c6f9766fa4b81aef3"
dependencies = [
"autocfg",
"hashbrown 0.9.1",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "inotify"
cargo update
2020-06-06 20:08:02 +03:00
version = "0.7.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-06 20:08:02 +03:00
checksum = "4816c66d2c8ae673df83366c18341538f234a26d65a9ecea5c348b453ac1d02f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"inotify-sys",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "inotify-sys"
cargo update
2021-01-18 10:38:11 +03:00
version = "0.1.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-18 10:38:11 +03:00
checksum = "e05c02b5e89bff3b946cedeca278abc628fe811e604f027c45a8aa3cf793d0eb"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "inplace_it"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "90953f308a79fe6d62a4643e51f848fbfddcd05975a38e69fdf4ab86a7baf7ca"
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 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.1.9"
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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "61124eeebbd69b8190558df225adf7e4caafce0d743919e5d6b19652314ec5ec"
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ioctl-rs"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f7970510895cee30b3e9128319f2cefd4bde883a39f38baa279567ba3a7eb97d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "iovec"
version = "0.1.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "b2b3ea6ff95e175473f8ffe6a7eb7c00d054240321b84c57051175fe3c1e075e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "itertools"
version = "0.8.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 = "f56a2d0bc861f9165be4eb3442afd3c236d8a98afd426f65d92324ae1091a484"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "itoa"
cargo update
2020-12-28 19:23:20 +03:00
version = "0.4.7"
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
2020-12-28 19:23:20 +03:00
checksum = "dd25036021b0de88a0aff6b850051563c6516d0bf53f8638938edbb9de732736"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "jobserver"
cargo update
2021-04-19 19:23:33 +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
2021-04-19 19:23:33 +03:00
checksum = "972f5ae5d1cb9c6ae417789196c803205313edde988685da5e3aae0827b9e7fd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "jpeg-decoder"
cargo update
2021-02-01 18:54:01 +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
2021-02-01 18:54:01 +03:00
checksum = "229d53d58899083193af11e15917b5640cd40b29ff475a1fe4ef725deb02d0f2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2021-04-05 18:46:55 +03:00
version = "0.3.50"
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-04-05 18:46:55 +03:00
checksum = "2d99f9e3e84b8f67f846ef5b4cbbc3b1c29f6c759fcbce6f01aa0e73d932a24c"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"wasm-bindgen",
]
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "k9"
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 = "0.11.0"
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"
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
checksum = "94244855304b22b07529bbcaf413983d0be2ed70dfdd82efcd8c5b7c5723b1a7"
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
dependencies = [
"anyhow",
"colored",
"diff",
"lazy_static",
"libc",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
"regex",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"syn",
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
"term_size",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "kernel32-sys"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "7507624b29483431c0ba2d82aece8ca6cdba9382bff4ddd0f7490560c056098d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi 0.2.8",
"winapi-build",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +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.0",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "khronos_api"
version = "3.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "e2db585e1d738fc771bf08a151420d3ed193d9d895a36df7f6f8a9456b911ddc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "kv-log-macro"
cargo update
2020-07-09 09:54:56 +03:00
version = "1.0.7"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-07-09 09:54:56 +03:00
checksum = "0de8b303297635ad57c9f5059fd9cee7a47f8e8daa09df0fcd07dd39fb22977f"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
dependencies = [
"log",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "lazy_static"
version = "1.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "e2abad23fbc42b3700f2f279844dc832adb2b2eb069b2df918f455c4e18cc646"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "lazycell"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.3.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "830d08ce1d1d941e6b30645f1a0eb5643013d835ce3779a5fc208261dbe10f55"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "leb128"
version = "0.2.4"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "3576a87f2ba00f6f106fdfcd16db1d698d648a26ad8e0573cad8537c3c362d2a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
[[package]]
name = "lexical-core"
cargo update
2021-04-26 18:34:45 +03:00
version = "0.7.6"
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "6607c62aa161d23d17a9072cc5da0be67cdfc89d3afb1e8d9c842bebc2525ffe"
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
dependencies = [
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
"arrayvec",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update
2021-02-15 23:14:00 +03:00
"cfg-if 1.0.0",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"ryu",
"static_assertions",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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
2021-04-26 18:34:45 +03:00
version = "0.2.94"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "18794a8ad5b29321f790b55d93dfba91e125cb1a9edbd4f8e3150acc771c1a5e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2020-06-06 20:08:02 +03:00
[[package]]
name = "libloading"
cargo update
2021-01-18 10:38:11 +03:00
version = "0.6.7"
cargo update
2020-06-06 20:08:02 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-18 10:38:11 +03:00
checksum = "351a32417a12d5f7e82c368a66781e307834dae04c6ce0cd4456d52989229883"
cargo update
2020-06-06 20:08:02 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
cargo update
2020-06-06 20:08:02 +03:00
]
cargo update
2021-03-01 20:02:05 +03:00
[[package]]
name = "libloading"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6f84d96438c15fcd6c3f244c8fce01d1e2b9c6b5623e9c711dc9286d8fc92d6a"
dependencies = [
"cfg-if 1.0.0",
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "libssh2-sys"
cargo update
2021-02-04 10:28:23 +03:00
version = "0.2.21"
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
source = "git+https://github.com/wez/ssh2-rs.git?branch=win32ssl#c65067040c97a0cf7f96c69d6fc87764a32c34ae"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
"libz-sys",
"openssl-sys",
"pkg-config",
"vcpkg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "libz-sys"
cargo update
2021-05-01 19:42:46 +03:00
version = "1.1.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "de5435b8549c16d423ed0c03dbaafe57cf6c3344744f1242520d59c9d8ecec66"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
"pkg-config",
"vcpkg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "line_drawing"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f81902e542483002b103c6424d23e765c2e5a65f732923299053a601bce50ab2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"num-traits 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
]
[[package]]
name = "lock_api"
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
version = "0.3.4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
wezterm: lua: add glob and read_dir These functions are useful when dynamically constructing configuration.
2020-04-12 05:21:52 +03:00
checksum = "c4da24a77a3d8a6d4862d95f72e6fdb9c09a643ecdb402d754004a557f2bec75"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"scopeguard",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
[[package]]
name = "lock_api"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.4.4"
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
2021-05-01 19:42:46 +03:00
checksum = "0382880606dff6d15c9476c416d18690b72742aa7b605bb6dd6ec9030fbf07eb"
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 = [
"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
2021-02-01 18:54:01 +03:00
version = "0.4.14"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-01 18:54:01 +03:00
checksum = "51b9bbe6c47d51fc3e1a9b945965946b4c44142ab8792c50835a980d362c2710"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-02-01 18:54:01 +03:00
"cfg-if 1.0.0",
"value-bag",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
[[package]]
name = "lru"
cargo update
2021-02-15 23:14:00 +03:00
version = "0.6.5"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-15 23:14:00 +03:00
checksum = "1f374d42cdfc1d7dbf3d3dec28afab2eb97ffbf43a3234d795b5986dbf4b90ba"
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 = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"hashbrown 0.9.1",
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"
cargo update
2021-04-12 17:54:46 +03:00
version = "543.0.0"
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
2021-04-12 17:54:46 +03:00
checksum = "029180f994b9b36f47d905f92569b516acf7d073778e2e781c15ee375b1ca27d"
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 = [
cargo update
2021-05-01 19:42:46 +03:00
"bstr 0.2.16",
move lua helpers into own crate
2020-10-02 20:28:58 +03:00
"log",
"mlua",
"serde",
add window:set_config_overrides lua method This commit expands on the prior commits to introduce the concept of per-window configuration overrides. Each TermWindow maintains json compatible object value holding a map of config key -> config value overrides. When the window notices that the config has changed, the config file is loaded, the CLI overrides (if any) are applied, and then finally the per-window overrides, before attempting to coerce the resultant lua value into a Config object. This mechanism has some important constraints: * Only data can be assigned to the overrides. Closures or special lua userdata object handles are not permitted. This is because the lifetime of those objects is tied to the lua context in which they were parsed, which doesn't really exist in the context of the window. * Only simple keys are supported for the per-window overrides. That means that trying to override a very specific field of a deeply structured value (eg: something like `font_rules[1].italic = false` isn't able to be expressed in this scheme. Instead, you would need to assign the entire `font_rules` key. I don't anticipate this being a common desire at this time; if more advance manipulations are required, then I have some thoughts on an event where arbitrary lua modifications can be applied. The implementation details are fairly straight-forward, but in testing the two examplary use cases I noticed that some hangovers from supporting overrides for a couple of font related options meant that the window-specific config wasn't being honored. I've removed the code that handled those overrides in favor of the newer more general CLI option override support, and threaded the config through to the font code. closes: #469 closes: #329
2021-02-28 01:53:19 +03:00
"serde_json",
move lua helpers into own crate
2020-10-02 20:28:58 +03:00
"strsim 0.10.0",
"thiserror",
]
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
2021-03-15 16:32:14 +03:00
version = "210.1.3+restyfe08842"
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
2021-03-15 16:32:14 +03:00
checksum = "36d3de8377d8e0492b646527befb7eb826a9ecd2dc8c1f81ab0e654bc03a029b"
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
dependencies = [
"cc",
]
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
[[package]]
name = "mach"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b823e83b2affd8f40a9ee8c29dbc56404c1e34cd2710921f2801e2cf29527afa"
dependencies = [
"libc",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "malloc_buf"
version = "0.0.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "62bb907fe88d54d8d9ce32a3cceab4218ed2f6b7d35617cafe9adf84e43919cb"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "maplit"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3e2e65a1a2e43cfcb47a895c4c8b10d1f4a61097f9f254f183aee60cad9c651d"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "match_cfg"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "ffbee8634e0d45d258acb448e7eaab3fce7a0a467395d4d9f228e3c1f01fb2e4"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "matches"
version = "0.1.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "7ffc5c5338469d4d3ea17d269fa8ea3512ad247247c30bd2df69e68309ed0a08"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "maybe-uninit"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "60302e4db3a61da70c0cb7991976248362f30319e88850c487b9b95bbf059e00"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "memchr"
cargo update
2021-05-01 19:42:46 +03:00
version = "2.4.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "b16bd47d9e329435e309c58469fe0791c2d0d1ba96ec0954152a5ae2b04387dc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "memmap"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "6585fd95e7bb50d6cc31e20d4cf9afb4e2ba16c5846fc76793f11218da9c475b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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
[[package]]
name = "memmap2"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "d9b70ca2a6103ac8b665dc150b142ef0e4e89df640c9e6cf295d189c3caebe5a"
dependencies = [
"libc",
]
fonts: add custom freetype stream impl The intent is to reveal more context on what's happening in https://github.com/wez/wezterm/issues/671 As a nice side benefit, this avoids the potential inability to open paths that are not utf8 or representable as c-strings on Windows. And on top of that: this enables memory mapped file IO as well, which wasn't enabled previously. This should help to reduce extraneous copies of the font in memory, have fewer open files and minimize the chances of racing with O_CLOEXEC.
2021-04-10 19:23:11 +03:00
[[package]]
name = "memmap2"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "397d1a6d6d0563c0f5462bbdae662cf6c784edf5e828e40c7257f85d82bf56dd"
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
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
[[package]]
name = "memoffset"
version = "0.5.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "043175f069eda7b85febe4a74abbaeff828d9f8b448515d3151a14a3542811aa"
dependencies = [
"autocfg",
]
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
[[package]]
name = "memoffset"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.6.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
2021-04-05 18:46:55 +03:00
checksum = "f83fb6581e8ed1f85fd45c116db8405483899489e38406156c25eb743554361d"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "metal"
version = "0.22.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1c12e48c737ee9a55e8bb2352bcde588f79ae308d3529ee888f7cc0f469b5777"
dependencies = [
"bitflags",
"block",
"cocoa-foundation",
"foreign-types",
"log",
"objc",
]
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
[[package]]
name = "metrics"
cargo update
2021-02-15 23:14:00 +03:00
version = "0.14.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
2021-02-15 23:14:00 +03:00
checksum = "58e285601dcfb9f3a8f37a7093b9956a0df730b50848c8ac0117406aff06c851"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
dependencies = [
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
"metrics-macros",
"proc-macro-hack",
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"
version = "0.2.0"
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 metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
checksum = "11ac60cd4d3a869fd39d57baf0ed7f79fb677580d8d6655c4330d4f1126bc27b"
dependencies = [
"lazy_static",
"proc-macro-hack",
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
"regex",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"syn",
deps: update metrics from 0.12 -> 0.14
2021-02-04 10:50:29 +03:00
]
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "miniz_oxide"
cargo update
2020-06-13 20:21:49 +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"
cargo update
2020-06-13 20:21:49 +03:00
checksum = "791daaae1ed6889560f8c4359194f56648355540573244a5448a83ba1ecc7435"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"adler32",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "mio"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.6.23"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "4afd66f5b91bf2a3bc13fad0e21caedac168ca4c707504e75585648ae80e4cc4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fuchsia-zircon",
"fuchsia-zircon-sys",
"iovec",
"kernel32-sys",
"libc",
"log",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"miow",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"net2",
"slab",
"winapi 0.2.8",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "mio-extras"
Update Cargo.lock
2019-12-30 00:43:59 +03:00
version = "2.0.6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "52403fe290012ce777c4626790c8951324a2b9e3316b3143779c72b029742f19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazycell",
"log",
"mio",
"slab",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "miow"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.2.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "ebd808424166322d4a38da87083bfddd3ac4c131334ed55856112eb06d46944d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"kernel32-sys",
"net2",
"winapi 0.2.8",
"ws2_32-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
[[package]]
name = "mlua"
cargo update
2021-04-26 18:34:45 +03:00
version = "0.5.4"
cargo update to pick up mlua 5.0.1 and the cross compilation fixes
2021-01-21 07:16:30 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-26 18:34:45 +03:00
checksum = "dd448d3e7018f2ff38dd732a374045f5b037eb4ee477d9241d9bb8c209528c1c"
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 = [
cargo update
2021-05-01 19:42:46 +03:00
"bstr 0.2.16",
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",
"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
"lua-src",
"luajit-src",
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
"num-traits 0.2.14",
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",
]
move mux to its own crate
2020-10-03 03:42:49 +03:00
[[package]]
name = "mux"
version = "0.1.0"
dependencies = [
"anyhow",
"async-trait",
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"bintree",
"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",
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",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"portable-pty",
"promise",
"rangeset",
"ratelim",
"regex",
"serde",
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",
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
"sysinfo",
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",
cargo update
2021-03-01 20:02:05 +03:00
"textwrap 0.13.4",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"thiserror",
tmux: attach control mode parser to terminal This causes `tmux -CC attach` to enter control mode and patch into the terminal, printing out parsed event messages. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 19:33:01 +03:00
"tmux-cc",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"unicode-segmentation",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"url",
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",
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "naga"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "a462414ac6a74a8fcc2c6d235d9a92b288f22682c016cf725e75d0c9470fb515"
dependencies = [
"bit-set",
"bitflags",
"codespan-reporting",
"fxhash",
"log",
"num-traits 0.2.14",
"petgraph",
"spirv_headers",
"thiserror",
]
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"
cargo update
2021-01-06 11:28:11 +03:00
version = "0.5.2"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-06 11:28:11 +03:00
checksum = "ac1378b66f7c93a1c0f8464a19bf47df8795083842e5090f4b7305973d5a22d0"
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 to pick up mlua 5.0.1 and the cross compilation fixes
2021-01-21 07:16:30 +03:00
"getrandom 0.2.2",
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
2020-09-09 19:31:37 +03:00
[[package]]
cargo update
2020-10-02 17:16:20 +03:00
name = "nb-connect"
cargo update
2021-05-01 19:42:46 +03:00
version = "1.2.0"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "b1bb540dc6ef51cfe1916ec038ce7a620daf3a111e2502d745197cd53d6bca15"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
cargo update
2020-10-02 17:16:20 +03:00
"libc",
cargo update
2021-02-15 23:14:00 +03:00
"socket2",
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 = "net2"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
version = "0.2.37"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
checksum = "391630d12b68002ae1e25e8f974306474966550ad82dac6886fb8910c19568ae"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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 = "nix"
version = "0.17.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "50e4785f2c3b7589a0d0c1dd60285e1188adac4006e8abd6dd578e1567027363"
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
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
"cc",
"cfg-if 0.1.10",
"libc",
"void",
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "nix"
version = "0.18.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "83450fe6a6142ddd95fb064b746083fc4ef1705fe81f64a64e1d4b39f54a1055"
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update
2020-09-09 19:31:37 +03:00
"cc",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update
2020-09-09 19:31:37 +03:00
"libc",
]
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500
2021-03-07 01:25:36 +03:00
[[package]]
name = "nix"
version = "0.19.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "b2ccba0cfe4fdf15982d1674c69b1fd80bad427d293849982668dfe454bd61f2"
dependencies = [
"bitflags",
"cc",
"cfg-if 1.0.0",
"libc",
]
cargo update
2021-03-01 20:02:05 +03:00
[[package]]
name = "nix"
version = "0.20.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "fa9b4819da1bc61c0ea48b63b7bc8604064dd43013e7cc325df098d49cd7c18a"
dependencies = [
"bitflags",
"cc",
"cfg-if 1.0.0",
"libc",
]
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",
]
[[package]]
name = "nom"
cargo update
2021-02-15 23:14:00 +03:00
version = "6.1.2"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-15 23:14:00 +03:00
checksum = "e7413f999671bd4745a7b624bd370a569fb6bc574b23c83a3c5ed2e453f3d5e2"
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 = [
"bitvec",
cargo update
2021-02-15 23:14:00 +03:00
"funty",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"lexical-core",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"version_check",
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 = "nonzero_ext"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "db1b4163932b207be6e3a06412aed4d84cca40dc087419f231b3a38cba2ca8e9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "notify"
cargo update
2021-04-19 19:23:33 +03:00
version = "4.0.16"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "2599080e87c9bd051ddb11b10074f4da7b1223298df65d4c2ec5bcf309af1533"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filetime",
"fsevent",
"fsevent-sys",
"inotify",
"libc",
"mio",
"mio-extras",
"walkdir",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
refine skip_close_confirmation_for_processes_named to look at proc tree That means that we won't be fooled by a shell with a backgrounded editor. refs: https://github.com/wez/wezterm/issues/562
2021-03-23 07:34:10 +03:00
[[package]]
name = "ntapi"
version = "0.3.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "3f6bb902e437b6d86e03cce10a7e2af662292c5dfef23b65899ea3ac9354ad44"
dependencies = [
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "num"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.3.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "8b7a8e9be5e039e2ff869df49155f1c06bd01ade2117ec783e56ab0932b67a8f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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-bigint",
"num-complex",
"num-integer",
"num-iter",
deps: misc updates
2020-12-29 20:21:50 +03:00
"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
"num-traits 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
]
[[package]]
name = "num-bigint"
cargo update
2021-03-08 10:18:21 +03:00
version = "0.3.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "7d0a3d5e207573f948a9e5376662aa743a2ea13f7c50a554d7af443a73fbfeba"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 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
]
[[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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 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
]
[[package]]
name = "num-derive"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.3.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "876a53fff98e03a936a674b29568b0e605f06b29372c2489ff4de23f1949743d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "num-integer"
cargo update 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.1.44"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "d2cc698a63b549a70bc047073d2949cce27cd1c7b0a4a862d08a8031bc2801db"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 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
]
[[package]]
name = "num-iter"
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.1.42"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "b2021c8337a54d21aca0d59a92577a029af9431cb59b909b03252b9c164fad59"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 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
]
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",
deps: misc updates
2020-12-29 20:21:50 +03:00
"num-bigint",
cargo update
2020-06-30 03:52:14 +03:00
"num-integer",
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
"num-traits 0.2.14",
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 = "num-traits"
version = "0.1.43"
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 = "92e5113e9fd4cc14ded8e499429f396a20f98c772a47cc8622a736e1ec843c31"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"num-traits 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
]
[[package]]
name = "num-traits"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.2.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "9a64b1ec5cda2586e284722486d802acf1f7dbdc623e2bfc57e65ca1cd099290"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2020-05-02 22:13:10 +03:00
version = "1.13.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-05-02 22:13:10 +03:00
checksum = "05499f3756671c15885fee9034446956fff3f243d6077b91e5767df161f766b3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hermit-abi",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[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",
add wgpu example
2021-05-06 19:04:16 +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
]
add wgpu example
2021-05-06 19:04:16 +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"
cargo update
2021-01-26 07:51:25 +03:00
version = "0.23.0"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-26 07:51:25 +03:00
checksum = "a9a7ab5d64814df0fe4a4b5ead45ed6c5f181ee3ff04ba344313a6c80446c5d4"
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 primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
version = "1.7.2"
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 primarily to pick up open 1.5.1
2021-03-03 18:28:35 +03:00
checksum = "af8b08b04175473088b46763e51ee54da5f9a164bc162f615b91bc179dbf15a3"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "opaque-debug"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2839e79665f131bdb5782e51f2c6c9599c133c6098982a54c794358bf432529c"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
[[package]]
name = "opaque-debug"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "624a8340c38c1b80fd549087862da4ba43e08858af025b236e509b6649fc13d5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "open"
cargo update
2021-04-19 19:23: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
2021-04-19 19:23:33 +03:00
checksum = "1711eb4b31ce4ad35b0f316d8dfba4fe5c7ad601c448446d84aae7a896627b20"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-03-01 20:02:05 +03:00
"which",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "openssl"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.10.34"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "6d7830286ad6a3973c0f1d9b73738f69c76b739301d0229c4b96501695cbe4c8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
build(deps): bump openssl from 0.10.30 to 0.10.31 Bumps [openssl](https://github.com/sfackler/rust-openssl) from 0.10.30 to 0.10.31. - [Release notes](https://github.com/sfackler/rust-openssl/releases) - [Commits](https://github.com/sfackler/rust-openssl/compare/openssl-v0.10.30...openssl-v0.10.31) Signed-off-by: dependabot[bot] <support@github.com>
2020-12-10 10:11:07 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"foreign-types",
"libc",
cargo update
2021-03-15 16:32:14 +03:00
"once_cell",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"openssl-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "openssl-src"
cargo update
2021-03-25 20:08:03 +03:00
version = "111.15.0+1.1.1k"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-25 20:08:03 +03:00
checksum = "b1a5f6ae2ac04393b217ea9f700cd04fa9bf3d93fae2872069f3d15d908af70a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.9.62"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "fa52160d45fa2e7608d504b7c3a3355afed615e6d8b627a74458634ba21b69bd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2021-05-03 19:34:29 +03:00
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"
cargo update
2021-05-03 19:34:29 +03:00
checksum = "b50b8919aecb97e5ee9aceef27e24f39c46b11831130f4a6b7b091ec5de0de12"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"num-traits 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
]
[[package]]
name = "output_vt100"
version = "0.1.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 = "53cdc5b785b7a58c5aad8216b3dfa114df64b0b06ae6e1501cef91df2fbdf8f9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
[[package]]
name = "owned_ttf_parser"
version = "0.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "9f923fb806c46266c02ab4a5b239735c144bdeda724a50ed058e5226f594cde3"
dependencies = [
fonts: remove ttf_parser, compute coverage from freetype Replaces the last usage of ttf-parser with calling into freetype. This removes a source of inconsistency, as ttf-parser doesn't support all of the things that freetype does. Notably, this prevents a weird error from blowing up codepoint coverage calculations on a system where I have helvetica.bdf in my font dir for long-forgotten reasons.
2021-04-08 19:12:59 +03:00
"ttf-parser",
window: update smithay-client-toolkit
2020-06-06 21:58: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 = "palette"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.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 to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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 = "a05c0334468e62a4dfbda34b29110aa7d70d58c7fdb2c9857b5874dd9827cc59"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"approx",
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
"num-traits 0.2.14",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"palette_derive",
"phf",
"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 = "palette_derive"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.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 to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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 = "0b4b5f600e60dd3a147fb57b4547033d382d1979eb087af310e91cb45a63b1f4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "parking"
version = "2.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "427c3892f9e783d91cc128285287e70a59e206ca452770ece88a76f7a3eddd72"
cargo update
2020-06-30 03:52:14 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "parking_lot"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f842b1982eb6c2fe34036a4fbfb06dd185a3f5c8edfaacdf7d1ea10b07de6252"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
"lock_api 0.3.4",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
"parking_lot_core 0.6.2",
fixup build to not consider termwiz tags as wezterm tags CI got broken by the termwiz release. This commit teaches the various `git describe --tags` calls to filter to the wezterm tags which all start with the year. We're match `20*` which should be good for the next 79 years. I've removed the vergen dependency as there was no way to teach it to do the equivalent matching, and it wasn't a terrible burden to just inline the git describe call anyway.
2021-03-18 07:02:03 +03:00
"rustc_version",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
version = "0.11.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"
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
checksum = "6d7744ac029df22dca6284efe4e898991d28e3085c706c972bcd7da4a27a15eb"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
dependencies = [
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
"instant",
cargo update
2021-05-01 19:42:46 +03:00
"lock_api 0.4.4",
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
"parking_lot_core 0.8.3",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "parking_lot_core"
version = "0.6.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "b876b1b9e7ac6e1a74a6da34d25c42e17e8862aa409cbbbdcfc8d86c6f3bc62b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 0.1.10",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cloudabi",
"libc",
cargo update
2021-01-11 19:43:32 +03:00
"redox_syscall 0.1.57",
fixup build to not consider termwiz tags as wezterm tags CI got broken by the termwiz release. This commit teaches the various `git describe --tags` calls to filter to the wezterm tags which all start with the year. We're match `20*` which should be good for the next 79 years. I've removed the vergen dependency as there was no way to teach it to do the equivalent matching, and it wasn't a terrible burden to just inline the git describe call anyway.
2021-03-18 07:02:03 +03:00
"rustc_version",
cargo update
2021-01-11 19:43:32 +03:00
"smallvec 0.6.14",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
[[package]]
name = "parking_lot_core"
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
version = "0.8.3"
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"
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
checksum = "fa7a782938e745763fe6907fc6ba86946d72f49fe7e21de074e08128a99fb018"
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
dependencies = [
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
"cfg-if 1.0.0",
"instant",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
"libc",
cargo update
2021-05-01 19:42:46 +03:00
"redox_syscall 0.2.7",
cargo update
2021-01-11 19:43:32 +03:00
"smallvec 1.6.1",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
]
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
2021-02-15 23:14:00 +03:00
version = "0.8.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
2021-02-15 23:14:00 +03:00
checksum = "fd56cbd21fea48d0c440b41cd69c589faacade08c992d9a54e471b79d0fd13eb"
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
mux: upgrade rcgen This version no longer generates invalid CA certificates and allows TLS connections using the internal PKI to advance further. Still need to debug an early disconnect.
2020-10-04 20:05:31 +03:00
"once_cell",
"regex",
]
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "percent-encoding"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d4fd5641d01c8f18a23da7b6fe29298ff4b55afcccdf78973b24cf3175fee32e"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "pest"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "10f4872ae94d7b90ae48754df22fd42ad52ce740b8f370b03da4835417403e53"
dependencies = [
"ucd-trie",
]
[[package]]
name = "pest_derive"
version = "2.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "833d1ae558dc601e9a60366421196a8d94bc0ac980476d0b67e1d0988d72b2d0"
dependencies = [
"pest",
"pest_generator",
]
[[package]]
name = "pest_generator"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "99b8db626e31e5b81787b9783425769681b347011cc59471e33ea46d2ea0cf55"
dependencies = [
"pest",
"pest_meta",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
]
[[package]]
name = "pest_meta"
version = "2.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "54be6e404f5317079812fc8f9f5279de376d8856929e21c184ecf6bbd692a11d"
dependencies = [
"maplit",
"pest",
"sha-1",
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "petgraph"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "467d164a6de56270bd7c4d070df81d07beace25012d5103ced4e9ff08d6afdb7"
dependencies = [
"fixedbitset",
"indexmap",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "phf"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "3dfb61232e34fcb633f43d12c58f83c1df82962dcdfa565a4e866ffc17dafe12"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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_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 = "phf_codegen"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "cbffee61585b0411840d3ece935cce9cb6321f01c45477d30066498cd5e1a815"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"phf_generator",
"phf_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 = "phf_generator"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "17367f0cc86f2d25802b2c26ee58a7b23faeccf78a396094c13dced0d0182526"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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_shared",
"rand 0.7.3",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "phf_shared"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "c00cf8b9eafe68dde5e9eaa2cef8ee84a9336a47d566ec55ca16589633b65af7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"siphasher",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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
2021-04-19 19:23:33 +03:00
version = "1.0.7"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "c7509cc106041c40a4518d2af7a61530e1eed0e6285296a3d8c5472806ccc4a4"
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
2021-04-19 19:23:33 +03:00
version = "1.0.7"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "48c950132583b500556b1efd71d45b319029f2b71518d979fcc208e16b42426f"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
]
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
[[package]]
name = "pin-project-lite"
cargo update
2021-03-08 10:18:21 +03:00
version = "0.2.6"
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
2021-03-08 10:18:21 +03:00
checksum = "dc0e1f259c92177c30a4c9d177246edd0a3568b25756a977d0632cf8fa37e905"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
[[package]]
name = "pin-utils"
cargo update
2020-05-02 22:13:10 +03:00
version = "0.1.0"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-02 22:13:10 +03:00
checksum = "8b870d8c151b6f2fb93e84a13146138f05d02ed11c7e7c54f8826aaaf7c9f184"
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "pkg-config"
cargo update 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.19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "3831453b3449ceb48b6d9c7ad7c96d5ea673e9b470a1dc578c2ce6521230884c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "png"
cargo update (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
version = "0.16.8"
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 (this will probably annoy dependabot)
2020-12-10 00:58:44 +03:00
checksum = "3c3287920cb847dee3de33d301c463fba14dda99db24214ddf93f83d3021f4c6"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
"crc32fast",
cargo update
2020-06-13 20:21:49 +03:00
"deflate",
cargo update
2020-06-30 03:52:14 +03:00
"miniz_oxide 0.3.7",
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
]
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "polling"
cargo update
2021-03-22 06:18:02 +03:00
version = "2.0.3"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-22 06:18:02 +03:00
checksum = "4fc12d774e799ee9ebae13f4076ca003b40d18a11ac0f3641e6f899618580b7b"
cargo update
2020-09-09 19:31:37 +03:00
dependencies = [
cargo update
2021-03-22 06:18:02 +03:00
"cfg-if 1.0.0",
cargo update
2020-09-09 19:31:37 +03:00
"libc",
"log",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"wepoll-sys",
cargo update
2020-09-09 19:31:37 +03:00
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "portable-pty"
prep for pty 0.4 release
2021-04-30 20:17:25 +03:00
version = "0.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
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filedescriptor",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
"futures",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
"log",
"serde",
"serde_derive",
"serial",
"shared_library",
"shell-words",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
"smol",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"ssh2",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.2.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "ac74c624d6b2d21f425f752262f42188365d7b8ff1aff74c82e45136510a4857"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "pretty_assertions"
version = "0.6.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 = "3f81e1644e1b54f5a68959a29aa86cde704219254669da328ecfdf6a1f09d427"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"ansi_term",
"ctor",
"difference",
"output_vt100",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 timestamps in the logger
2020-02-14 20:46:19 +03:00
[[package]]
name = "pretty_env_logger"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "926d36b9553851b8b0005f1275891b392ee4d2d833852c417ed025477350fb9d"
dependencies = [
cargo update
2020-06-13 20:21:49 +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
"log",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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 = "proc-macro-crate"
version = "0.1.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1d6ea3c4595b96363c13943497db34af4460fb474a95c43f4446ad341b8c9785"
dependencies = [
"toml",
]
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
[[package]]
name = "proc-macro-error"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.0.4"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "da25490ff9892aab3fcf7c36f08cfb902dd3e71ca0f9f9517bea02a73a5ce38c"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
dependencies = [
"proc-macro-error-attr",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"version_check",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
]
[[package]]
name = "proc-macro-error-attr"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.0.4"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "a1be40180e52ecc98ad80b184934baf3d0d29f979574e439af5a55274b35f869"
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"version_check",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
]
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
[[package]]
name = "proc-macro-hack"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "0.5.19"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "dbf0c48bc1d91375ae5c3cd81e3722dff1abcf81a30960240640d223f59fe0e5"
switch most of the rest of the mux over to the new model This mostly works, but has a cache invalidation issue wrt. passing invalidated rows from the server to the client... sometimes. However, scrollback is cached on demand and selection works.
2020-01-05 10:25:49 +03:00
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "proc-macro-nested"
cargo update
2021-01-18 10:38:11 +03:00
version = "0.1.7"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-18 10:38:11 +03:00
checksum = "bc881b2c22681370c6a780e47af9840ef841837bc98118431d4e1868bd0c1086"
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 = "proc-macro2"
cargo update
2021-04-05 18:46:55 +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
2021-04-05 18:46:55 +03:00
checksum = "a152013215dca273577e18d2bf00fa862b89b24169fb78c4c95aeb07992c9cec"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"unicode-xid",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "profiling"
version = "1.0.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c3a66d5e88679f2720126c11ee29da07a08f094eac52306b066edd7d393752d6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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",
migrate some more code to the newer spawn mechanism
2020-01-16 20:15:07 +03:00
"async-std",
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
"flume",
move spawn_task into a new promise::spawn module
2020-01-16 14:39:44 +03:00
"lazy_static",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"thiserror",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
[[package]]
name = "pulldown-cmark"
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
version = "0.8.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
source = "registry+https://github.com/rust-lang/crates.io-index"
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
checksum = "ffade02495f22453cd593159ea2f59827aae7f53fa8323f756799b670881dcf8"
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
"getopts",
"memchr",
"unicase",
]
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
[[package]]
name = "pure-rust-locales"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.5.6"
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-05 18:46:55 +03:00
checksum = "b45c49fc4f91f35bae654f85ebb3a44d60ac64f11b3166ffa609def390c732d8"
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500
2021-03-02 20:51:56 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "quick-error"
bump some versions
2020-01-10 09:39:34 +03:00
version = "1.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"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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 = "a1d01941d82fa2ab50be1e79e6714289dd7cde78eba4c074bc5a4374f650dfe0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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"
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
version = "1.0.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"
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
checksum = "c3d0b9745dc2debf507c8422de05d7226cc1f0644216dfdfead988f9b1ab32a7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
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 = "radium"
version = "0.5.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "941ba9d78d8e2f7ce474c015eea4d9c6d25b6a3327f9832ee29a4de27f91bbb8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rand"
version = "0.4.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "552840b97013b1a26992c11eac34bdd778e464601a4c2054b5f0bff7c6761293"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fuchsia-cprng",
"libc",
"rand_core 0.3.1",
"rdrand",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
version = "0.7.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "6a6b1679d49b24bbfe0c803429aa1874472f50d9b363131f0e89fc356b544d03"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"getrandom 0.1.16",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"rand_chacha",
"rand_core 0.5.1",
"rand_hc",
"rand_pcg",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand_chacha"
cargo update
2020-03-14 19:39:38 +03:00
version = "0.2.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-03-14 19:39:38 +03:00
checksum = "f4c8ed856279c9737206bf725bf36935d8666ead7aa69b52be55af369d193402"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-03-14 19:39:38 +03:00
"ppv-lite86",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.5.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand_core"
version = "0.3.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "7a6fdeb83b075e8266dcc8762c22776f6877a63111121f5f8c7411e5be7eed4b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.4.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand_core"
version = "0.4.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "9c33a3c44ca05fa6f1807d8e6743f3824e8509beca625669633be0acbdf509dc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rand_core"
version = "0.5.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "90bde5296fc891b0cef12a6d03ddccc162ce7b2aff54160af9338f8d40df6d19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"getrandom 0.1.16",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand_hc"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "ca3129af7b92a17112d59ad498c6f81eaf463253766b90396d39ea7a39d6613c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.5.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rand_pcg"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.2.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "16abd0c1b639e9eb4d7c50c0b8100b0d0f849be2349829c740fe8e6eb4816429"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.5.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "range-alloc"
version = "0.1.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "63e935c45e09cc6dcf00d2f0b2d630a58f4095320223d47fc68918722f0538b6"
add RangeSet type The idea is to use this to maintain a set of dirty StableRowIndex values for the mux rpc.
2020-01-05 05:10:53 +03:00
[[package]]
name = "rangeset"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
add RangeSet type The idea is to use this to maintain a set of dirty StableRowIndex values for the mux rpc.
2020-01-05 05:10:53 +03:00
]
move ratelim to its own crate
2020-10-03 03:31:39 +03:00
[[package]]
name = "ratelim"
version = "0.1.0"
dependencies = [
"config",
"ratelimit_meter",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ratelimit_meter"
version = "5.0.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "a37d4f95369ef809d01448bdf8d82ef974e3b21f3698d87015a575bb26f27724"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"evmap",
"nonzero_ext",
deps: update to ssh2 0.7.0
2020-01-25 04:49:37 +03:00
"parking_lot 0.9.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add raw-window-handle impls
2021-05-06 08:59:52 +03:00
[[package]]
name = "raw-window-handle"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "0a441a7a6c80ad6473bd4b74ec1c9a4c951794285bf941c2126f607c72e48211"
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 = "rayon"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.5.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "8b0d8e0819fadc20c74ea8373106ead0600e3a67ef1fe8da56e39b9ae7275674"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
Update lru -> 0.6
2020-12-10 01:04:56 +03:00
"autocfg",
deps: misc updates
2020-12-29 20:21:50 +03:00
"crossbeam-deque",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"either",
"rayon-core",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "rayon-core"
cargo update 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.9.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "9ab346ac5921dc62ffa9f89b7a773907511cdfa5490c572ae9be1be33e8afa4a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"lazy_static",
"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
2021-05-01 19:42:46 +03:00
version = "0.8.11"
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
2021-05-01 19:42:46 +03:00
checksum = "48b4fc1b81d685fcd442a86da2e2c829d9e353142633a8159f42bf28e7e94428"
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 = [
"chrono",
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",
"yasna",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rdrand"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "678054eb77286b51581ba43620cc911abf02758c91f93f479767aed0f90458b2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand_core 0.3.1",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "redox_syscall"
cargo update
2020-09-09 19:31:37 +03:00
version = "0.1.57"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "41cc0f7e4d5d4544e8861606a285bb08d3e70712ccc7d2b84d7c0ccfaf4b05ce"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2021-01-11 19:43:32 +03:00
[[package]]
name = "redox_syscall"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.2.7"
cargo update
2021-01-11 19:43:32 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "85dd92e586f7355c633911e11f77f3d12f04b1b1bd76a198bd34ae3af8341ef2"
cargo update
2021-01-11 19:43:32 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update
2021-01-11 19:43:32 +03:00
]
[[package]]
name = "redox_users"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "528532f3d801c87aec9def2add9ca802fe569e44a544afe633765267840abe64"
dependencies = [
cargo update to pick up mlua 5.0.1 and the cross compilation fixes
2021-01-21 07:16:30 +03:00
"getrandom 0.2.2",
cargo update
2021-05-01 19:42:46 +03:00
"redox_syscall 0.2.7",
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
2021-05-03 19:34:29 +03:00
version = "1.5.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-03 19:34:29 +03:00
checksum = "ce5f1ceb7f74abbce32601642fcf8e8508a8a8991e0621c7d750295b9095702b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2020-03-14 19:39:38 +03:00
version = "0.1.9"
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
2020-03-14 19:39:38 +03:00
checksum = "ae1ded71d66a4a97f5e961fd0cb25a5f366a42a41570d16a763a69c092c26ae4"
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
dependencies = [
"byteorder",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "regex-syntax"
cargo update
2021-05-03 19:34:29 +03:00
version = "0.6.25"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-03 19:34:29 +03:00
checksum = "f497285884f3fcff424ffc933e56d7cbca511def0c9831a7f9b5f6153e3cc89b"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "remove_dir_all"
cargo update
2020-06-13 20:21:49 +03:00
version = "0.5.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-13 20:21:49 +03:00
checksum = "3acd125665422973a33ac9d3dd2df85edad0f4ae9b00dafb1a05e43a9f5ef8e7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
[[package]]
name = "rental"
cargo update
2021-05-03 19:34:29 +03:00
version = "0.5.6"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-03 19:34:29 +03:00
checksum = "cc89fe2acac36d212474d138aaf939c04a82df5b61d07011571ebce5aef81f2e"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
dependencies = [
"rental-impl",
"stable_deref_trait",
]
[[package]]
name = "rental-impl"
version = "0.5.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "475e68978dc5b743f2f40d8e0a8fdc83f1c5e78cbf4b8fa5e74e73beebc340de"
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "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"
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
version = "0.8.27"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
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
checksum = "8fddb3b23626145d1776addfc307e1a1851f60ef6ca64f376bcb889697144cf0"
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",
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
"spin",
"untrusted",
"web-sys",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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-05-03 19:34:29 +03:00
version = "0.1.19"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-03 19:34:29 +03:00
checksum = "410f7acf3cb3a44527c5d9546bad4bf4e6c460915d5f9f2fc524498bfe8f70ce"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
[[package]]
name = "rustc-hash"
version = "1.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "08d43f7aa6b08d49f382cde6a7982047c3426db949b1424bc4b7ec9ae12c6ce2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rustc_version"
version = "0.2.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "138e3e0acb6c9fb258b19b67cb8abd63c00679d2851805ea151465464fe9030a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"semver 0.9.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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 = "rustls"
cargo update
2021-04-19 19:23:33 +03:00
version = "0.19.1"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "35edb675feee39aec9c99fa5ff985081995a06d594114ae14cbe797ad7b7a6d7"
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 = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
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
"log",
"ring",
"sct",
"webpki",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "rusttype"
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
version = "0.9.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"
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
checksum = "dc7c727aded0be18c5b80c1640eae0ac8e396abf6fa8477d96cb37d18ee5ec59"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = [
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
"ab_glyph_rasterizer",
"owned_ttf_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
]
bump some versions
2020-01-10 09:39:34 +03:00
[[package]]
name = "ryu"
cargo update
2020-06-06 20:08:02 +03:00
version = "1.0.5"
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-06 20:08:02 +03:00
checksum = "71d301d4193d031abdd79ff7e3dd721168a9572ef3fe51a1517aba235bd8f86e"
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 = "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
]
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
cargo update
2020-06-30 03:52:14 +03:00
name = "scoped-tls"
version = "1.0.0"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "ea6a9290e3c9cf0f18145ef7ffa62d68ee0bf5fcd651017e586dc7fd5da448c2"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "scoped_threadpool"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "1d51f5df5af43ab3f1360b429fa5e0152ac5ce8c0bd6485cae490332e96846a8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "scopeguard"
cargo update
2020-03-14 19:39:38 +03:00
version = "1.1.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-03-14 19:39:38 +03:00
checksum = "d29ab0c6d3fc0ee92fe66e2d99f700eab17a8d57d1c1d3b748380fb20baa78cd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "sct"
cargo update
2021-04-12 17:54:46 +03:00
version = "0.6.1"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "b362b83898e0e69f38515b82ee15aa80636befe47c3b6d3d89a911e78fc228ce"
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 = [
"ring",
"untrusted",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "semver"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "1d7eb9ef2c18661902cc47e535f9bc51b78acd254da71d375c2f6720d9a40403"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"semver-parser 0.7.0",
]
[[package]]
name = "semver"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f301af10236f6df4160f7c3f04eec6dbc70ace82d23326abad5edee88801c6b6"
dependencies = [
cargo update
2021-01-06 11:28:11 +03:00
"semver-parser 0.10.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "semver-parser"
version = "0.7.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "388a1df253eca08550bef6c72392cfe7c30914bf41df5269b68cbd6ff8f570a3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
deps: misc updates
2020-12-29 20:21:50 +03:00
[[package]]
name = "semver-parser"
cargo update
2021-01-06 11:28:11 +03:00
version = "0.10.2"
deps: misc updates
2020-12-29 20:21:50 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-06 11:28:11 +03:00
checksum = "00b0bef5b7f9e0df16536d3961cfb6e84331c065b4066afb39768d0e319411f7"
deps: misc updates
2020-12-29 20:21:50 +03:00
dependencies = [
"pest",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "serde"
cargo update
2021-03-25 20:08:03 +03:00
version = "1.0.125"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-25 20:08:03 +03:00
checksum = "558dc50e1a5a5fa7112ca2ce4effcb321b0300c0d4ccf0776a9f60cd89031171"
serde_derive -> serde with derive feature
2020-01-03 20:22:17 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serde_derive",
serde_derive -> serde with derive feature
2020-01-03 20:22:17 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "serde_derive"
cargo update
2021-03-25 20:08:03 +03:00
version = "1.0.125"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-25 20:08:03 +03:00
checksum = "b093b7a2bb58203b5da3056c05b4ec1fed827dcfdb37347a8841695263b3d06d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "serde_json"
cargo update
2021-03-01 20:02:05 +03:00
version = "1.0.64"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-01 20:02:05 +03:00
checksum = "799e97dc9fdae36a5c8b8f2cae9ce2ee9fdce2058c57a93e6099d919fd982f79"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
dependencies = [
"itoa",
"ryu",
"serde",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "serde_repr"
version = "0.1.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "2dc6b7951b17b051f3210b063f12cc17320e2fe30ae05b0fe2a3abb068551c76"
dependencies = [
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "serial"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "a1237a96570fc377c13baa1b88c7589ab66edced652e43ffb17088f003db3e86"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serial-core",
"serial-unix",
"serial-windows",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "serial-core"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "3f46209b345401737ae2125fe5b19a77acce90cd53e1658cda928e4fe9a64581"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "serial-unix"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "f03fbca4c9d866e24a459cbca71283f545a37f8e3e002ad8c70593871453cab7"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"ioctl-rs",
"libc",
"serial-core",
"termios 0.2.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "serial-windows"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "15c6d3b776267a75d31bbdfd5d36c0ca051251caafc285827052bc53bcdc8162"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"serial-core",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "sha-1"
version = "0.8.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f7d94d0bede923b3cea61f3f1ff57ff8cdfd77b400fb8f9998949e0cf04163df"
dependencies = [
"block-buffer 0.7.3",
"digest 0.8.1",
"fake-simd",
"opaque-debug 0.2.3",
]
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
2021-02-01 18:54:01 +03:00
version = "0.9.3"
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
2021-02-01 18:54:01 +03:00
checksum = "fa827a14b29ab7f44778d14a88d3cb76e949c45083f7dbfa507d0cb699dc12de"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
dependencies = [
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
"block-buffer 0.9.0",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
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
"cpuid-bool",
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
"digest 0.9.0",
"opaque-debug 0.3.0",
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "shared_library"
version = "0.1.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "5a9e7e0f2bfae24d8a5b5a66c5b257a83c7412304311512a0c054cd5e619da11"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "shell-words"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "1.0.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "b6fa3938c99da4914afedd13bf3d79bcb6c277d1b2c398d23257a304d9e1b074"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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
2021-04-05 18:46:55 +03:00
version = "0.3.8"
cargo update
2021-02-08 09:51:28 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-05 18:46:55 +03:00
checksum = "ef33d6d0cd06e0840fba9985aab098c147e67e05cee14d412d3345ed14ff30ac"
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
2020-12-28 19:23:20 +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-12-28 19:23:20 +03:00
checksum = "16f1d0fef1604ba8f7a073c7e701f213e056707210e9020af4528e0101ce11a6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "siphasher"
cargo update
2021-03-22 06:18:02 +03:00
version = "0.3.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-22 06:18:02 +03:00
checksum = "cbce6d4507c7e4a3962091436e56e95290cb71fa302d0d270e32130b75fbff27"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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
2021-04-26 18:34:45 +03:00
version = "0.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-04-26 18:34:45 +03:00
checksum = "f173ac3d1a7e3b28003f40de0b5ce7fe2710f9b9dc3fc38664cebee46b3b6527"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "slotmap"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "c46a3482db8f247956e464d783693ece164ca056e6e67563ee5505bdb86452cd"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "smallvec"
cargo update
2021-01-11 19:43:32 +03:00
version = "0.6.14"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-11 19:43:32 +03:00
checksum = "b97fcaeba89edba30f044a10c6a3cc39df9c3f17d7cd829dd1446cab35f890e0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"maybe-uninit",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "smallvec"
cargo update
2021-01-11 19:43:32 +03:00
version = "1.6.1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-11 19:43:32 +03:00
checksum = "fe0f37c9e8f3c5a4a66ad655a93c74daac4ad00c441533bf5c6e7990bb42604e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
textwrap -> 0.13
2020-12-10 01:07:35 +03:00
[[package]]
name = "smawk"
cargo update
2021-02-01 18:54:01 +03:00
version = "0.3.1"
textwrap -> 0.13
2020-12-10 01:07:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-01 18:54:01 +03:00
checksum = "f67ad224767faa3c7d8b6d91985b78e70a1324408abcb1cfcc2be4c06bc06043"
textwrap -> 0.13
2020-12-10 01:07:35 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "smithay-client-toolkit"
cargo update
2021-03-08 10:18:21 +03:00
version = "0.12.3"
window: update smithay-client-toolkit However, I'm not able to create wayland windows any more on my nvidia system (either with or without this change). I don't know if this is specific to my nvidia drivers or something else :-/ refs: https://github.com/wez/wezterm/issues/476
2020-12-30 22:09:21 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "4750c76fd5d3ac95fa3ed80fe667d6a3d8590a960e5b575b98eea93339a80b80"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
"andrew",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
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
"calloop",
cargo update
2021-03-01 20:02:05 +03:00
"dlib 0.4.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
"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",
fonts: add custom freetype stream impl The intent is to reveal more context on what's happening in https://github.com/wez/wezterm/issues/671 As a nice side benefit, this avoids the potential inability to open paths that are not utf8 or representable as c-strings on Windows. And on top of that: this enables memory mapped file IO as well, which wasn't enabled previously. This should help to reduce extraneous copies of the font in memory, have fewer open files and minimize the chances of racing with O_CLOEXEC.
2021-04-10 19:23:11 +03:00
"memmap2 0.1.0",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"nix 0.18.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
"wayland-client",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"wayland-cursor",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-protocols",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
name = "smol"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
version = "1.2.5"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "85cf3b5351f3e783c1d79ab5fc604eeed8b8ae9abd36b166e8b87a089efd85e4"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
"async-channel",
"async-executor",
"async-fs",
"async-io",
"async-lock",
"async-net",
"async-process",
"blocking",
"futures-lite",
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
"once_cell",
]
cargo update
2021-02-15 23:14:00 +03:00
[[package]]
name = "socket2"
cargo update
2021-03-22 06:18:02 +03:00
version = "0.4.0"
cargo update
2021-02-15 23:14:00 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-22 06:18:02 +03:00
checksum = "9e3dfc207c526015c632472a77be09cf1b6e46866581aecae5cc38fb4235dea2"
cargo update
2021-02-15 23:14:00 +03:00
dependencies = [
"libc",
"winapi 0.3.9",
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[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]]
name = "spinning_top"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.2.3"
fix clipboard on x11 This was broken by the changes in aad493ab2a121fab7678b3a528091734bdbf69bb. The issue was that the channel send didn't wakeup the receiver. I'm not sure why, and I tried a couple of different async channel implementation. Doing the simplistic solution here works reliably.
2020-10-09 21:07:18 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-05 18:46:55 +03:00
checksum = "8bd0ab6b8c375d2d963503b90d3770010d95bc3b5f98036f948dee24bf4e8879"
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
2021-05-01 19:42:46 +03:00
"lock_api 0.4.4",
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
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "spirv_cross"
version = "0.23.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "60647fadbf83c4a72f0d7ea67a7ca3a81835cf442b8deae5c134c3e0055b2e14"
dependencies = [
"cc",
"js-sys",
"wasm-bindgen",
]
[[package]]
name = "spirv_headers"
version = "1.5.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1f5b132530b1ac069df335577e3581765995cba5a13995cdbbdbc8fb057c532c"
dependencies = [
"bitflags",
"num-traits 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
[[package]]
name = "ssh2"
cargo update
2021-02-04 10:28:23 +03:00
version = "0.9.1"
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
source = "git+https://github.com/wez/ssh2-rs.git?branch=win32ssl#c65067040c97a0cf7f96c69d6fc87764a32c34ae"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"libssh2-sys",
ssh2: on windows, link against openssl The wincng based build doesn't recognize newer keys which makes it impossible to connect to a reasonably up to date Fedora installation. This commit points to my branch of ssh2-rs that has some changes to build ssh2 against the vendored openssl that is already part of the dependency graph for wezterm. refs: https://github.com/wez/wezterm/issues/507
2021-03-26 20:00:43 +03:00
"parking_lot 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
]
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
[[package]]
name = "stable_deref_trait"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.2.0"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "a8f112729512f8e442d81f95a8a7ddf2b7c6b8a1a6f509a95864142b30cab2d3"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +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"
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "storage-map"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "418bb14643aa55a7841d5303f72cf512cfb323b8cc221d51580500a1ca75206c"
dependencies = [
"lock_api 0.4.4",
]
move strip-ansi-escapes into its own crate
2020-10-03 09:54:54 +03:00
[[package]]
name = "strip-ansi-escapes"
version = "0.1.0"
dependencies = [
"structopt",
"termwiz",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "strsim"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "8ea5119cdb4c55b55d432abb513a0429384878c15dde60cc77b1c99de1a95a6a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
lua: give a nice error message when using an invalid field name Make a reasonable suggestion to the user based on similarity with possible field names, but don't error out. This facilitates evolving the configuration over time, and makes the config more forgiving of typos.
2020-03-01 20:39:14 +03:00
[[package]]
name = "strsim"
version = "0.10.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "structopt"
cargo update 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.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "5277acd7ee46e63e5168a80734c9f6ee81b1367a7d8772a2d765df2a3705d28c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"clap",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
"lazy_static",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"structopt-derive",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "structopt-derive"
cargo update 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.4.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "5ba9cdfda491b814720b6b06e0cac513d922fc407582032e8706e9f137976f90"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"heck",
Update structopt to 0.3
2020-01-10 10:48:33 +03:00
"proc-macro-error",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
[[package]]
name = "svg_fmt"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "8fb1df15f412ee2e9dfc1c504260fa695c1c3f10fe9f4a6ee2d2184d7d6450e2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "syn"
cargo update
2021-05-01 19:42:46 +03:00
version = "1.0.71"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "ad184cc9470f9117b2ac6817bfe297307418819ba40552f9b3846f05c33d5373"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"unicode-xid",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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 = "sysinfo"
version = "0.16.5"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "567e910ef0207be81a4e1bb0491e9a8d9866cf45b20fe1a52c03d347da9ea51b"
dependencies = [
"cfg-if 1.0.0",
"core-foundation-sys 0.8.2",
"doc-comment",
"libc",
"ntapi",
"once_cell",
"rayon",
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "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
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 = "tap"
cargo update
2021-02-15 23:14:00 +03:00
version = "1.0.1"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-15 23:14:00 +03:00
checksum = "55937e1799185b12863d447f42597ed69d9928686b8d88a1df17376a097d8369"
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
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "tempdir"
version = "0.3.7"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "15f2b5fb00ccdf689e0149d1b1b3c03fead81c2b37735d812fa8bddbbf41b6d8"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rand 0.4.6",
"remove_dir_all",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm: add ScrollToPrompt key assignment Adds some supporting methods for computing the `SemanticZone`s in the display and a key assignment that allows scrolling the viewport to jump to the next/prev Prompt zone.
2020-11-08 20:58:02 +03:00
[[package]]
name = "term_size"
version = "0.3.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "1e4129646ca0ed8f45d09b929036bafad5377103edd06e50bf574b353d2b08d9"
dependencies = [
"libc",
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "termcolor"
cargo update 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.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "2dfed899f0eb03f32ee8c6a0aabdb8a7949659e3466561fc0adf54e26d88c5f4"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi-util",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "terminfo"
cargo update
2020-05-26 08:25:39 +03:00
version = "0.7.3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-26 08:25:39 +03:00
checksum = "76971977e6121664ec1b960d1313aacfa75642adc93b9d4d53b247bd4cb1747e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"dirs",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fnv",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"nom 5.1.2",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
"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
]
[[package]]
name = "termwiz"
vtparse/termwiz: prep for release
2021-04-14 22:59:26 +03:00
version = "0.13.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
deps: misc updates
2020-12-29 20:21:50 +03:00
"base64",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cassowary",
fix one 32-bit build issue refs: #474
2021-02-12 19:35:00 +03:00
"cfg-if 1.0.0",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filedescriptor",
"fnv",
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",
"num-derive",
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
"num-traits 0.2.14",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
termwiz: fix hyperlink matching issue with double wide chars refs: https://github.com/wez/wezterm/issues/221
2020-06-18 19:46:03 +03:00
"pretty_assertions",
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
2021-02-08 09:51:28 +03:00
"signal-hook 0.1.17",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"terminfo",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"termios 0.3.3",
termwiz: Remove anyhow::Result from public API It's been replaced with an opaque termwiz error type instead. This is a bit of a more conservative approach than that in (refs: #407) and has less of an impact on the surrounding code, which appeals to me from a maintenance perspective. refs: #406 refs: #407
2021-01-08 11:21:54 +03:00
"thiserror",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
"unicode-width",
"varbincode",
"vtparse",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"xi-unicode",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "textwrap"
version = "0.11.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d326610f408c7a4eb6f51c37c330e496b08506c9457c9d34287ecc38809fb060"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"unicode-width",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
[[package]]
name = "textwrap"
cargo update
2021-03-01 20:02:05 +03:00
version = "0.13.4"
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-01 20:02:05 +03:00
checksum = "cd05616119e612a8041ef58f2b578906cc2531a6069047ae092cfb86a325d835"
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",
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
2021-02-22 11:09:01 +03:00
version = "1.0.24"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-22 11:09:01 +03:00
checksum = "e0f4a65597094d4483ddaed134f409b2cb7c1beccf25201a9f73c719254fa98e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2021-02-22 11:09:01 +03:00
version = "1.0.24"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-22 11:09:01 +03:00
checksum = "7765189610d8241a44529806d6fd1f2e0a08734313a35d5b3a556f92b381f3c0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "thunderdome"
version = "0.4.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "87b4947742c93ece24a0032141d9caa3d853752e694a57e35029dd2bd08673e0"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
[[package]]
name = "tiff"
deps: cargo update
2020-12-14 19:50:45 +03:00
version = "0.6.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"
deps: cargo update
2020-12-14 19:50:45 +03:00
checksum = "9a53f4706d65497df0c4349241deddf35f84cee19c87ed86ea8ca590f4464437"
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +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
"jpeg-decoder",
cargo update
2021-03-01 20:02:05 +03:00
"miniz_oxide 0.4.4",
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"weezl",
wezterm: sixel rendering basically working refs: https://github.com/wez/wezterm/issues/217
2020-06-11 17:45:10 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "time"
cargo update
2021-01-11 19:43:32 +03:00
version = "0.1.43"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-01-11 19:43:32 +03:00
checksum = "ca8a50ef2360fbd1eeb0ecd46795a87a19024eb4b53c5dc916ca1fd95fe62438"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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
2021-04-05 18:46:55 +03:00
version = "1.2.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
2021-04-05 18:46:55 +03:00
checksum = "5b5220f05bb7de7f3f53c7c065e1199b3172696fe2db9f9c4d8ad9b4ee74c342"
wezterm: update allsorts shaper The current master of allsorts supports color fonts in both bitmap and svg varieties. I'm interested to see if I can teach wezterm to render the svg based variety in a subsequent diff. First though, it's times to dust off our allsorts shaper logic. This commit updates to point to the current master of allsorts at the time of writing; there's a little bit of API fanout that makes it a bit easier to manage font fallback. The fallback logic has been improved so that we can now successfully fall back to the emoji font. The shaping logic has been improved so that we turn on the options that enable ZWJ for combining sequences of emoji, such as "man health worker". Running with the allsorts shaper enabled produces generally superior emoji/ligature substitution results compared to harfbuzz with Noto Color Emoji; the "man health worker" and the flags (eg: `flag: England`) from the subdivsion-flag section don't get substituted at all with harfbuzz, but do produce appropriate glyphs with allsorts. refs: https://github.com/wez/wezterm/issues/66
2020-11-21 03:56:07 +03:00
dependencies = [
"tinyvec_macros",
]
[[package]]
name = "tinyvec_macros"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "cda74da7e1a664f795bb1f8a87ec406fb89a02522cf6e50620d016add6dbbf5c"
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 = "tmux-cc"
version = "0.1.0"
dependencies = [
"anyhow",
"log",
"pest",
"pest_derive",
"pretty_assertions",
"pretty_env_logger",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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
2020-12-20 03:44:27 +03:00
version = "0.5.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
2020-12-20 03:44:27 +03:00
checksum = "a31142970826733df8241ef35dc040ef98c679ab14d7c3e54d827099b3acecaa"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
[[package]]
name = "ttf-parser"
cargo update
2020-07-09 09:54:56 +03:00
version = "0.6.2"
window: update smithay-client-toolkit
2020-06-06 21:58:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-07-09 09:54:56 +03:00
checksum = "3e5d7cd7ab3e47dda6e56542f4bbf3824c15234958c6e1bd6aaa347e93499fdc"
window: update smithay-client-toolkit
2020-06-06 21:58:38 +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
2021-03-15 16:32:14 +03:00
version = "1.13.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
2021-03-15 16:32:14 +03:00
checksum = "879f6906492a7cd215bfa4cf595b600146ccfac0c79bcbd1f3000162af5e8b06"
term: cache recently decoded images This commit introduces a small, bounded, LRU cache for recently decoded images. This allows the same image ID to be used in the cache that the same image bits are repeatedly sent to the terminal. This is advantageous because it reduces the amount of texture space required by the gui layer.
2020-10-25 21:59:44 +03:00
tmux: add tmux-cc crate This crate knows how to parse data returned from the `tmux -CC` protocol. refs: https://github.com/wez/wezterm/issues/336
2020-11-02 05:43:44 +03:00
[[package]]
name = "ucd-trie"
version = "0.1.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "56dee185309b50d1f11bfedef0fe6d036842e3fb77413abef29f8f8d1c5d4c1c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "uds_windows"
cargo update
2021-02-04 10:28:23 +03:00
version = "0.1.6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-04 10:28:23 +03:00
checksum = "09b22bf5f590ee6a2892e134e18482e63361319cc62ed108eb236803284cefec"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"tempdir",
cargo update
2021-02-04 10:28:23 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
[[package]]
name = "umask"
version = "0.1.0"
dependencies = [
Take care to restore the original umask wezterm sets a more restrictive umask (`0o077`) by default so that any files that it creates (eg: unix domain socket, log files) are more secure by default. However, some environments rely on the more general default of (`0o022`) without checking that it is set. This matters because programs spawned by wezterm inherit its more restricted umask. I hadn't noticed this because I've had `umask 022` in my shell RC files since sometime in the 1990's. This commit adds some plumbing to the pty layer to specify an optional umask for the child process, and some more to our umask saver helper so that any thread can determine the saved umask without needing a reference to the saver itself, which may be in a different crate. The logic in the config crate has been adjusted to connect the saved value to the default command builder arguments. The net result of this is that running `wezterm -n start bash -- --norc` and typing `umask` in the resultant window now prints `0022`. refs: #416
2021-01-07 20:14:51 +03:00
"lazy_static",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"libc",
]
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
[[package]]
name = "unicase"
version = "2.6.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "50f37be617794602aabbeee0be4f259dc1778fabe05e2d67ee8f79326d5cb4f6"
dependencies = [
upgrade misc deps, notably, async-task
2020-10-05 10:06:01 +03:00
"version_check",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
]
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "unicode-bidi"
cargo update
2021-04-12 17:54:46 +03:00
version = "0.3.5"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-12 17:54:46 +03:00
checksum = "eeb8be209bb1c96b7c177c7420d26e04eccacb0eeae6b980e35fcb74678107e0"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"matches",
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
]
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 = "unicode-general-category"
version = "0.1.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "961c7c250ebd2c88c8f2ca994489e6cac38fe94301f843f0785ed86bc5490881"
wezterm: fixup some allsorts shaping cases * Fixes `keycap 0` by plucking out the prior character for an EnclosingMark * Fixes lookahead for VariationSelector refs: #66
2020-11-21 05:44:28 +03:00
[[package]]
name = "unicode-general-category"
version = "0.3.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "eab1e2c61f9441613aca1a1c88803bb36df292990aada6abb5133b9b532e07ec"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
[[package]]
name = "unicode-joining-type"
cargo update
2020-09-09 19:31:37 +03:00
version = "0.3.1"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "aa33c011d7f075f1e724a8401666be7c7aaa922af7c3b0151e5618c9ed5b599e"
update Cargo.lock Should have been included in refs: https://github.com/wez/wezterm/pull/226
2020-06-20 22:37:40 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "unicode-normalization"
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
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"
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
checksum = "07fbfce1c8a97d547e8b5334978438d9d6ec8c20e38f56d4a4374d181493eaef"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 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.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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "bb0d2e7be6ae3a5fa87eed5fb451aff96f2573d2694942e40543ae0bbe19c796"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "unicode-width"
cargo update
2020-06-30 03:52:14 +03:00
version = "0.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"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "unicode-xid"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.2.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-05-01 19:42:46 +03:00
checksum = "8ccb82d61f80a663efe1f787a51b16b5a51e3314d6ac365b08639f52387b33f3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "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 = [
"num-traits 0.2.14",
"typenum",
]
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
[[package]]
name = "url"
cargo update
2021-02-22 11:09:01 +03:00
version = "2.2.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
2021-02-22 11:09:01 +03:00
checksum = "9ccd964113622c8e9322cfac19eb1004a07e636c545f325da085d5cdde6f1f8b"
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"form_urlencoded",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"idna",
"matches",
"percent-encoding",
Track current working dir via OSC
2020-01-11 10:18:49 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "utf8parse"
deps: misc updates
2020-12-29 20:21:50 +03:00
version = "0.2.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: misc updates
2020-12-29 20:21:50 +03:00
checksum = "936e4b492acfd135421d8dca4b1aa80a7bfc26e702ef3af710e0752684df5372"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2021-02-01 18:54:01 +03:00
[[package]]
name = "value-bag"
version = "1.0.0-alpha.6"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6b676010e055c99033117c2343b33a40a30b91fecd6c49055ac9cd2d6c305ab1"
dependencies = [
"ctor",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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-04-19 19:23:33 +03:00
version = "0.2.12"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-04-19 19:23:33 +03:00
checksum = "cbdbff6266a24120518560b5dc983096efb98462e51d0d68169895b237be3e5d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "vec_map"
cargo update
2020-05-26 08:25:39 +03:00
version = "0.8.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-26 08:25:39 +03:00
checksum = "f1bddf1187be692e79c5ffeab891132dfb0f236ed36a43c7ed39f1165ee20191"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2020-03-14 19:39:38 +03:00
[[package]]
name = "version_check"
cargo update
2021-03-19 08:08:40 +03:00
version = "0.9.3"
cargo update
2020-03-14 19:39:38 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-19 08:08:40 +03:00
checksum = "5fecdca9a5291cc2b8dcf7dc02453fee791a280f3743cb0905f8822ae463b3fe"
cargo update
2020-03-14 19:39:38 +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 = "void"
version = "1.0.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "6a02e4885ed3bc0f2de90ea6dd45ebcbb66dacffe03547fadbb0eeae2770887d"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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"
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 = "fc2f5402d3d0e79a069714f7b48e3ecc60be7775a2c049cb839457457a239532"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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"
vtparse/termwiz: prep for release
2021-04-14 22:59:26 +03:00
version = "0.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
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
"pretty_assertions",
"utf8parse",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
cargo update
2020-06-30 03:52:14 +03:00
[[package]]
name = "waker-fn"
cargo update
2020-09-09 19:31:37 +03:00
version = "1.1.0"
cargo update
2020-06-30 03:52:14 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-09-09 19:31:37 +03:00
checksum = "9d5b2c62b4012a3e1eca5a7e077d13b3bf498c4073e33ccd58626607748ceeca"
cargo update
2020-06-30 03:52:14 +03:00
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "walkdir"
cargo update
2021-03-25 20:08:03 +03:00
version = "2.3.2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-25 20:08:03 +03:00
checksum = "808cf2735cd4b6866113f648b791c6adc5714537bc222d9347bb203386ffda56"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"same-file",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi-util",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "wasi"
bump some versions
2020-01-10 09:39:34 +03:00
version = "0.9.0+wasi-snapshot-preview1"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "cccddf32554fecc6acb585f82a32a72e28b48f8c4c1883ddfeeeaa96f7d8e519"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
cargo update
2020-09-09 19:31:37 +03:00
[[package]]
name = "wasi"
cargo update
2021-02-01 18:54:01 +03:00
version = "0.10.2+wasi-snapshot-preview1"
cargo update
2020-09-09 19:31:37 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-02-01 18:54:01 +03:00
checksum = "fd6fbd9a79829dd1ad0cc20627bf1ed606756a7f77edff7b66b7064f9cb327c6"
cargo update
2020-09-09 19:31:37 +03:00
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
2021-04-05 18:46:55 +03:00
version = "0.2.73"
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-04-05 18:46:55 +03:00
checksum = "83240549659d187488f91f33c0f8547cbfef0b2088bc470c116d1d260ef623d9"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"wasm-bindgen-macro",
]
[[package]]
name = "wasm-bindgen-backend"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.2.73"
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-04-05 18:46:55 +03:00
checksum = "ae70622411ca953215ca6d06d3ebeb1e915f0f6613e3b495122878d7ebec7dae"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
"bumpalo",
"lazy_static",
"log",
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"wasm-bindgen-shared",
]
cargo update
2020-05-26 08:25:39 +03:00
[[package]]
name = "wasm-bindgen-futures"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.4.23"
cargo update
2020-05-26 08:25:39 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-05 18:46:55 +03:00
checksum = "81b8b767af23de6ac18bf2168b690bed2902743ddf0fb39252e36f9e2bfc63ea"
cargo update
2020-05-26 08:25:39 +03:00
dependencies = [
cargo update We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"cfg-if 1.0.0",
cargo update
2020-05-26 08:25:39 +03:00
"js-sys",
"wasm-bindgen",
"web-sys",
]
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "wasm-bindgen-macro"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.2.73"
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-04-05 18:46:55 +03:00
checksum = "3e734d91443f177bfdb41969de821e15c516931c3c3db3d318fa1b68975d0f6f"
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
2021-04-05 18:46:55 +03:00
version = "0.2.73"
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-04-05 18:46:55 +03:00
checksum = "d53739ff08c8a68b0fdbcd54c372b8ab800b1449ab3c9d706503bc7dd1621b2c"
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
dependencies = [
deps: misc updates
2020-12-29 20:21:50 +03:00
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
"wasm-bindgen-backend",
"wasm-bindgen-shared",
]
[[package]]
name = "wasm-bindgen-shared"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.2.73"
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-04-05 18:46:55 +03:00
checksum = "d9a543ae66aa233d14bb765ed9af4a33e81b8b58d1584cf1b47ff8cd0b9e4489"
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
2021-03-01 20:02:05 +03:00
version = "0.28.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-03-01 20:02:05 +03:00
checksum = "06ca44d86554b85cf449f1557edc6cc7da935cc748c8e4bf1c507cbd43bae02c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"downcast-rs",
"libc",
cargo update
2021-03-01 20:02:05 +03:00
"nix 0.20.0",
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
2021-03-01 20:02:05 +03:00
version = "0.28.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-03-01 20:02:05 +03:00
checksum = "8bd75ae380325dbcff2707f0cd9869827ea1d2d6d534cff076858d3f0460fd5a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-03-01 20:02:05 +03:00
"nix 0.20.0",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"once_cell",
cargo update
2021-01-11 19:43:32 +03:00
"smallvec 1.6.1",
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
2021-03-01 20:02:05 +03:00
version = "0.28.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
2021-03-01 20:02:05 +03:00
checksum = "b37e5455ec72f5de555ec39b5c3704036ac07c2ecd50d0bffe02d5fe2d4e65ab"
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
2021-03-01 20:02:05 +03:00
"nix 0.20.0",
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
"wayland-client",
"xcursor",
]
[[package]]
name = "wayland-egl"
cargo update
2021-03-01 20:02:05 +03:00
version = "0.28.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
2021-03-01 20:02:05 +03:00
checksum = "9461a67930ec16da7a4fd8b50e9ffa23f4417240b43ec84008bd1b2c94421c94"
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
2021-03-01 20:02:05 +03:00
version = "0.28.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-03-01 20:02:05 +03:00
checksum = "95df3317872bcf9eec096c864b69aa4769a1d5d6291a5b513f8ba0af0efbd52c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"wayland-client",
"wayland-commons",
"wayland-scanner",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "wayland-scanner"
cargo update
2021-03-01 20:02:05 +03:00
version = "0.28.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-03-01 20:02:05 +03:00
checksum = "389d680d7bd67512dc9c37f39560224327038deb0f0e8d33f870900441b68720"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
2021-03-01 20:02:05 +03:00
version = "0.28.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-03-01 20:02:05 +03:00
checksum = "2907bd297eef464a95ba9349ea771611771aa285b932526c633dc94d5400a8e2"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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-03-01 20:02:05 +03:00
"dlib 0.5.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
"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
2021-04-05 18:46:55 +03:00
version = "0.3.50"
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-04-05 18:46:55 +03:00
checksum = "a905d57e488fec8861446d3393670fb50d27a262344013181c2cdf9fff5481be"
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",
]
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 = "webpki"
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.21.4"
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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "b8e38c0608262c46d4a56202ebabdeb094cef7e560ca7a226c6bf055188aa4ea"
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 = [
"ring",
"untrusted",
]
[[package]]
name = "webpki-roots"
cargo update
2021-04-05 18:46:55 +03:00
version = "0.21.1"
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-05 18:46:55 +03:00
checksum = "aabe153544e473b775453675851ecc86863d2a81d786d741f6b76778f2a48940"
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 = [
"webpki",
]
cargo update
2020-10-02 17:16:20 +03:00
[[package]]
name = "weezl"
cargo update
2021-04-19 19:23:33 +03:00
version = "0.1.5"
cargo update
2020-10-02 17:16:20 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-19 19:23:33 +03:00
checksum = "d8b77fdfd5a253be4ab714e4ffa3c49caf146b4de743e97510c0656cf90f1e8e"
cargo update
2020-10-02 17:16:20 +03:00
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[[package]]
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
name = "wepoll-sys"
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 = "3.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"
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 = "0fcb14dea929042224824779fbc82d9fab8d2e6d3cbc0ac404de8edf489e77ff"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
dependencies = [
"cc",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
move strip-ansi-escapes into its own crate
2020-10-03 09:54:54 +03:00
name = "wezterm"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
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",
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",
fix: cli proxy would terminate too soon refs: https://github.com/wez/wezterm/issues/507
2021-03-28 17:10:30 +03:00
"smol",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"structopt",
"tabout",
"termwiz",
cargo update
2021-03-01 20:02:05 +03:00
"textwrap 0.13.4",
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",
]
[[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",
"log",
"lru",
"metrics",
"mux",
"openssl",
"portable-pty",
"promise",
"rangeset",
"ratelim",
"smol",
"termwiz",
cargo update
2021-03-01 20:02:05 +03:00
"textwrap 0.13.4",
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",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"url",
wezterm-client: cut over to new wezterm-ssh bits refs: https://github.com/wez/wezterm/issues/507
2021-03-28 17:11:14 +03:00
"wezterm-ssh",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"wezterm-term",
]
[[package]]
name = "wezterm-font"
version = "0.1.0"
dependencies = [
"allsorts",
"anyhow",
"config",
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.9.1",
"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",
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: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"fontconfig",
wezterm-font: remove font-kit dep This wasn't used by anything and the version was getting pretty stale. Upgrading is awkward because newer versions pull in an incompatible freetype library version.
2020-10-25 08:01:00 +03:00
"freetype",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"harfbuzz",
Add shaper post-processing function This function is intended to deal with certain kinds of ligatures and certain combining sequences that don't have corresponding glyphs. It isn't hooked up to the gui yet, but does have unit tests that are probably mostly correct. refs: https://github.com/wez/wezterm/issues/478
2021-02-22 20:19:05 +03:00
"k9",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"lazy_static",
"log",
fonts: add custom freetype stream impl The intent is to reveal more context on what's happening in https://github.com/wez/wezterm/issues/671 As a nice side benefit, this avoids the potential inability to open paths that are not utf8 or representable as c-strings on Windows. And on top of that: this enables memory mapped file IO as well, which wasn't enabled previously. This should help to reduce extraneous copies of the font in memory, have fewer open files and minimize the chances of racing with O_CLOEXEC.
2021-04-10 19:23:11 +03:00
"memmap2 0.2.2",
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",
"mux",
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",
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
"pretty_env_logger",
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",
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",
wezterm: fixup some allsorts shaping cases * Fixes `keycap 0` by plucking out the prior character for an EnclosingMark * Fixes lookahead for VariationSelector refs: #66
2020-11-21 05:44:28 +03:00
"unicode-general-category 0.3.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
"unicode-segmentation",
"walkdir",
"wezterm-term",
fonts: use toast notification for missing glyph notification Popping open the config error window is a bit of overkill
2021-05-02 02:05:23 +03:00
"wezterm-toast-notification",
wezterm: fixup win32 build for wezterm-gui changes refs: #301
2020-10-25 03:00:07 +03:00
"winapi 0.3.9",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"window",
]
[[package]]
name = "wezterm-gui"
version = "0.1.0"
dependencies = [
"anyhow",
benchmarking shaping `cargo test --release -p wezterm-gui -- --nocapture bench_shaping`: ``` running 1 test 100: 139.82µs 1000: 385.333µs 10000: 3.144203ms test shapecache::test::bench_shaping ... ok ```
2021-04-28 07:48:15 +03:00
"benchmarking",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"cc",
add debug overlay Adds a `ShowDebugOverlay` key assignment that will create a tab overlay that shows a limited number of recently logged events. refs: https://github.com/wez/wezterm/issues/641
2021-05-03 06:50:01 +03:00
"chrono",
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
"codec",
"config",
"downcast-rs",
"embed-resource",
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
"env-bootstrap",
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
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",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"hdrhistogram",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
"http_req",
cargo update
2020-06-13 20:21:49 +03:00
"image",
Add shaper post-processing function This function is intended to deal with certain kinds of ligatures and certain combining sequences that don't have corresponding glyphs. It isn't hooked up to the gui yet, but does have unit tests that are probably mostly correct. refs: https://github.com/wez/wezterm/issues/478
2021-02-22 20:19:05 +03:00
"k9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"lazy_static",
"libc",
"log",
"lru",
move lua helpers into own crate
2020-10-02 20:28:58 +03:00
"luahelper",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"metrics",
config: we can now read ~/.wezterm.lua This allows for slightly more fancy configuration in the future, but for now it is rather simple: your lua script returns a configuration struct with the same shape as that from the TOML file. A `wezterm` module is provided to the script that provides some constants to help understand the environment in which wezterm is running. I want to add some helpers that make setting up the fonts feel less weird (lots of nesting in the data model makes this weird). The ability to conditionally construct configuration is powerful and helps to address the broader request in refs: https://github.com/wez/wezterm/issues/152 An example config looks like this: ```lua local wezterm = require 'wezterm'; print(wezterm.config_dir); print(wezterm.executable_dir); wezterm.log_error("w00t! running " .. wezterm.version .. " on " .. wezterm.target_triple .. " " .. wezterm.home_dir); return { enable_scroll_bar = true, enable_tab_bar = true, ratelimit_output_bytes_per_second = 400000, scrollback_lines = 350000, font_dirs = {".dotfiles/fonts"}, window_padding = { left = 2, bottom = 2, }, font = { font = {{ family = "Operator Mono SSm Lig Medium", }}, }, unix_domains = { { name = "unix", } }, ssh_domains = { { name = "localhost", remote_address = "localhost", username = "wez", }, }, tls_clients = { { name = "cubetls", remote_address = "cube-localdomain:8080", bootstrap_via_ssh = "cube-localdomain", }, }, tls_servers = { { bind_address = "192.168.1.8:8080", }, }, hyperlink_rules = { { regex = "\\b\\w+://(?:[\\w.-]+)\\.[a-z]{2,15}\\S*\\b", format = "$0", }, }, font_rules= { { italic = true, font = { font = {{ family = "Operator Mono SSm Lig Medium Italic", }} }, }, { italic = true, intensity = "Bold", font = { font = {{ family = "Operator Mono SSm Lig Book Italic", }} }, }, { intensity = "Bold", font = { foreground = "tomato", font = {{ family = "Operator Mono SSm Lig Bold", }} }, }, { intensity = "Half", font = { font = {{ family = "Operator Mono SSm Lig Light", }} }, }, }, } ```
2020-02-26 21:21:03 +03:00
"mlua",
move mux to its own crate
2020-10-03 03:42:49 +03:00
"mux",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"open",
wezterm: allow adding images to termwiztermtab apps Tidies up the plumbing around pixel dimensions so that ImageData can be rendered via the termwiztermtab bits. I put this together to play with sticking the wezterm logo in the close confirmation dialogs. I didn't end up using that though, but have preserved the commented code for use in future hacking.
2020-12-27 01:01:48 +03:00
"ordered-float",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"palette",
"portable-pty",
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
"pretty_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
"promise",
wezterm: render release notes as markdown in the update UI This adds a markdown -> termwiz render helper for the update UI to make the release notes look a bit more intelligible.
2020-06-06 09:13:43 +03:00
"pulldown-cmark",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"rangeset",
move ratelim to its own crate
2020-10-03 03:31:39 +03:00
"ratelim",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
"regex",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serde",
wezterm: check for new releases This commit adds some plumbing that will use the github API to probe the currently released version of wezterm, and if it is newer than the running version, show a window with some release information and links to the changelog and download page. The checks can be disabled in the config (but require a restart to take effect!) and default to checking every 24 hours. If running an AppImage on linux, links directly to the appimage download. In the future I'd like to have the download button use zsync to apply the update to the local image.
2020-05-07 18:58:52 +03:00
"serde_json",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"serial",
"shared_library",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"smol",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"structopt",
"tabout",
wezterm: enable scrollback in the error window This commit doesn't do anything specific to scrollback though! It moves the implementation of the TermWizTermTab away from a directly manipulated Surface and over to using the term::Terminal, making the renderer look more like the one used by the local tab and domain implementation. As a side effect of doing this, we get scrollback management for free. refs: https://github.com/wez/wezterm/issues/201
2020-06-03 17:58:20 +03:00
"terminfo",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"termwiz",
cargo update
2021-03-01 20:02:05 +03:00
"textwrap 0.13.4",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"thiserror",
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",
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-font",
"wezterm-gui-subcommands",
wezterm-gui: we now start an implicit unix mux server When running the GUI, we generate a unix domain socket path for the current process and start up a mux server for that path. This allows `wezterm cli list` and `wezterm cli split-pane` to work implicitly inside the GUI session. When started in this way, the mux server is not persistent; when the GUI process is terminated, all of its windows, tabs and panes are terminated. refs: https://github.com/wez/wezterm/issues/230
2020-12-30 02:58:39 +03:00
"wezterm-mux-server-impl",
RemoteSshDomain now uses wezterm-ssh crate There are a few notable changes as a result: * A number of `.ssh/config` options are now respected; host matching and aliasing and identity file are the main things * The authentication prompt is inline in the window, rather than popping up a separate authentication window Refs: https://github.com/wez/wezterm/issues/457
2021-03-28 03:49:30 +03:00
"wezterm-ssh",
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
"wezterm-term",
tweak updating checking * Allow injecting some initial output to new panes * Have the update checker set this new-pane-banner to a short upsell to let the user know there is an update. * Refactor toast notifications into their own crate * Have the update checker call a new stub function that triggers a toast notification with an URL... but it does nothing because the rust ecosystem doesn't support this on macos yet and I'm writing this code there
2020-12-13 11:17:10 +03:00
"wezterm-toast-notification",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"window",
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
"windows",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
split gui into wezterm-gui executable This commit moves a bunch of stuff around such that `wezterm` is now a lighter-weight executable that knows how to spawn the gui, talk to the mux or emit some escape sequences for imgcat. The gui portion has been moved into `wezterm-gui`, a separate executable that doesn't know about the CLI or imgcat functionality. Importantly, `wezterm.exe` is no longer a window subsystem executable on windows, which makes interactions such as `wezterm -h` feel more natural when spawned from `cmd`, and should allow `type foo.png | wezterm imgcat` to work as expected. That said, I've only tested this on linux so far, and there's a good chance that something mac or windows specific is broken by this change and will need fixing up. refs: #301
2020-10-25 02:40:15 +03:00
[[package]]
name = "wezterm-gui-subcommands"
version = "0.1.0"
dependencies = [
"config",
"structopt",
]
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
[[package]]
name = "wezterm-input-types"
version = "0.1.0"
dependencies = [
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
"serde",
]
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
[[package]]
name = "wezterm-mux-server"
version = "0.1.0"
dependencies = [
"anyhow",
fixup tls mux sessions This adopts smol more broadly, but not yet completely.
2020-10-05 07:07:40 +03:00
"async_ossl",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"config",
wezterm: add env bootstrap to mux server, too
2020-10-25 09:29:52 +03:00
"env-bootstrap",
clean up mux server startup kindof a lot going on in this commit, unintentionally: * Need the lua context set to be moved into the config crate otherwise configs cannot be parsed by the server and we end up with the default configs * Make the server use smol for async io * Drop the use of the daemonize crate, which I had forked anyway. Just inline our own tighter daemonize module * Improve daemon spawning synchronization, however, it still needs work for windows to avoid blocking forever where we don't do daemonizing.
2020-10-04 19:39:28 +03:00
"libc",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"log",
"mux",
"openssl",
"portable-pty",
"promise",
"structopt",
"umask",
add --config name=value CLI options `wezterm`, `wezterm-gui` and `wezterm-mux-server` now all support a new `--config name=value` CLI option that can be specified multiple times to supply config overrides. Since there isn't a simple, direct way to update arbitrary fields of a struct in Rust (there's no runtime reflection), we do this work in lua. The config file returns a config table. Before that is mapped to the Rust Config type, we have a new phase that takes each of the `--config` values and applies it to the config table. For example, you can think of configuration as working like this if wezterm is started as `wezterm --config foo="bar"`: ```lua config = load_config_file(); config.foo = "bar"; return config; ``` The `--config name=value` option is split into `name` and `value` parts. The name part is literally concatenated with `config` in the generated lua code, so the name MUST be valid in that context. The `value` portion is literally inserted verbatim as the rvalue in the assignment. Not quoting or other processing is done, which means that you can (and must!) use the same form that you would use in the config file for the RHS. Strings must be quoted. This allows you to use more complicated expressions on the right hand side, such as: ``` wezterm --config 'font=wezterm.font("Fira Code")' ``` The overrides stick for the lifetime of the process; even if you change the config file and reload, then the value specified by the override will take precedence. refs: https://github.com/wez/wezterm/issues/469 refs: https://github.com/wez/wezterm/issues/499
2021-02-27 21:41:48 +03:00
"wezterm-gui-subcommands",
mux: factor out server bits to helper crate
2020-12-30 02:21:46 +03:00
"wezterm-mux-server-impl",
fixup windows build
2020-12-30 03:59:59 +03:00
"winapi 0.3.9",
mux: factor out server bits to helper crate
2020-12-30 02:21:46 +03:00
]
[[package]]
name = "wezterm-mux-server-impl"
version = "0.1.0"
dependencies = [
"anyhow",
"async_ossl",
"codec",
"config",
"futures",
"hostname",
"lazy_static",
"log",
"mux",
"portable-pty",
"promise",
"rangeset",
"rcgen",
"smol",
wezterm-gui: we now start an implicit unix mux server When running the GUI, we generate a unix domain socket path for the current process and start up a mux server for that path. This allows `wezterm cli list` and `wezterm cli split-pane` to work implicitly inside the GUI session. When started in this way, the mux server is not persistent; when the GUI process is terminated, all of its windows, tabs and panes are terminated. refs: https://github.com/wez/wezterm/issues/230
2020-12-30 02:58:39 +03:00
"uds_windows",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
"url",
"wezterm-term",
wezterm-gui: we now start an implicit unix mux server When running the GUI, we generate a unix domain socket path for the current process and start up a mux server for that path. This allows `wezterm cli list` and `wezterm cli split-pane` to work implicitly inside the GUI session. When started in this way, the mux server is not persistent; when the GUI process is terminated, all of its windows, tabs and panes are terminated. refs: https://github.com/wez/wezterm/issues/230
2020-12-30 02:58:39 +03:00
"winapi 0.3.9",
Move server to its own wezterm-mux-server binary
2020-10-03 09:35:18 +03:00
]
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
[[package]]
name = "wezterm-ssh"
wezterm-ssh: prep for release
2021-05-03 19:56:19 +03:00
version = "0.1.1"
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",
"base64",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
"dirs-next",
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",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
"k9",
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",
"portable-pty",
wezterm-ssh: add pubkey based auth I can't get this to succeed though; I suspect there may be a lingering bug from libssh2 and/or trailing support for newer openssh features. refs: https://github.com/wez/wezterm/issues/457
2021-03-27 09:54:57 +03:00
"pretty_env_logger",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
"regex",
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",
"ssh2",
"structopt",
"termwiz",
Add ssh_config parser refs: https://github.com/wez/wezterm/issues/457
2021-03-16 19:43:33 +03:00
]
term: rename crate to wezterm-term in advance of publishing Add some more docs and remove a couple of dead bits of code.
2020-06-13 19:04:13 +03:00
[[package]]
name = "wezterm-term"
version = "0.1.0"
dependencies = [
"anyhow",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
"num-traits 0.2.14",
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",
"palette",
"pretty_assertions",
termwiz+term: improved emulation conformance in a number of areas This commit adds support for left/right margins and has been tested against esctest, with a final status of: ``` 309 tests passed, 239 known bugs ``` "known bugs" also includes unimplemented features; we have a similar degree as iTerm2. As of this commit, we now report as a vt520ish machine to DA1. I confess to not having read enough of the relevant docs to know whether this is totally righteous.
2020-06-20 07:20:05 +03:00
"pretty_env_logger",
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
"serde",
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
"sha2",
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",
"unicode-segmentation",
"unicode-width",
"url",
]
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 = [
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",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"log",
wezterm: macos: show a toast notification when an update is available This commit implements the deprecated NSUserNotification bits needed to be able to handle clicking on a notification and open our choice of URL. Ideally we'd use the newer UserNotifications framework, but that requires code signing.
2020-12-16 08:21:23 +03:00
"objc",
"open",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"serde",
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
"windows",
toast: hook up action/event handling on Windows refs: #489
2021-03-15 01:23:42 +03:00
"xml-rs",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
"zbus",
"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
]
add wgpu example
2021-05-06 19:04:16 +03:00
[[package]]
name = "wgpu"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "f07667388164ad75066dcbab46e295abd8204fd9a6dc057704b8d703837d12a8"
dependencies = [
"arrayvec",
"js-sys",
"log",
"naga",
"parking_lot 0.11.1",
"raw-window-handle",
"smallvec 1.6.1",
"wasm-bindgen",
"wasm-bindgen-futures",
"web-sys",
"wgpu-core",
"wgpu-types",
]
[[package]]
name = "wgpu-core"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "59abd59fe91fe502fe2dd8777bcac414069199af22dd2a92a1bb635f9f251425"
dependencies = [
"arrayvec",
"bitflags",
"cfg_aliases",
"copyless",
"fxhash",
"gfx-backend-dx11",
"gfx-backend-dx12",
"gfx-backend-empty",
"gfx-backend-gl",
"gfx-backend-metal",
"gfx-backend-vulkan",
"gfx-hal",
"gpu-alloc",
"gpu-descriptor",
"log",
"naga",
"parking_lot 0.11.1",
"profiling",
"raw-window-handle",
"smallvec 1.6.1",
"thiserror",
"wgpu-types",
]
[[package]]
name = "wgpu-types"
version = "0.8.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "aa248d90c8e6832269b8955bf800e8241f942c25e18a235b7752226804d21556"
dependencies = [
"bitflags",
]
cargo update
2021-03-01 20:02:05 +03:00
[[package]]
name = "which"
cargo update
2021-04-05 18:46:55 +03:00
version = "4.1.0"
cargo update
2021-03-01 20:02:05 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-04-05 18:46:55 +03:00
checksum = "b55551e42cbdf2ce2bedd2203d0cc08dba002c27510f86dab6d0ce304cba3dfe"
cargo update
2021-03-01 20:02:05 +03:00
dependencies = [
cargo update
2021-04-05 18:46:55 +03:00
"either",
cargo update
2021-03-01 20:02:05 +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 = "winapi"
version = "0.2.8"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "167dc9d6949a9b857f3451275e911c3f44255842c1f7a76f33c55103a909087a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "winapi"
cargo update
2020-06-30 03:52:14 +03:00
version = "0.3.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-06-30 03:52:14 +03:00
checksum = "5c839a674fcd7a98952e593242ea400abe93992746761e38641405d28b00f419"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi-i686-pc-windows-gnu",
"winapi-x86_64-pc-windows-gnu",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "winapi-build"
version = "0.1.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "2d315eee3b34aca4797b2da6b13ed88266e6d612562a0c46390af8299fc699bc"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "winapi-i686-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "ac3b87c63620426dd9b991e5ce0329eff545bccbbb34f3be09ff6fb6ab51b7b6"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "winapi-util"
cargo update
2020-05-02 22:13:10 +03:00
version = "0.1.5"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2020-05-02 22:13:10 +03:00
checksum = "70ec6ce85bb158151cae5e5c87f95a8e97d2c0c4b001223f33a334e3ce5de178"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "winapi-x86_64-pc-windows-gnu"
version = "0.4.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "712e227841d057c1ee1cd2fb22fa7e5a5461ae8e48fa2ca79ec42cfc1931183f"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "window"
version = "0.1.0"
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"anyhow",
window: separate gui window state from app state Removes the callbacks type and replaces event dispatch with an async capable channel. This makes it a bit simpler to model some of the window internals, and to prepare for a wgpu enabled future. This changes have been tested only on linux so far.
2021-05-04 18:38:43 +03:00
"async-channel",
deps: misc updates
2020-12-29 20:21:50 +03:00
"async-task",
window: separate gui window state from app state Removes the callbacks type and replaces event dispatch with an async capable channel. This makes it a bit simpler to model some of the window internals, and to prepare for a wgpu enabled future. This changes have been tested only on linux so far.
2021-05-04 18:38:43 +03:00
"async-trait",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"bitflags",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
"clipboard-win",
"cocoa",
remove the config bridge and have window -> config directly
2021-03-24 07:56:57 +03:00
"config",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"core-foundation 0.7.0",
cargo update
2020-06-30 03:52:14 +03:00
"core-graphics 0.19.2",
x11: load XCursor.theme based cursors when available This requires `xcb-util-image-devel` on fedora, not sure about debian or other systems so far. refs: #524
2021-03-09 09:00:42 +03:00
"dirs-next",
deps: upgrade euclid -> 0.22
2020-12-10 21:03:16 +03:00
"euclid",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"filedescriptor",
window: glium and gl_generator version bump
2020-06-15 07:24:54 +03:00
"gl_generator",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"glium",
wezterm: improve texture atlas allocation This commit uses the guillotine algorithm to assign rectangles, which is superior to the dumb algorithm previously in use. In addition, in the first pass of painting, if we get a texture space error, we clear the atlas and try again without increasing it size, which should serve as the ultimate defrag. Subsequent passes will cause the texture to grow if needed. refs: #306
2020-10-23 23:57:58 +03:00
"guillotiere",
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to 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",
"memmap",
"metrics",
"mio",
"objc",
cargo update
2020-06-13 20:21:49 +03:00
"pretty_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
"promise",
add raw-window-handle impls
2021-05-06 08:59:52 +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-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",
extract window::input to wezterm-input-types
2020-12-10 00:00:23 +03:00
"wezterm-input-types",
add wgpu example
2021-05-06 19:04:16 +03:00
"wgpu",
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
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
"winreg 0.6.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
"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
"xcb 0.9.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
"xcb-util",
"xkbcommon",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
toast: hook up action/event handling on Windows refs: #489
2021-03-15 01:23:42 +03:00
[[package]]
name = "windows"
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
version = "0.9.1"
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
checksum = "361f3533a83ee1a28c9be59683f40043db02dbedf6479ce8795657386195c97f"
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 = [
"const-sha1",
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
"windows_gen",
"windows_macros",
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]]
name = "windows_gen"
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
version = "0.9.1"
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"
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
checksum = "54154dbc515d58723f6b6053c12f1065da7389f733660581b2391bd1af480452"
toast: hook up action/event handling on Windows refs: #489
2021-03-15 01:23:42 +03:00
dependencies = [
"syn",
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]]
name = "windows_macros"
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
version = "0.9.1"
build(deps): bump windows from 0.4.0 to 0.5.0 Bumps [windows](https://github.com/microsoft/windows-rs) from 0.4.0 to 0.5.0. - [Release notes](https://github.com/microsoft/windows-rs/releases) - [Changelog](https://github.com/microsoft/windows-rs/blob/master/docs/changelog.md) - [Commits](https://github.com/microsoft/windows-rs/commits) Signed-off-by: dependabot[bot] <support@github.com>
2021-03-22 09:26:29 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
checksum = "0f7794c652845dc466cb8dc1b86c08345707c8144bc53e9086430047c7d33b76"
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 = [
"syn",
deps: update windows dep to 0.4 -> 0.9 dependabot keeps trying and failing because lots of things changed. Let's try and get ahead of it...
2021-05-04 08:05:35 +03:00
"windows_gen",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = "winreg"
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
version = "0.6.2"
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"
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
checksum = "b2986deb581c4fe11b621998a5e53361efe6b48a151178d0cd9eeffa4dc6acc9"
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 = [
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
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"
version = "0.8.0"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
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
checksum = "d107f8c6e916235c4c01cabb3e8acf7bea8ef6a63ca2e7fa0527c049badfc48c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update
2020-06-30 03:52:14 +03:00
"winapi 0.3.9",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
wezterm-font: teach gdi locator how to search for fallback fonts This commit uses a bit of DirectWrite to discover which font(s) can be used to render a set of codepoints. While hooking this up, I found that the method we were using to extract the font data didn't handle TTC data so this commit improves some parser diagnostics and handling for that. refs: https://github.com/wez/wezterm/issues/299
2020-11-26 01:53:42 +03:00
[[package]]
name = "wio"
version = "0.2.2"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "5d129932f4644ac2396cb456385cbf9e63b5b30c6e8dc4820bdca4eb082037a5"
dependencies = [
"winapi 0.3.9",
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "ws2_32-sys"
version = "0.2.1"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d59cefebd0c892fa2dd6de581e937301d8552cb44489cdff035c6187cb63fa5e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"winapi 0.2.8",
"winapi-build",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
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 = "wyz"
version = "0.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "85e60b0d1b5f99db2556934e21937020776a5d31520bf169e851ac44e6420214"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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
2020-02-01 10:01:38 +03:00
version = "2.18.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-02-01 10:01:38 +03:00
checksum = "77ecd092546cb16f25783a5451538e73afc8d32e242648d54f4ae5459ba1e773"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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
]
[[package]]
name = "x11-clipboard"
version = "0.3.3"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "89bd49c06c9eb5d98e6ba6536cf64ac9f7ee3a009b2f53996d405b3944f6bcea"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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 = [
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
"xcb 0.8.2",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "xcb"
version = "0.8.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 = "5e917a3f24142e9ff8be2414e36c649d47d6cc2ba81f16201cdef96e533e02de"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
"log",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
upgrade to latest smithay client toolkit This version greatly improves the client side decoration handling under Wayland and allows rendering the window title in the titlebar (shocker!).
2020-05-03 01:53:32 +03:00
[[package]]
name = "xcb"
version = "0.9.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
checksum = "62056f63138b39116f82a540c983cc11f1c90cd70b3d492a70c25eaa50bd22a6"
dependencies = [
"libc",
"log",
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
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "xcb-util"
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
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"
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
checksum = "43893e47f27bf7d81d489feef3a0e34a457e90bc314b7e74ad9bb3980e4c1c48"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
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
"xcb 0.9.0",
]
[[package]]
name = "xcursor"
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"
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 We need a newer version of ring in order to compile on M1 refs: #343
2020-12-05 21:30:13 +03:00
checksum = "3a9a231574ae78801646617cefd13bfe94be907c0e4fa979cfd8b770aa3c5d08"
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
2021-02-15 23:14:00 +03:00
"nom 6.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
]
[[package]]
name = "xdg"
version = "2.2.0"
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
checksum = "d089681aa106a86fade1b0128fb5daf07d5867a509ab036d99988dec80429a57"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "xi-unicode"
deps: misc updates
2020-12-29 20:21:50 +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: misc updates
2020-12-29 20:21:50 +03:00
checksum = "a67300977d3dc3f8034dae89778f502b6ba20b269527b3223ba59c0cf393bb8a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the 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"
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
version = "0.5.0"
source = "git+https://github.com/wez/xkbcommon-rs.git?rev=01a0a0cd5663405e6e4abb1ad3add9add1496f58#01a0a0cd5663405e6e4abb1ad3add9add1496f58"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking 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",
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
"memmap",
"xcb 0.9.0",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "xml-rs"
cargo update
2020-05-02 22:13:10 +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"
cargo update
2020-05-02 22:13:10 +03:00
checksum = "b07db065a5cf61a7e4ba64f29e67db906fb1787316516c4e6e5ff0fea1efcd8a"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
mux: sound groundwork for auto pki This is a step towards automatic management of TLS certs for the mux stuff.
2020-02-02 04:40:27 +03:00
[[package]]
name = "yasna"
cargo update
2021-05-01 19:42:46 +03:00
version = "0.4.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
2021-05-01 19:42:46 +03:00
checksum = "e262a29d0e61ccf2b6190d7050d4b237535fc76ce4c1210d9caa316f71dffa75"
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 = [
"chrono",
]
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
2021-04-12 17:54:46 +03:00
version = "1.9.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
2021-04-12 17:54:46 +03:00
checksum = "2326acc379a3ac4e34b794089f5bdb17086bf29a5fdf619b7b4cc772dc2e9dad"
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 = [
"async-io",
"byteorder",
"derivative",
"enumflags2",
"fastrand",
"futures",
"nb-connect",
"nix 0.17.0",
"once_cell",
"polling",
"scoped-tls",
"serde",
"serde_repr",
"zbus_macros",
"zvariant",
]
[[package]]
name = "zbus_macros"
cargo update
2021-04-12 17:54:46 +03:00
version = "1.9.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
2021-04-12 17:54:46 +03:00
checksum = "a482c56029e48681b89b92b5db3c446db0915e8dd1052c0328a574eda38d5f93"
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-macro-crate",
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
[[package]]
name = "zstd"
cargo update
2021-03-08 10:18:21 +03:00
version = "0.6.1+zstd.1.4.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "5de55e77f798f205d8561b8fe2ef57abfb6e0ff2abe7fd3c089e119cdb5631a3"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"zstd-safe",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "zstd-safe"
cargo update
2021-03-08 10:18:21 +03:00
version = "3.0.1+zstd.1.4.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "1387cabcd938127b30ce78c4bf00b30387dddf704e3f0881dbc4ff62b5566f8c"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"libc",
"zstd-sys",
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
]
[[package]]
name = "zstd-sys"
cargo update
2021-03-08 10:18:21 +03:00
version = "1.4.20+zstd.1.4.9"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-08 10:18:21 +03:00
checksum = "ebd5b733d7cf2d9447e2c3e76a5589b4f5e5ae065c22a2bc0b023cbc331b6c8e"
Enable GH actions build caching We need to build in release mode so targets are cacheable. GH has a limit of 400MB per cache blob and we're at 750MB with the debug build. Slim it down a bit. The cache wants to hash the Cargo.lock file so I've removed that from the ignore file and added it to the repo. This might cause an error for users checking out the repo after this change is pushed; removing the local Cargo.lock should resolve that.
2019-12-29 21:43:35 +03:00
dependencies = [
cargo update to pick up filedescriptor 0.7.1 I got to the bottom of the hang on startup when trying to connect to the multiplexer on windows and it was because of the change in 367a44fb96d9ebd4a38621cc6afdde04a320350c to try to drain the pollable channel. This mapped to ReadFile on windows which always tries to fill the buffer even if it is a socket under the covers. https://github.com/wez/wzsh/commit/348421b0109f3be498dc23fc3937b5fba7c97132 teaches filedescriptor to use the recv/send if the filedescriptor is really a socket and that resolves the hang.
2020-01-16 10:05:03 +03:00
"cc",
"libc",
]
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
[[package]]
name = "zvariant"
cargo update
2021-03-15 16:32:14 +03:00
version = "2.6.0"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-15 16:32:14 +03:00
checksum = "678e7262502a135f49b1ece65010526649be7ee68acb80e1fc5377fc71fef878"
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",
"serde",
"zvariant_derive",
]
[[package]]
name = "zvariant_derive"
cargo update
2021-03-15 16:32:14 +03:00
version = "2.6.0"
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
source = "registry+https://github.com/rust-lang/crates.io-index"
cargo update
2021-03-15 16:32:14 +03:00
checksum = "27d7c34325a35020b94343389cc9391e0f8ac245cca9155429c4022d93141241"
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-macro-crate",
"proc-macro2",
toast: windows: setup own AppUserModelID for our notifications This is so that our notifications show as coming from wezterm rather than powershell.
2021-02-18 10:45:52 +03:00
"quote",
"syn",
remove libdbus/libsystem dependency Replaces notify-rust with directly calling into the zbus crate. This provides a pure rust interface to DBUS and provides more flexible control over notification handling. closes: #485
2021-02-17 09:24:23 +03:00
]
Reference in New Issue Copy Permalink