Skip to content

A modern terminal with a built-in multiplexer: close it and your sessions keep running. Run shells and tons of AI agents across your machines, then pick them up from desktop, browser, TUI and more. Written in Rust with no UI framework: interface drawn straight on the GPU. No Electron, GPUI or webview.

1.3 KB
Raw Blame

window-config-reloaded

{{since('20210314-114017-04b7cedd')}}

The window-config-reloaded event is emitted when the configuration for a window has been reloaded. This can occur when the configuration file is detected as changed (when automatically_reload_config is enabled), when the configuration is explicitly reloaded via the ReloadConfiguration key action, and when window:set_config_overrides is called for the window.

This event is fire-and-forget from the perspective of wezterm; it fires the event to advise of the config change, but has no other expectations.

If you call window:set_config_overrides from inside this event callback then an additional window-config-reloaded event will be triggered. You should take care to avoid creating a loop by only calling window:set_config_overrides when the actual override values are changed.

The first event parameter is a window object that represents the gui window.

The second event parameter is a pane object that represents the active pane in that window.

local wezterm = require 'wezterm'

wezterm.on('window-config-reloaded', function(window, pane)
  wezterm.log_info 'the config was reloaded for this window!'
end)