wezterm/term/Cargo.toml

[package]
authors = ["Wez Furlong <wez@wezfurlong.org>"]
name = "wezterm-term"
version = "0.1.0"
edition = "2018"
repository = "https://github.com/wez/wezterm"
description = "The Virtual Terminal Emulator core from wezterm; helpful for implementing terminal emulators"
license = "MIT"
documentation = "https://docs.rs/wezterm-term"
keywords = ["terminal", "emulator", "vte"]
readme = "README.md"

[features]
use_serde = ["termwiz/use_serde"]

[dependencies]
anyhow = "1.0"
bitflags = "1.3"
csscolorparser = "0.6"
downcast-rs = "1.0"
humansize = "2.1"
miniz_oxide = "0.4"
finl_unicode = "1.2"
hex = "0.4"
image = "0.24.6"
lazy_static = "1.4"
log = "0.4"
lru = "0.7"
num-traits = "0.2"
ordered-float = "4.1"
serde = {version="1.0", features = ["rc"]}
terminfo = "0.8"
unicode-normalization = "0.1.21"
url = "2"
wezterm-bidi = { path = "../bidi" }
wezterm-dynamic = { path = "../wezterm-dynamic" }

[dev-dependencies]
env_logger = "0.10"
k9 = "0.11.0"

[dependencies.termwiz]
version = "0.22"
path = "../termwiz"
features = ["use_image"]
move term to its own crate This makes it harder to accidentally violate separation of concerns. 2018-01-31 21:38:33 +03:00			`[package]`
			`authors = ["Wez Furlong <wez@wezfurlong.org>"]`
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			`name = "wezterm-term"`
move term to its own crate This makes it harder to accidentally violate separation of concerns. 2018-01-31 21:38:33 +03:00			`version = "0.1.0"`
update term to 2018 edition 2019-02-19 10:20:59 +03:00			`edition = "2018"`
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			`repository = "https://github.com/wez/wezterm"`
			`description = "The Virtual Terminal Emulator core from wezterm; helpful for implementing terminal emulators"`
			`license = "MIT"`
			`documentation = "https://docs.rs/wezterm-term"`
			`keywords = ["terminal", "emulator", "vte"]`
			`readme = "README.md"`
move term to its own crate This makes it harder to accidentally violate separation of concerns. 2018-01-31 21:38:33 +03:00
term: make serde optional 2020-06-13 20:00:09 +03:00			`[features]`
remove serde from bidi 2022-05-18 19:25:41 +03:00			`use_serde = ["termwiz/use_serde"]`
term: make serde optional 2020-06-13 20:00:09 +03:00
move term to its own crate This makes it harder to accidentally violate separation of concerns. 2018-01-31 21:38:33 +03:00			`[dependencies]`
failure -> anyhow + thiserror 2019-12-15 08:43:05 +03:00			`anyhow = "1.0"`
deps: update bitflags -> 1.3 2021-08-16 04:21:17 +03:00			`bitflags = "1.3"`
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry. 2022-06-13 06:17:48 +03:00			`csscolorparser = "0.6"`
mux: allow client to provide palette to mux server The server-side ownership of the palette is a stumbling block for many users, so let's fix it. This commit allows the client to pass its configured palette to the server when it connects, and when the config is changed. That palette takes precedence over the palette from the server config. However, if the remote application uses any escape sequences that redefine the color palette, the color palette that was active at that point in time is forked and use as the basis, and will remain the active palette until the palette is reset via escape sequences. refs: https://github.com/wez/wezterm/issues/2686 refs: https://github.com/wez/wezterm/issues/3397 2023-03-31 18:02:32 +03:00			`downcast-rs = "1.0"`
term: improve readability of error message for oversized image refs: https://github.com/wez/wezterm/issues/3264 2023-03-17 08:41:52 +03:00			`humansize = "2.1"`
basic kitty img animation support this is the bare minimum to squeak by with notcurses; it currently only supports editing single frame images. refs: #986 2021-08-03 07:34:38 +03:00			`miniz_oxide = "0.4"`
deps: upgrade finl_unicode to 1.2 2022-10-23 22:07:00 +03:00			`finl_unicode = "1.2"`
termwiz: recognize the XTGETTCAP DCS sequence Parse and respond to this sequence docs can be found https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h4-Device-Control-functions:DCS-plus-q-Pt-ST.F95 refs: https://github.com/wez/wezterm/issues/954 2021-07-25 07:02:54 +03:00			`hex = "0.4"`
imgcat: work better with tmux and conpty Neither of these understand image protocols, and both are an additional processing layer between the application and wezterm. This commit detects and wraps OSC sequences in tmux's passthru sequence so that the data is passed on to wezterm rather than elided from the data stream. For image protocols in both tmux and conpty, work a little smarter and explicitly move the cursor position to the same location that wezterm would move it to. That prevents the display from being as mangled by tmux/conpty due to a diverging understanding of the cursor position. The logic isn't perfect, and can result in the x-coordinate being incorrect, and this won't work with the new --position argument either in its current state, without adding a lot of complexity to deal with scrolling and relative and absolute positioning handling. To facilitate that, a new termwiz Terminal trait method has been added to probe the terminal name, version, cell and pixel dimensions. It's not pretty. refs: https://github.com/wez/wezterm/issues/3624 refs: https://github.com/wez/wezterm/issues/3716 2023-07-16 08:07:49 +03:00			`image = "0.24.6"`
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 = "1.4"`
more log changes 2019-06-09 01:30:47 +03:00			`log = "0.4"`
deps: lru 0.6 -> 0.7 2021-10-11 05:29:42 +03:00			`lru = "0.7"`
maybe fixup windows build for num/num_traits changes 2020-06-13 22:05:47 +03:00			`num-traits = "0.2"`
deps: ordered-float -> 4.1.0 closes: https://github.com/wez/wezterm/pull/4338 2023-09-29 00:39:22 +03:00			`ordered-float = "4.1"`
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			`serde = {version="1.0", features = ["rc"]}`
update terminfo to 0.8 2023-03-24 20:12:49 +03:00			`terminfo = "0.8"`
add normalize_to_nfc config option refs: #2482 2022-09-06 18:58:09 +03:00			`unicode-normalization = "0.1.21"`
Track current working dir via OSC 2020-01-11 10:18:49 +03:00			`url = "2"`
bidi: tag Line with bidi mode This commit refines bidi property handling: * experimental_bidi has been split into two new configuration settings; `bidi_enabled` (which controls whether the terminal performs implicit bidi processing) and `bidi_direction` which specifies the base direction and whether auto detection is enabled. * The `Line` type can now store those bidi properties (they are actually split across 3 bits representing enabled, auto-detection and direction) * The terminal now has a concept of active bidi properties and default bidi properties * The default properties are pulled from the wezterm configuration * active bidi properties are potentially set via escape sequences, BDSM (which sets bidi_enabled) and SCP (which sets bidi_direction). We don't support the 2501 temporary dec private mode suggested by the BIDI recommendation doc at this time. * When creating new `Line`'s or clearing from the start of a `Line`, the effective bidi properties are computed (from the active props, falling back to default propr) and applied to the `Line`. * When rendering the line, we now look at its bidi properties instead of just the global config. The default bidi properties are `bidi_enabled: false` and `bidi_direction: LeftToRight` which corresponds to the typical bidi-unaware mode of most terminals. It is possible to live reload the config to change the effective defaults, but note that they apply, by design, to new lines being processed through the terminal. That means existing output is left unaffected by a config reload, but subsequently printed lines will respect it. Pressing CTRL-L or otherwise contriving to have the running application refresh its display should cause the refreshed display to update and apply the new bidi mode. refs: #784 2022-01-30 19:22:17 +03:00			`wezterm-bidi = { path = "../bidi" }`
config: cut over to wezterm-dynamic Avoid using serde for mapping between Lua and Rust for the `Config` struct. This improves the build speed of the config crate by 2x; it goes down from 30 seconds to 9 seconds on my 5950x. 2022-05-14 18:00:03 +03:00			`wezterm-dynamic = { path = "../wezterm-dynamic" }`
use termwiz to replace most of the escape parsing 2018-08-04 08:37:04 +03:00
improve double-click selection of wrapped lines This one has been bugging me for a while; we now know when we've wrapped a line and can join it without a line break when double-clicking to select a word. This commit introduces a wrapped attribute to help record this information, which could potentially help with when it comes to looking at nicer resize behavior in refs: https://github.com/wez/wezterm/issues/14 2019-05-27 02:05:51 +03:00			`[dev-dependencies]`
env_logger -> 0.10 closes: https://github.com/wez/wezterm/pull/2803 2022-11-28 07:37:25 +03:00			`env_logger = "0.10"`
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			`k9 = "0.11.0"`
improve double-click selection of wrapped lines This one has been bugging me for a while; we now know when we've wrapped a line and can join it without a line break when double-clicking to select a word. This commit introduces a wrapped attribute to help record this information, which could potentially help with when it comes to looking at nicer resize behavior in refs: https://github.com/wez/wezterm/issues/14 2019-05-27 02:05:51 +03:00
use termwiz to replace most of the escape parsing 2018-08-04 08:37:04 +03:00			`[dependencies.termwiz]`
fixup images with the multiplexer * Translate from File to EncodedFile as needed * Adopt blob leases in the mux server * Fix an issue where the first image sent by the mux server would be replaced on the client by its background image, if configured. Removed the ImageData::id field to resolve this: you should use the hash field instead to identify and disambiguate images. Bumped the termwiz API version because this is conceptually a breaking change to the API refs: https://github.com/wez/wezterm/issues/3343 2023-03-24 07:40:01 +03:00			`version = "0.22"`
tweak manifest to point to in-tree termwiz 2018-08-05 18:00:45 +03:00			`path = "../termwiz"`
move image decoding into termwiz Adds a use_image feature to termwiz that enables an optional dep on the image crate. This in turn allows decoding of animation formats (gif, apng) from file data, but more crucially, allows modeling animation frames at the termwiz layer, which is a pre-req for enabling kitty img protocol animation support. refs: #986 2021-08-03 02:22:55 +03:00			`features = ["use_image"]`