wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-09-20 19:27:22 +03:00
Code Issues Projects Releases Wiki Activity
ecd05547d5
wezterm/config/Cargo.toml

44 lines
1.3 KiB
TOML
Raw Normal View History

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]
deps: remove pretty_env_loggger Go directly to the underlying env_logger crate, as pretty_env_logger hasn't been updated in some time, and I'd like to be able to redirect the log output to a file more directly, and that feature is in a newer version of the env logger than pretty_env_logger was pulling in.
2022-04-07 18:22:46 +03:00
env_logger = "0.9"
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
move config into its own crate
2020-10-02 21:50:50 +03:00
[dependencies]
anyhow = "1.0"
deps: update bitflags -> 1.3
2021-08-16 04:21:17 +03:00
bitflags = "1.3"
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: colorgrad -> 0.5
2021-09-06 09:27:01 +03:00
colorgrad = "0.5"
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
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" }
Add cycle detection when converting lua values to dynamic
2022-05-18 07:53:36 +03:00
mlua = {version="0.8.0-beta.4", 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"
deps: ordered-float closes: https://github.com/wez/wezterm/pull/1946
2022-05-02 07:43:22 +03:00
ordered-float = { version = "3.0", features = ["serde"] }
move config into its own crate
2020-10-02 21:50:50 +03:00
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"]}
introduce quote_dropped_files config option Signed-off-by: Ye Sijun <junnplus@gmail.com>
2022-04-25 09:31:33 +03:00
shlex = "1.1"
wezterm.run_child_process is now async capable
2020-10-07 18:51:54 +03:00
smol = "1.2"
allow setting selection colors with alpha values This commit allows the following configuration: ``` wezterm -n --config 'colors = { selection_fg = "clear", selection_bg = "rgba:50% 50% 50% 50%" }' ``` which sets the selection_bg to fully transparent, and selection_bg to 50% transparent gray. When selection_fg is fully transparent we'll use the normal fg color. When selection_bg is partially (or fully!) transparent, it will be alpha blended over the current cell background color. To support this, the config file will now accept rgba colors specified as 4 whitespace delimited numeric values. If a value ends with `%` it is interpreted as a number in the range 0-100. Otherwise, it is interpreted as a number in the range 0-255. The 4 values are red, green, blue, alpha. At this time, only the selection_fg and selection_bg settings accept alpha values. refs: #1615
2022-02-06 01:13:19 +03:00
termwiz = { path = "../termwiz", features=["use_serde"] }
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" }
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" }
remove serde from bidi
2022-05-18 19:25:41 +03:00
wezterm-bidi = { path = "../bidi" }
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"]}
Reference in New Issue Copy Permalink