1
1
mirror of https://github.com/wez/wezterm.git synced 2024-11-24 07:46:59 +03:00
wezterm/termwiz/Cargo.toml

67 lines
1.4 KiB
TOML
Raw Normal View History

[package]
authors = ["Wez Furlong"]
name = "termwiz"
version = "0.11.0"
2019-02-19 10:26:41 +03:00
edition = "2018"
repository = "https://github.com/wez/wezterm"
description = "Terminal Wizardry for Unix and Windows"
license = "MIT"
documentation = "https://docs.rs/termwiz"
2019-05-28 05:57:44 +03:00
keywords = ["terminal", "readline", "console", "curses"]
2019-05-28 06:08:02 +03:00
readme = "README.md"
[dependencies]
2020-12-29 20:21:50 +03:00
base64 = "0.13"
2019-05-28 06:08:02 +03:00
bitflags = "1.0"
cassowary = {version="0.3", optional=true}
2019-12-15 08:43:05 +03:00
anyhow = "1.0"
2020-01-26 20:14:26 +03:00
filedescriptor = { version="0.7", path = "../filedescriptor" }
fnv = {version="1.0", optional=true}
lazy_static = "1.4"
2019-05-28 06:08:02 +03:00
libc = "0.2"
2019-06-09 01:37:55 +03:00
log = "0.4"
2019-05-28 06:08:02 +03:00
memmem = "0.1"
num-traits = "0.2"
2020-12-28 19:25:43 +03:00
ordered-float = "2.0"
regex = "1"
2020-12-29 20:21:50 +03:00
semver = "0.11"
serde = {version="1.0", features = ["rc", "derive"], optional=true}
2020-01-10 09:39:34 +03:00
terminfo = "0.7"
thiserror = "1.0"
wezterm: improve shaping of emoji This is one of those massive time sinks that I almost regret... As part of recent changes to dust-off the allsorts shaper, I noticed that the harfbuzz shaper wasn't shaping as well as the allsorts one. This commit: * Adds emoji-test.txt, a text file you can `cat` to see how well the emoji are shaped and rendered. * Fixes (or at least, improves) the column width calculation for combining sequences such as "deaf man" which was previously calculated at 3 cells in width when it should have just been 2 cells wide, which resulted in a weird "prismatic" effect during rendering where the glyph would be rendered with an extra RHS portion of the glyph across 3 cells. * Improved/simplified the clustering logic used to compute fallbacks. Previously we could end up with some wonky/disjoint sequence of undefined glyphs which wouldn't be successfully resolved from a fallback font. We now make a better effort to consolidate runs of undefined glyphs for fallback. * For sequences such as "woman with veil: dark skin tone" that occupy a single cell, the shaper may return 3 clusters with 3 glyphs in the case that the font doesn't fully support this grapheme. At render time we'd just take the last glyph from that sequence and render it, resulting in eg: a female symbol in this particular case. It is generally a bit more useful to show the first glyph in the sequence (eg: person with veil) rather than the gender or skin tone, so the renderer now checks for this kind of overlapping sequence and renders only the first glyph from the sequence.
2020-11-24 00:45:38 +03:00
unicode-segmentation = "1.7"
2019-05-28 06:08:02 +03:00
unicode-width = "0.1"
2020-12-29 20:21:50 +03:00
xi-unicode = "0.3"
vtparse = { version="0.4", path="../vtparse" }
[features]
widgets = ["cassowary", "fnv"]
use_serde = ["serde"]
docs = ["widgets", "use_serde"]
[dev-dependencies]
2019-05-28 05:44:55 +03:00
varbincode = "0.1"
pretty_assertions = "0.6"
[dependencies.num-derive]
features = ["full-syntax"]
2020-12-29 20:21:50 +03:00
version = "0.3"
[target."cfg(unix)".dependencies]
2019-05-28 06:08:02 +03:00
signal-hook = "0.1"
termios = "0.3"
[target."cfg(windows)".dependencies.winapi]
features = [
"winbase",
"winerror",
"winuser",
"consoleapi",
"handleapi",
"fileapi",
"synchapi",
]
2019-05-28 06:08:02 +03:00
version = "0.3"
[package.metadata.docs.rs]
features = ["docs"]
rustdoc-args = ["--cfg", "feature=\"docs\""]