wezterm/termwiz/Cargo.toml

[package]
authors = ["Wez Furlong"]
name = "termwiz"
version = "0.8.0"
edition = "2018"
repository = "https://github.com/wez/wezterm"
description = "Terminal Wizardry for Unix and Windows"
license = "MIT"
documentation = "https://docs.rs/termwiz"
keywords = ["terminal", "readline", "console", "curses"]
readme = "README.md"

[dependencies]
base64 = "0.10"
bitflags = "1.0"
cassowary = {version="0.3", optional=true}
anyhow = "1.0"
filedescriptor = { version="0.7", path = "../filedescriptor" }
fnv = {version="1.0", optional=true}
lazy_static = "1.3"
libc = "0.2"
log = "0.4"
memmem = "0.1"
num = "0.2"
num-traits = "0.2"
ordered-float = "1.0"
regex = "1"
semver = "0.9"
serde = {version="1.0", features = ["rc", "derive"]}
smallvec = "0.6"
terminfo = "0.7"
unicode-segmentation = "1.5"
unicode-width = "0.1"
xi-unicode = "0.2"
vtparse = { version="0.2", path="../vtparse" }

[features]
widgets = ["cassowary", "fnv"]

[dev-dependencies]
varbincode = "0.1"

[dependencies.num-derive]
features = ["full-syntax"]
version = "0.2"
[target."cfg(unix)".dependencies]
signal-hook = "0.1"
termios = "0.3"
[target."cfg(windows)".dependencies.winapi]
features = [
    "winbase",
    "winerror",
    "winuser",
    "consoleapi",
    "handleapi",
    "fileapi",
    "synchapi",
]
version = "0.3"
start building out the terminal model This is influenced by my code in wezterm 2018-07-12 17:26:37 +03:00			`[package]`
add some structs for holding image data 2018-08-07 07:54:17 +03:00			`authors = ["Wez Furlong"]`
start building out the terminal model This is influenced by my code in wezterm 2018-07-12 17:26:37 +03:00			`name = "termwiz"`
termwiz: allow using terminfo on Windows This commit changes the behavior on Windows: * If $TERM is set and the `terminfo` crate is able to successfully initialize and locate a terminfo database (this also requires that $TERMINFO be set in the environment), then we'll use the `TerminfoRenderer` instead of the `WindowsConsoleRenderer` * If $TERM is set to `xterm-256color` and no terminfo database was found, use our modern compiled-in copy (look in the `termwiz/data/` directory for the source and compiled version of this) and use the `TerminfoRenderer`. * Otherwise use the `WindowsConsoleRenderer`. In practice, this allows termwiz apps to opt in to features such as true color support on Windows 10 build 1903 an later by setting their `TERM=xterm-256color`. This happens to be the default behavior when `ssh`ing in to a windows host via `wezterm`. You can see the truecolor mode get applied by running this example: ``` cargo run --example widgets_basic --features widgets ``` with TERM set as above the background region that is painted by the app will be a blueish/purplish color, but with it unset or set to something invalid, it will fall back to black. I'd like to eventually make termwiz assume the equivalent configuration to `TERM=xterm-256color` by default on Windows 10 build 1903 and later, but it's worth getting some feedback on how this works for clients such as `streampager`. cc: @quark-zju and @markbt 2020-04-05 03:32:39 +03:00			`version = "0.8.0"`
update termwiz to 2018 edition 2019-02-19 10:26:41 +03:00			`edition = "2018"`
termwiz: prep for publishing on crates.io 2019-05-28 05:51:10 +03:00			`repository = "https://github.com/wez/wezterm"`
			`description = "Terminal Wizardry for Unix and Windows"`
			`license = "MIT"`
			`documentation = "https://docs.rs/termwiz"`
add keywords 2019-05-28 05:57:44 +03:00			`keywords = ["terminal", "readline", "console", "curses"]`
bump some deps 2019-05-28 06:08:02 +03:00			`readme = "README.md"`
start building out the terminal model This is influenced by my code in wezterm 2018-07-12 17:26:37 +03:00
			`[dependencies]`
bump some deps 2019-05-28 06:08:02 +03:00			`base64 = "0.10"`
			`bitflags = "1.0"`
prep termwiz for a new release Make the widgets portion a feature that can be disabled 2020-01-10 08:52:47 +03:00			`cassowary = {version="0.3", optional=true}`
failure -> anyhow + thiserror 2019-12-15 08:43:05 +03:00			`anyhow = "1.0"`
point to local filedescriptor crate 2020-01-26 20:14:26 +03:00			`filedescriptor = { version="0.7", path = "../filedescriptor" }`
prep termwiz for a new release Make the widgets portion a feature that can be disabled 2020-01-10 08:52:47 +03:00			`fnv = {version="1.0", optional=true}`
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 = "1.3"`
bump some deps 2019-05-28 06:08:02 +03:00			`libc = "0.2"`
more log 2019-06-09 01:37:55 +03:00			`log = "0.4"`
bump some deps 2019-05-28 06:08:02 +03:00			`memmem = "0.1"`
			`num = "0.2"`
			`num-traits = "0.2"`
			`ordered-float = "1.0"`
termwiz: bump regex to 1.0+ This makes termwiz (likely) use the same regex when being compiled together with other dependencies in the eco-system. 2020-02-04 18:52:23 +03:00			`regex = "1"`
IOError -> IoError, tidy up cargo deps 2018-07-24 15:45:24 +03:00			`semver = "0.9"`
serde_derive -> serde with derive feature 2020-01-03 20:22:17 +03:00			`serde = {version="1.0", features = ["rc", "derive"]}`
bump some deps 2019-05-28 06:08:02 +03:00			`smallvec = "0.6"`
bump some versions 2020-01-10 09:39:34 +03:00			`terminfo = "0.7"`
bump up to latest unicode segmentation crate 2019-11-05 09:12:21 +03:00			`unicode-segmentation = "1.5"`
bump some deps 2019-05-28 06:08:02 +03:00			`unicode-width = "0.1"`
improve emoji width calculation I noticed while scrolling `emoji-test.txt` that some of the combined emoji sequences rendered very poorly. This was due to the unicode width being reported as up to 4 in some cases. Digging into it, I discovered that the unicode width crate uses a standard calculation that doesn't take emoji combination sequences into account (see https://github.com/unicode-rs/unicode-width/issues/4). This commit takes a dep on the xi-unicode crate as a lightweight way to gain access to emoji tables and test whether a given grapheme is part of a combining sequence of emoji. 2019-11-05 19:45:08 +03:00			`xi-unicode = "0.2"`
bump vtparse version for publishing 2019-12-19 22:30:21 +03:00			`vtparse = { version="0.2", path="../vtparse" }`
Add a parser for terminal input This includes a trie structure for dealing with the keymap lookups. 2018-07-24 00:49:15 +03:00
prep termwiz for a new release Make the widgets portion a feature that can be disabled 2020-01-10 08:52:47 +03:00			`[features]`
			`widgets = ["cassowary", "fnv"]`

Enable serializing various Line and Cell related structs 2019-03-14 17:58:48 +03:00			`[dev-dependencies]`
moved varbincode to its own repo 2019-05-28 05:44:55 +03:00			`varbincode = "0.1"`
Enable serializing various Line and Cell related structs 2019-03-14 17:58:48 +03:00
Add a parser for terminal input This includes a trie structure for dealing with the keymap lookups. 2018-07-24 00:49:15 +03:00			`[dependencies.num-derive]`
			`features = ["full-syntax"]`
bump some deps 2019-05-28 06:08:02 +03:00			`version = "0.2"`
add some structs for holding image data 2018-08-07 07:54:17 +03:00			`[target."cfg(unix)".dependencies]`
bump some deps 2019-05-28 06:08:02 +03:00			`signal-hook = "0.1"`
			`termios = "0.3"`
add some structs for holding image data 2018-08-07 07:54:17 +03:00			`[target."cfg(windows)".dependencies.winapi]`
			`features = [`
add terminal wakers Terminal wakers allow other threads to wake the main terminal processing thread. 2019-04-28 19:31:35 +03:00			`"winbase",`
			`"winerror",`
add some structs for holding image data 2018-08-07 07:54:17 +03:00			`"winuser",`
			`"consoleapi",`
			`"handleapi",`
			`"fileapi",`
add terminal wakers Terminal wakers allow other threads to wake the main terminal processing thread. 2019-04-28 19:31:35 +03:00			`"synchapi",`
add some structs for holding image data 2018-08-07 07:54:17 +03:00			`]`
bump some deps 2019-05-28 06:08:02 +03:00			`version = "0.3"`