wezterm/config/Cargo.toml

[package]
name = "config"
version = "0.1.0"
authors = ["Wez Furlong <wez@wezfurlong.org>"]
edition = "2018"
build = "build.rs"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dev-dependencies]
pretty_env_logger = "0.4"

[dependencies]
anyhow = "1.0"
battery = "0.7"
bitflags = "1.0"
bstr = "0.2"
chrono = {version="0.4", features=["unstable-locales"]}
dirs-next = "2.0"
enum-display-derive = "0.1"
filenamegen = "0.2"
hostname = "0.3"
lazy_static = "1.4"
libc = "0.2"
log = "0.4"
luahelper = { path = "../luahelper" }
mlua = {version="0.5", features=["vendored", "lua54", "async", "send"]}
# file change notification
notify = "4.0"
portable-pty = { path = "../pty", features = ["serde_support"]}
promise = { path = "../promise" }
serde = {version="1.0", features = ["rc", "derive"]}
serde_json = "1.0"
smol = "1.2"
terminfo = "0.7"
termwiz = { path = "../termwiz" }
toml = "0.5"
umask = { path = "../umask" }
unicode-segmentation = "1.7"
wezterm-input-types = { path = "../wezterm-input-types" }
wezterm-term = { path = "../term", features=["use_serde"] }

[target."cfg(windows)".dependencies]
winapi = { version = "0.3", features = ["winuser"]}
move config into its own crate 2020-10-02 21:50:50 +03:00			`[package]`
			`name = "config"`
			`version = "0.1.0"`
			`authors = ["Wez Furlong <wez@wezfurlong.org>"]`
			`edition = "2018"`
			`build = "build.rs"`

			`# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html`

add wezterm.on(), wezterm.emit() * `wezterm.on("event-name", func)` * `wezterm.emit("event-name", "arg1", "arg2")` `on` allows registering multiple functions. `emit` will call each of the registered functions in turn, passing a copy of the arguments. If a handler returns false, no additional handlers are called and `emit` will return false. Otherwise, once all the handlers have been called, `emit` will return true. `emit` is capable of being called by async code. These functions are available to the config layer, but nothing in wezterm uses them at this time. refs: #225 2020-10-07 08:04:48 +03:00			`[dev-dependencies]`
			`pretty_env_logger = "0.4"`

move config into its own crate 2020-10-02 21:50:50 +03:00			`[dependencies]`
			`anyhow = "1.0"`
lua: add `wezterm.battery_info()` function Queries the system battery information and returns an array of battery information. Each element is a lua table with the following entries: * state_of_charge: expressed as percents * vendor: the battery manufacturer * model: the battery model * serial: the battery serial number * time_to_full: how long until the battery is full * time_to_empty: how long until the battery is empty * state: "Charging", "Discharging", "Empty", "Full", "Unknown" I haven't run this on a system with a battery yet, so I'm holding off from showing an example until I've got a work one. refs: https://github.com/wez/wezterm/issues/500 2021-03-07 01:25:36 +03:00			`battery = "0.7"`
introduce freetype_load_flags and freetype_load_target config In the earlier times wezterm supported different font rasterizers, and the configuration was a bit vague and generic to accomodate differences in how the rasterizers worked. Since then, we've standardized on freetype. One of the things that's been bothering me for a while is that we have some fiddly logic to transform from the config to the freetype flags. This commit does away with the transformation and simply exposes the two sets of freetype options. The main thing that I expect people to play with is `freetype_load_target` which can have one of the following values: ``` pub enum FreeTypeLoadTarget { /// This corresponds to the default hinting algorithm, optimized for standard gray-level rendering. Normal, /// A lighter hinting algorithm for non-monochrome modes. Many generated glyphs are more fuzzy but better resemble its original shape. A bit like rendering on Mac OS X. This target implies FT_LOAD_FORCE_AUTOHINT. Light, /// Strong hinting algorithm that should only be used for monochrome output. The result is probably unpleasant if the glyph is rendered in non-monochrome modes. Mono, /// A variant of Normal optimized for horizontally decimated LCD displays. HorizontalLcd, /// A variant of Normal optimized for vertically decimated LCD displays. VerticalLcd, } ``` I expect most people will want to set this to one of `Normal`, `Light` or `HorizontalLcd`. `HorizontalLcd` is what `font_antialias=Subpixel` used to select. refs: #491 2021-02-21 00:54:56 +03:00			`bitflags = "1.0"`
clean up mux server startup kindof a lot going on in this commit, unintentionally: * Need the lua context set to be moved into the config crate otherwise configs cannot be parsed by the server and we end up with the default configs * Make the server use smol for async io * Drop the use of the daemonize crate, which I had forked anyway. Just inline our own tighter daemonize module * Improve daemon spawning synchronization, however, it still needs work for windows to avoid blocking forever where we don't do daemonizing. 2020-10-04 19:39:28 +03:00			`bstr = "0.2"`
lua: add wezterm.strftime refs: https://github.com/wez/wezterm/issues/500 2021-03-02 20:51:56 +03:00			`chrono = {version="0.4", features=["unstable-locales"]}`
deps: dirs -> dirs_next I saw that former is unmaintained, and dependabot wants to upgrade that one. 2020-12-10 21:08:49 +03:00			`dirs-next = "2.0"`
Allow matching font weight and font width in `wezterm.font` refs: https://github.com/wez/wezterm/issues/655 2021-04-09 01:41:07 +03:00			`enum-display-derive = "0.1"`
clean up mux server startup kindof a lot going on in this commit, unintentionally: * Need the lua context set to be moved into the config crate otherwise configs cannot be parsed by the server and we end up with the default configs * Make the server use smol for async io * Drop the use of the daemonize crate, which I had forked anyway. Just inline our own tighter daemonize module * Improve daemon spawning synchronization, however, it still needs work for windows to avoid blocking forever where we don't do daemonizing. 2020-10-04 19:39:28 +03:00			`filenamegen = "0.2"`
			`hostname = "0.3"`
move config into its own crate 2020-10-02 21:50:50 +03:00			`lazy_static = "1.4"`
move running_under_wsl to config crate 2020-10-03 06:51:50 +03:00			`libc = "0.2"`
move config into its own crate 2020-10-02 21:50:50 +03:00			`log = "0.4"`
extract window::input to wezterm-input-types 2020-12-10 00:00:23 +03:00			`luahelper = { path = "../luahelper" }`
deps: update to mlua 0.5 2021-01-13 21:06:35 +03:00			`mlua = {version="0.5", features=["vendored", "lua54", "async", "send"]}`
move config into its own crate 2020-10-02 21:50:50 +03:00			`# file change notification`
			`notify = "4.0"`
			`portable-pty = { path = "../pty", features = ["serde_support"]}`
extract window::input to wezterm-input-types 2020-12-10 00:00:23 +03:00			`promise = { path = "../promise" }`
move config into its own crate 2020-10-02 21:50:50 +03:00			`serde = {version="1.0", features = ["rc", "derive"]}`
add window:set_config_overrides lua method This commit expands on the prior commits to introduce the concept of per-window configuration overrides. Each TermWindow maintains json compatible object value holding a map of config key -> config value overrides. When the window notices that the config has changed, the config file is loaded, the CLI overrides (if any) are applied, and then finally the per-window overrides, before attempting to coerce the resultant lua value into a Config object. This mechanism has some important constraints: * Only data can be assigned to the overrides. Closures or special lua userdata object handles are not permitted. This is because the lifetime of those objects is tied to the lua context in which they were parsed, which doesn't really exist in the context of the window. * Only simple keys are supported for the per-window overrides. That means that trying to override a very specific field of a deeply structured value (eg: something like `font_rules[1].italic = false` isn't able to be expressed in this scheme. Instead, you would need to assign the entire `font_rules` key. I don't anticipate this being a common desire at this time; if more advance manipulations are required, then I have some thoughts on an event where arbitrary lua modifications can be applied. The implementation details are fairly straight-forward, but in testing the two examplary use cases I noticed that some hangovers from supporting overrides for a couple of font related options meant that the window-specific config wasn't being honored. I've removed the code that handled those overrides in favor of the newer more general CLI option override support, and threaded the config through to the font code. closes: #469 closes: #329 2021-02-28 01:53:19 +03:00			`serde_json = "1.0"`
wezterm.run_child_process is now async capable 2020-10-07 18:51:54 +03:00			`smol = "1.2"`
lua: add wezterm.format function The intent is to use this to compose text for a configurable tab bar. refs: https://github.com/wez/wezterm/issues/500 2021-03-02 11:15:37 +03:00			`terminfo = "0.7"`
move config into its own crate 2020-10-02 21:50:50 +03:00			`termwiz = { path = "../termwiz" }`
upgrade misc deps, notably, async-task 2020-10-05 10:06:01 +03:00			`toml = "0.5"`
Take care to restore the original umask wezterm sets a more restrictive umask (`0o077`) by default so that any files that it creates (eg: unix domain socket, log files) are more secure by default. However, some environments rely on the more general default of (`0o022`) without checking that it is set. This matters because programs spawned by wezterm inherit its more restricted umask. I hadn't noticed this because I've had `umask 022` in my shell RC files since sometime in the 1990's. This commit adds some plumbing to the pty layer to specify an optional umask for the child process, and some more to our umask saver helper so that any thread can determine the saved umask without needing a reference to the saver itself, which may be in a different crate. The logic in the config crate has been adjusted to connect the saved value to the default command builder arguments. The net result of this is that running `wezterm -n start bash -- --norc` and typing `umask` in the resultant window now prints `0022`. refs: #416 2021-01-07 20:14:51 +03:00			`umask = { path = "../umask" }`
add wezterm.truncate_to_width refs: https://github.com/wez/wezterm/issues/647 2021-04-27 08:25:52 +03:00			`unicode-segmentation = "1.7"`
extract window::input to wezterm-input-types 2020-12-10 00:00:23 +03:00			`wezterm-input-types = { path = "../wezterm-input-types" }`
move config into its own crate 2020-10-02 21:50:50 +03:00			`wezterm-term = { path = "../term", features=["use_serde"] }`
maybe fixup build for windows 2020-10-05 21:57:08 +03:00
			`[target."cfg(windows)".dependencies]`
			`winapi = { version = "0.3", features = ["winuser"]}`