wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-11-28 01:06:37 +03:00
Code Issues Projects Releases Wiki Activity
ee1c335703
wezterm/Cargo.toml

112 lines
2.5 KiB
TOML
Raw Normal View History

Render text on sdl using harfbuzz and freetype
2018-01-15 10:34:59 +03:00
[package]
authors = ["Wez Furlong <wez@wezfurlong.org>"]
there's already a wterm, rename to wezterm
2018-01-29 10:52:21 +03:00
name = "wezterm"
Render text on sdl using harfbuzz and freetype
2018-01-15 10:34:59 +03:00
version = "0.1.0"
migrate wezterm to 2018 edition
2019-02-19 10:10:37 +03:00
edition = "2018"
use vergen to embed the git version info in the output
2019-03-24 09:45:14 +03:00
build = "build.rs"
[build-dependencies]
vergen = "3"
Render text on sdl using harfbuzz and freetype
2018-01-15 10:34:59 +03:00
Embed icon into windows executable and titlebar This also applies to X11 when using the glutin frontend
2019-03-25 05:06:03 +03:00
[target.'cfg(windows)'.build-dependencies]
windows: bump embed-resource version
2019-11-04 19:00:58 +03:00
embed-resource = "1.3"
Embed icon into windows executable and titlebar This also applies to X11 when using the glutin frontend
2019-03-25 05:06:03 +03:00
Render text on sdl using harfbuzz and freetype
2018-01-15 10:34:59 +03:00
[dependencies]
fonts: add a basic font parse using allsorts Refs: https://github.com/wez/wezterm/issues/66
2019-12-10 05:08:02 +03:00
allsorts = "0.1"
adopt async-task for muxserver task runner This simplifies some of its code
2020-01-16 12:03:32 +03:00
async-task = "1.2"
mux: make Domain::attach an async fn
2020-01-17 02:55:15 +03:00
async-trait = "0.1"
failure -> anyhow + thiserror
2019-12-15 08:43:05 +03:00
anyhow = "1.0"
thiserror = "1.0"
add support for unix mux via ssh This adds an ssh domain config type that allows us to ssh to a remote host and then proxy the unix domain mux protocol over the ssh session.
2019-07-29 02:15:44 +03:00
base64 = "0.10"
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
base91 = { path = "base91" }
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
rangeset = { path = "rangeset" }
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
bitflags = "1.0"
re-structure client in readiness for unilateral responses
2019-06-17 04:41:57 +03:00
crossbeam-channel = "0.3"
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
dirs = "1.0"
add Downcast trait to FrontEnd This removes some awkwardness in the impl by allowing casting to a concrete implementation. This is a pattern I want to use more widely and this diff proves the concept.
2019-06-09 21:10:07 +03:00
downcast-rs = "1.0"
upgrade euclid dep
2019-09-21 22:32:21 +03:00
euclid = "0.20"
fix pollable_channel to be non-blocking on Windows Upgrade filedescriptor to 0.7 to use the portable helper for setting non-blocking mode, and enable non-blocking mode on Windows.
2020-01-16 08:30:14 +03:00
filedescriptor = "0.7"
more log changes
2019-06-09 01:30:47 +03:00
pretty_env_logger = "0.3"
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
failure = "0.1"
failure_derive = "0.1"
Build our own freetype, harfbuzz This is primarily for macos where the default freetype installation is unable to render color emoji, but should also help make things more consistent across the various platforms. It's a little bit awkward on linux because the font-loader crate pulls in the now-conflicting servo-font* crates. I've disabled font-loader on linux systems; it's just calling fontconfig under the covers anyway.
2019-03-23 19:28:40 +03:00
freetype = { path = "deps/freetype" }
render iterm2 image protocol in the software renderer This is still a bit rough because the terminal parser doesn't understand the pixel sizes, so it relies on the hard coded cell dimensions being accurate.
2019-10-27 09:30:39 +03:00
image = "0.21"
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
harfbuzz = { path = "deps/harfbuzz" }
lazy_static = "1.3"
leb128 = "0.2"
libc = "0.2"
adopt log and env_logger for logging
2019-06-09 01:17:41 +03:00
log = "0.4"
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
lru = "0.4"
use the `open` crate for url clicking
2019-02-19 09:57:40 +03:00
open = "1.2"
instrument painting and rpc calls
2020-01-04 12:21:51 +03:00
metrics = { version="0.12", features=["std"]}
hdrhistogram = "6.3"
add basic tls listener We don't yet have a client that knows how to connect to it
2019-06-14 08:21:17 +03:00
native-tls = "0.2"
add basic notifications if the config is broken during reload
2019-12-05 05:26:47 +03:00
# file change notification
automatically reload config when the file changes
2019-11-25 06:20:14 +03:00
notify = "4.0"
bump some versions
2020-01-10 09:39:34 +03:00
palette = "0.5"
allow direct ssh pty This basically works, but I want to tidy up how we enable this kind of connection; right now its a bit of a hack.
2019-08-03 22:47:55 +03:00
portable-pty = { path = "pty", features = ["serde_support", "ssh"]}
move promise to its own crate
2019-03-04 18:38:56 +03:00
promise = { path = "promise" }
fix an issue with rate limiting data from the child pty We need to chunk the data that we read from the child otherwise we may potentially try to admit more data in a single action than the ratelimiter will ever allow (eg: if we read 4k of data and the limit is 100 bytes per second, we can never send that 4k of data in a single write). Our handling of that situation was not good: we'd panic and kill the background thread that was reading the data, but the rest of the app was still running. This commit upgrades to the most recent rate limiter crate and performs explicit chunking of the output so that we behave more sanely. Refs: https://github.com/wez/wezterm/issues/65
2019-11-21 19:36:16 +03:00
ratelimit_meter = "5.0"
serde_derive -> serde with derive feature
2020-01-03 20:22:17 +03:00
serde = {version="1.0", features = ["rc", "derive"]}
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"
update ssh2 dep
2019-12-08 21:43:55 +03:00
ssh2 = "0.6"
avoid use of a fork of structopt just for vergen compat This is much simpler! Clean up some of the attributes while I'm in here. refs: https://github.com/TeXitoi/structopt/issues/209
2019-06-27 17:21:59 +03:00
structopt = "0.2"
add cli command to list tabs
2019-06-14 01:00:57 +03:00
tabout = { path = "tabout" }
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
term = { path = "term" }
termwiz = { path = "termwiz"}
Show a window with the full error message for failed config load This is a very basic first approximation for the feature discussed in the associated github issue. Refs: https://github.com/wez/wezterm/issues/80
2020-01-18 05:40:40 +03:00
textwrap = "0.11"
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
toml = "0.4"
unicode-normalization = "0.1"
Add optional basic tab UI at the top of the window This is a little ghetto feeling because we're just stealing the top line from the terminal model, rather than rendering anything particularly native, but it is relatively quick and easy to do, and helps improve the feel when using wezterm on a chromebook inside crostini; in that environment, the system doesn't render any text in the window titlebars (WTF!?) so it is desirable to show something to help navigate the UI. The tab bar is off by default for now; we'll definitely want to add options to configure at least the colors, and perhaps add a keybinding to toggle it at runtime. ``` enable_tab_bar = true ``` While adding support for the tab bar, I found a couple of little bugs relating to computing the number of rows and columns; one was during resize where we'd use the prior size instead of the current size. Another was during tab spawning where we'd use a slightly different calculation to determine the size and end up raising an error about being confused about the screen size.
2019-11-21 08:52:56 +03:00
unicode-segmentation = "1.5"
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
unicode-width = "0.1"
track the full current dir URL for OSC 7 Matching against the current dir when it includes a host and a path seems like a handy way to automate selecting appropriate theme/color/profile settings, so I'd like to make sure that we have the full URL content available for that. Refs: https://github.com/wez/wezterm/issues/115 Refs: https://github.com/wez/wezterm/issues/117
2020-01-15 09:06:13 +03:00
url = "2"
moved varbincode to its own repo
2019-05-28 05:44:55 +03:00
varbincode = "0.1"
font-kit: add font_dirs configuration option This is another option to help with the portable wezterm on a flash drive use case. When the font system is set to FontKitAndFreeType, the set of directories specified by the `font_dirs` configuration option will be scanned for fonts and used as a source for fonts. In addition, any relative paths in the the `font_dirs` list will be expanded relative to the configuration file path. That allows deploying the following set of files to the root of a flash drive: * wezterm.exe * wezterm.toml * fonts/myfont.ttf and with this config snippet: ``` font_system = "FontKitAndFreeType" font_dir = ["fonts"] ``` wezterm will now consider myfont.ttf when loading fonts. Refs: https://github.com/wez/wezterm/issues/73
2019-12-09 03:34:17 +03:00
walkdir = "2"
window: wayland: input mostly working, and hidpi output Some key mappings are not done yet (arrows!) and need to make opengl work, but this can run a basic wezterm with the software renderer under wayland.
2019-11-28 09:00:44 +03:00
window = { path = "window", features=["opengl", "wayland"]}
Employ zstd compression for large pdus This cuts down the coarse data from ~13k to ~200 bytes
2019-03-16 20:04:41 +03:00
zstd = "0.4"
move term to its own crate This makes it harder to accidentally violate separation of concerns.
2018-01-31 21:38:33 +03:00
make harfbuzz dep optional
2019-02-17 23:55:02 +03:00
[target.'cfg(unix)'.dependencies]
Workaround daemonize bug refs: https://github.com/knsd/daemonize/pull/39
2020-01-06 07:55:28 +03:00
daemonize = { git = "https://github.com/wez/daemonize" }
make harfbuzz dep optional
2019-02-17 23:55:02 +03:00
add basic notifications if the config is broken during reload
2019-12-05 05:26:47 +03:00
[target.'cfg(not(windows))'.dependencies]
# show a notification
downrev notify-rust dependency SOmething on the CI doesn't like it and it looks like a problem with that alpha version, so let's go back to their stable rev.
2019-12-05 07:40:32 +03:00
notify-rust = "3"
add basic notifications if the config is broken during reload
2019-12-05 05:26:47 +03:00
Build our own freetype, harfbuzz This is primarily for macos where the default freetype installation is unable to render color emoji, but should also help make things more consistent across the various platforms. It's a little bit awkward on linux because the font-loader crate pulls in the now-conflicting servo-font* crates. I've disabled font-loader on linux systems; it's just calling fontconfig under the covers anyway.
2019-03-23 19:28:40 +03:00
# on linux, font-loader pulls in servo-font* crates which conflict with
# our newer font related deps, so we avoid it on linux
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
[target.'cfg(any(windows, target_os = "macos"))'.dependencies]
font-loader = { version = "0.8" }
font-kit: enable its use on macos FontKit is still broken, but FontKitAndFreeType works
2019-12-09 04:51:01 +03:00
font-kit = "0.5"
add very bare bones skeleton for unix domain socket bits
2019-03-03 16:08:58 +03:00
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
[target."cfg(windows)".dependencies]
fonts: allow using font-kit as a source for fonts This commit adds two new font system variants that are currently implemented only on Windows: * FontKit - uses fontkit both for font discovery and rasterizing * FontKitAndFreeType - uses fontkit for font discovery but freetype for rasterizing To a certain extent, FontKitAndFreeType obsoletes FontLoaderAndFreeType and I'll be looking at removing it once I can test the build on macOS. The FontKit impl has bad metrics and also crashes during shaping on Windows, so it's not ready to be used by default.
2019-12-09 03:02:04 +03:00
dwrote = "0.9"
dynamically load conpty functions on windows This allows travis to build and run tests, even though it can't run the full gui.
2019-03-24 03:07:10 +03:00
shared_library = "0.1"
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
uds_windows = "0.1"
winapi = { version = "0.3", features = [
flesh out some of the windows pty impl
2019-02-17 10:36:50 +03:00
"winuser",
"consoleapi",
"handleapi",
"fileapi",
"namedpipeapi",
fixup windows build
2019-03-03 00:16:25 +03:00
"synchapi",
re-structure client in readiness for unilateral responses
2019-06-17 04:41:57 +03:00
"winsock2",
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
]}
Windows: show toast notification if config reload encounters error This gives us a way to show notifs on windows, which is a feature that isn't supported by the notify-rust crate.
2019-12-08 22:14:02 +03:00
winrt-notification = "0.2"
start integrating rusttype and font_loader for windows
2019-02-17 03:15:39 +03:00
build our own harfbuzz for broader compat
2018-02-20 23:33:30 +03:00
[target.'cfg(any(target_os = "android", all(unix, not(target_os = "macos"))))'.dependencies]
Build our own freetype, harfbuzz This is primarily for macos where the default freetype installation is unable to render color emoji, but should also help make things more consistent across the various platforms. It's a little bit awkward on linux because the font-loader crate pulls in the now-conflicting servo-font* crates. I've disabled font-loader on linux systems; it's just calling fontconfig under the covers anyway.
2019-03-23 19:28:40 +03:00
fontconfig = { path = "deps/fontconfig" }
build our own harfbuzz for broader compat
2018-02-20 23:33:30 +03:00
tidy up the cargo manifest
2019-03-23 23:57:26 +03:00
[target.'cfg(all(unix, not(target_os = "macos")))'.dependencies]
try harder to get openssl vendoring right
2019-06-23 00:28:52 +03:00
openssl = "0.10"
fix an issue with CR processing This eliminates the zsh reversed % artifact issue. Added a feature flag to turn on diagnostics even in release mode; `cargo run --release --features debug-escape-sequences`
2018-02-01 06:00:15 +03:00
stubs for macos font loading
2018-02-21 09:33:09 +03:00
[target.'cfg(target_os = "macos")'.dependencies]
try harder to get openssl vendoring right
2019-06-23 00:28:52 +03:00
openssl = { version = "0.10", features = ["vendored"] }
remove local workaround for core-foundation UB issue My fixes landed upstream in https://github.com/servo/core-foundation-rs/commit/0a3ac83c1bb38d30a4d30530cd233385b7410b2c and are released already to crates.io
2019-11-13 11:05:55 +03:00
core-foundation = "0.7"
core-graphics = "0.19"
core-text = "15.0"
stubs for macos font loading
2018-02-21 09:33:09 +03:00
Add basic config file parsing So that we no longer assume Operator Mono SSm. We now default to `monospace`. I just tried this and the font metrics appear to be wonky, so there's some tweaking to do.
2018-02-07 18:51:04 +03:00
[workspace]
enable debug symbols in release builds
2019-02-23 07:59:03 +03:00
[profile.release]
add basic simd support for clearing rectangles
2019-09-30 04:59:42 +03:00
opt-level = 3
Reference in New Issue Copy Permalink