wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-12-25 22:33:52 +03:00
Code Issues Projects Releases Wiki Activity
a7d9cfd25f
wezterm/config/Cargo.toml

52 lines
1.4 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"
# 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: update env-logger Note that we are pinned on 0.10 for env-bootstrap, where we use it only for its module filter parser.
2024-01-21 02:01:10 +03:00
env_logger = "0.11"
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
add distro-defaults feature The intent is that when set, it changes defaults to something more suitable for distributions. I've also added a readme for distro maintainers. refs: https://github.com/wez/wezterm/issues/1795
2022-07-11 02:34:43 +03:00
[features]
distro-defaults = []
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"
deps: update Main thing to note here is that the open crate has deprecated open::that_in_background, but made open::that non-blocking. I think this is OK, but I'm a little cagey about what will happen with this on Windows. We may need to spawn our own thread for this if things go awry.
2022-06-13 06:17:48 +03:00
colorgrad = "0.6"
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" }
mlua 0.9 is now stable; update
2023-08-17 19:26:47 +03:00
mlua = {version="0.9", features=["vendored", "lua54", "async", "send"]}
move config into its own crate
2020-10-02 21:50:50 +03:00
# file change notification
cargo update
2022-09-04 04:54:36 +03:00
notify = "5.0.0"
build: revise dep graph for version changes Previously, the config crate would get rebuilt each time the git state changed, which has a lot of fan out and makes the build take longer than it really needs to. This commit breaks out the version changing stuff to its own crate and then provides a runtime mechanism for assigning the version information back into the config crate. The env-bootstrap crate is responsible for setting that up.
2023-04-09 02:51:31 +03:00
once_cell = "1.8"
deps: ordered-float -> 4.1.0 closes: https://github.com/wez/wezterm/pull/4338
2023-09-29 00:39:22 +03:00
ordered-float = { version = "4.1", 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"]}
color schemes: adjust sync aliasing * Change aliasing to exact matches of the color data. * Don't "GC" away schemes that are no longer reachable from aggregators; just because they are no longer listed elsewhere, doesn't mean that we should remove the name/scheme from wezterm if it was already made available in an earlier release. refs: #3831
2023-07-10 07:20:48 +03:00
serde_json = "1.0"
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"] }
deps: update toml 0.7 -> 0.8
2023-09-20 21:33:04 +03:00
toml = "0.8"
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: derive some metadata about the config This isn't used by anything yet, but will enable some runtime config editing functions that I have planeed for the future.
2022-09-22 03:42:43 +03:00
wezterm-config-derive = { version="0.1", path="derive" }
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" }
populate ssh domains from your ssh config by default If you haven't assigned `config.ssh_domains` to something else, this commit will populate it from the hosts it finds in your ssh config file. First it will emit no-multiplexing entries that allow ad-hoc ssh connections. Then it will emit wezterm multiplexing enabled versions of those entries.
2023-03-29 21:51:59 +03:00
wezterm-ssh = { path = "../wezterm-ssh" }
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
raise ulimit nofile and nproc to a reasonable min value on unix systems It's a tremendous PITA for the user to do this at the system level on a mac, where it is sorely needed. This commit allows raising to a desired minimum level, but won't decrease from an already larger soft limit. refs: https://github.com/wez/wezterm/discussions/3353
2023-03-28 17:29:47 +03:00
[target."cfg(unix)".dependencies]
nix = "0.26"
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