wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-12-25 14:22:37 +03:00
Code Issues Projects Releases Wiki Activity
7d01d3f683
wezterm/pty/Cargo.toml

45 lines
934 B
TOML
Raw Normal View History

move pty to its own crate in preparation for publishing Refs: https://github.com/wez/wezterm/issues/27
2019-05-20 04:38:59 +03:00
[package]
name = "portable-pty"
pty: introduce ChildKiller trait In the mux layer, we have some code that takes a `Child` and then does a bit of naughty reaching through the abstraction to get at the pid/handle of the child so that we can send it signals even if the child is itself mutably (and thus exclusively) borrowed for the purposes of waiting. That worked fine for local processes spawned in the mux, but we also use LocalPane to wrap around arbitrary `Child`ren, such as Ssh, that are not local and that don't have a local process id, which meant that this hack wouldn't work for them. To make things a bit worse, those ssh ptys were used to ssh2 days where we didn't have a way to signal the remote process and just did nothing, leading to confusing situations such as https://github.com/wez/wezterm/issues/1197 This commit graduates the hack mentioned in the first paragraph to its own ChildKiller trait. This makes the concept of waiting for the Child distinct from signalling it and explicitly allows getting a separate object that can be used for signalling. With that in place, we're forced to implement something appropriate for the ssh pty implementations; one in the pty crate itself, one in wezterm-ssh and the wrapper that we use in the mux crate. The upshot of this is that the `CloseCurrentPane` action now operates correctly on panes that were the result of split operations.
2021-12-11 18:32:21 +03:00
version = "0.7.0"
move pty to its own crate in preparation for publishing Refs: https://github.com/wez/wezterm/issues/27
2019-05-20 04:38:59 +03:00
authors = ["Wez Furlong"]
edition = "2018"
repository = "https://github.com/wez/wezterm"
description = "Cross platform pty interface"
license = "MIT"
documentation = "https://docs.rs/portable-pty"
[dependencies]
failure -> anyhow + thiserror
2019-12-15 08:43:05 +03:00
anyhow = "1.0"
term: ignore first OSC title change sequence on Windows ConPTY emits a sequence that sets the title to the name of the program that is initially launched into it. This commit tries to ignore that sequence in that circumstance, so that the logic in b5d156c282a01f2f1cb10aee98655a4a2c2c71e5 can more dynamically set the tab title.
2021-12-25 10:58:25 +03:00
downcast-rs = "1.0"
filedescriptor: remove anyhow from public interface Use thiserror instead
2021-05-24 00:24:01 +03:00
filedescriptor = { version="0.8", path = "../filedescriptor" }
more log
2019-06-09 01:37:55 +03:00
log = "0.4"
move pty to its own crate in preparation for publishing Refs: https://github.com/wez/wezterm/issues/27
2019-05-20 04:38:59 +03:00
libc = "0.2"
deps: shell-words -> 1.1.0
2022-02-07 04:32:10 +03:00
shell-words = "1.1"
move pty to its own crate in preparation for publishing Refs: https://github.com/wez/wezterm/issues/27
2019-05-20 04:38:59 +03:00
serde_derive = {version="1.0", optional=true}
serde = {version="1.0", optional=true}
pty, wezterm: add support for serial ports Tested only on windows with a USB serial connector to my NUC running linux. This allows opening up wezterm on a serial port connection. Serial is closer to a tty than a pty, so it is a bit different to configure and use. This commit allows running: ``` wezterm serial COM3 ``` to open a window that connects to the specified COM port. You can change the baud rate with: ``` wezterm serial --baud 9600 COM3 ``` There are more options that could be set, but I'm a bit lazy and have only exposed the baud rate to the wezterm cli so far.
2019-08-07 20:59:42 +03:00
serial = "0.4"
deps: misc updates
2020-12-29 20:21:50 +03:00
ssh2 = {optional=true, version="0.9"}
move pty to its own crate in preparation for publishing Refs: https://github.com/wez/wezterm/issues/27
2019-05-20 04:38:59 +03:00
[features]
default = []
serde_support = ["serde", "serde_derive"]
pty: add ssh support This commit adds (untested!) support for remote ttys over ssh. It requires that the embedding application connect and authenticate the ssh session prior to turning it into a PtySystem implementation.
2019-08-02 20:51:10 +03:00
ssh = ["ssh2"]
move pty to its own crate in preparation for publishing Refs: https://github.com/wez/wezterm/issues/27
2019-05-20 04:38:59 +03:00
[target."cfg(windows)".dependencies]
deps: update bitflags -> 1.3
2021-08-16 04:21:17 +03:00
bitflags = "1.3"
deps: normalize the lazy-static version
2020-11-13 18:57:09 +03:00
lazy_static = "1.4"
move pty to its own crate in preparation for publishing Refs: https://github.com/wez/wezterm/issues/27
2019-05-20 04:38:59 +03:00
shared_library = "0.1"
winapi = { version = "0.3", features = [
"winuser",
"consoleapi",
"handleapi",
"fileapi",
"namedpipeapi",
"synchapi",
]}
pty: pre-fill base env from registry env settings on Windows I think I'd like to make a config option for this, but for the moment, this first pass unconditionally updates the base environment with data from the registry. refs: https://github.com/wez/wezterm/issues/1848
2022-04-19 19:56:23 +03:00
winreg = "0.10"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
[dev-dependencies]
pty: update async example for more recent smol release
2020-10-02 17:30:38 +03:00
smol = "1.2"
pty: async example using smol refs: https://github.com/wez/wezterm/issues/166
2020-05-09 20:23:15 +03:00
futures = "0.3"
Reference in New Issue Copy Permalink