wez/wezterm
1
1
Fork 0
mirror of https://github.com/wez/wezterm.git synced 2024-12-26 14:54:16 +03:00
Code Issues Projects Releases Wiki Activity
9029b3bca6
wezterm/env-bootstrap/Cargo.toml

39 lines
1.2 KiB
TOML
Raw Normal View History

wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
[package]
name = "env-bootstrap"
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
[dependencies]
capture panic backtrace to log file
2022-04-28 00:47:28 +03:00
backtrace = "0.3"
add debug overlay Adds a `ShowDebugOverlay` key assignment that will create a tab overlay that shows a limited number of recently logged events. refs: https://github.com/wez/wezterm/issues/641
2021-05-03 06:50:01 +03:00
chrono = {version="0.4", features=["unstable-locales"]}
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
config = { path = "../config" }
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"
add debug overlay Adds a `ShowDebugOverlay` key assignment that will create a tab overlay that shows a limited number of recently logged events. refs: https://github.com/wez/wezterm/issues/641
2021-05-03 06:50:01 +03:00
lazy_static = "1.4"
on windows, log to C:\Users\USER\.local/share/wezterm/gui-log-PID.txt refs: #1576
2022-03-18 02:52:35 +03:00
libc = "0.2"
use $WEZTERM_LOG to configure log levels ad-hoc 80214319aec9d7b72217db3d7a6f8e8575081eac broke the use of RUST_LOG to turn up trace logging. This commit refactors logger initialization into the env-bootstrap crate so that it is centralized, and adopts the use of `WEZTERM_LOG` to override the default logging filters, rather than `RUST_LOG`.
2020-12-23 23:14:01 +03:00
log = "0.4"
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"
logging: use our own custom logger I wanted to use the Target::Pipe feature of env_logger so that we could log to a log file as well as stderr, but it just doesn't work (https://github.com/env-logger-rs/env_logger/issues/208). Since we were already composing over the top of the logger in order to capture data for our ringlog, this commit embraces that and makes our logger responsible for both stderr and log file printing. Thankfully, we can use the filter parsing code from env_logger to avoid having to get too crazy with this. Logs are stored in the runtime directory and look something like: /run/user/1000/wezterm/wezterm-gui-log-596324.txt Logs are collected on all platforms. There isn't currently a thing to clean up logs.
2022-04-07 19:51:00 +03:00
termwiz = { path = "../termwiz" }
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
battery = { path = "../lua-api-crates/battery" }
add wezterm.color module for working with colors wezterm.color.parse() returns a color object that can be assigned in the wezterm color config, and that can be used to adjust hue, saturation and lightness, as well as calculate harmonizing colors (complements, triads, squares) from the RGB/HSL color wheel.
2022-07-11 09:41:18 +03:00
color-funcs = { path = "../lua-api-crates/color-funcs" }
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
termwiz-funcs = { path = "../lua-api-crates/termwiz-funcs" }
logging = { path = "../lua-api-crates/logging" }
add wezterm.mux lua module The intent is to expose Mux related functions to lua, so `wezterm.mux` will be that module table. In order to test this out in the debug overlay, I realized that the overlay was running functions in a different thread and didn't have access to the mux, so this commit also tweaks the debug overlay repl to execute the input in the main thread. The result is that it is now possible to do `wezterm.mux.active_workspace()` in the debug overlay to print the active workspace name. More functions will follow. refs: https://github.com/wez/wezterm/issues/225
2022-06-17 17:46:25 +03:00
mux-lua = { path = "../lua-api-crates/mux" }
lua: add wezterm.procinfo module
2022-07-16 18:49:58 +03:00
procinfo-funcs = { path = "../lua-api-crates/procinfo-funcs" }
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
filesystem = { path = "../lua-api-crates/filesystem" }
add wezterm.json_parse and wezterm.json_encode
2022-07-10 19:30:54 +03:00
json = { path = "../lua-api-crates/json" }
lua: add wezterm.GLOBAL
2022-06-19 07:31:53 +03:00
share-data = { path = "../lua-api-crates/share-data" }
config: split out lua functions into their own crates This shaves off some build time and allows more parallism in the build.
2022-05-19 08:49:53 +03:00
ssh-funcs = { path = "../lua-api-crates/ssh-funcs" }
spawn-funcs = { path = "../lua-api-crates/spawn-funcs" }
lua: add wezterm.time and Time object Includes a method for determining sunrise/sunset.
2022-07-17 21:38:02 +03:00
time-funcs = { path = "../lua-api-crates/time-funcs" }
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
windows: workaround Rust 1.56 bug 88576 Skip initializing pretty logger when running in the windows subsystem. refs: https://github.com/wez/wezterm/issues/1245 refs: https://github.com/rust-lang/rust/issues/88576
2021-10-24 21:44:55 +03:00
[target."cfg(windows)".dependencies]
winapi = "0.3"
wezterm: fixup APPIMAGE environment consistently Need to apply the same logic in wezterm-gui as we do in the wezterm-cli.
2020-10-25 09:21:03 +03:00
[target.'cfg(target_os = "macos")'.dependencies]
cocoa = "0.20"
objc = "0.2"
Reference in New Issue Copy Permalink