SshDomain¶
The SshDomain
struct specifies information about an individual
SSH Domain.
It is a lua object with the following fields:
config.ssh_domains = {
{
-- The name of this specific domain. Must be unique amongst
-- all types of domain in the configuration file.
name = 'my.server',
-- identifies the host:port pair of the remote server
-- Can be a DNS name or an IP address with an optional
-- ":port" on the end.
remote_address = '192.168.1.1',
-- Whether agent auth should be disabled.
-- Set to true to disable it.
-- no_agent_auth = false,
-- The username to use for authenticating with the remote host
username = 'yourusername',
-- If true, connect to this domain automatically at startup
-- connect_automatically = true,
-- Specify an alternative read timeout
-- timeout = 60,
-- The path to the wezterm binary on the remote host.
-- Primarily useful if it isn't installed in the $PATH
-- that is configure for ssh.
-- remote_wezterm_path = "/home/yourusername/bin/wezterm"
},
}
Since: Version 20220101-133340-7edc5b5a
The functionality described in this section requires version 20220101-133340-7edc5b5a of wezterm, or a more recent version.
You may now specify a table with ssh config overrides:
config.ssh_domains = {
{
name = 'my.server',
remote_address = '192.168.1.1',
ssh_option = {
identityfile = '/path/to/id_rsa.pub',
},
},
}
Since: Version 20220319-142410-0fcdea07
The functionality described in this section requires version 20220319-142410-0fcdea07 of wezterm, or a more recent version.
You may now specify the type of multiplexing
used by an ssh domain.
The following values are possible:
"WezTerm"
- this is the default; use wezterm's multiplexing client. Having wezterm installed on the server is required to use this mode."None"
- don't use any multiplexing. The connection is an ssh connection using the same mechanism as is used bywezterm ssh
; losing connectivity will lose any panes/tabs. This mode of operation is convenient when using SSH to connect automatically into eg: a locally hosted WSL instance, together with the default_domain option.
A new assume_shell
option, when coupled with multiplexing = "None"
, allows
wezterm to assume that the remote host uses a specific shell command language
dialect, which in turn allows wezterm to respect the
current working directory as set by OSC 7 / Shell
Integration on the remote host when spawning new
panes and tabs. The following values are recognized for assume_shell
:
"Unknown"
- this is the default. We can't make any assumptions about the remote shell."Posix"
- the remote host uses a POSIX/Bourne Shell compatible environment that allows the syntaxenv -c DIR ENV1=VAL1 ENV2=VAL2 CMD
andenv -c DIR ENV1=VAL1 ENV2=VAL2 $SHELL
.
config.ssh_domains = {
{
name = 'my.server',
remote_address = '192.168.1.1',
multiplexing = 'None',
-- When multiplexing == "None", default_prog can be used
-- to specify the default program to run in new tabs/panes.
-- Due to the way that ssh works, you cannot specify default_cwd,
-- but you could instead change your default_prog to put you
-- in a specific directory.
default_prog = { 'fish' },
-- assume that we can use syntax like:
-- "env -C /some/where $SHELL"
-- using whatever the default command shell is on this
-- remote host, so that shell integration will respect
-- the current directory on the remote host.
assume_shell = 'Posix',
},
}
config.default_domain = 'my.server'
You may now specify the round-trip latency threshold for enabling predictive
local echo using local_echo_threshold_ms
. If the measured round-trip latency
between the wezterm client and the server exceeds the specified threshold, the
client will attempt to predict the server's response to key events and echo the
result of that prediction locally without waiting, hence hiding latency to the
user. This option only applies when multiplexing = "WezTerm"
.
config.ssh_domains = {
{
name = 'my.server',
remote_address = '192.168.1.1',
local_echo_threshold_ms = 10,
},
}
Since: Version 20221119-145034-49b9839f
The functionality described in this section requires version 20221119-145034-49b9839f of wezterm, or a more recent version.
The lag indicator now defaults to disabled. It is recommended to display the lag information in your status bar using this example.
If you prefer to have the information overlaid on the content area, then
you can set overlay_lag_indicator = true
, but note that I'd like to
remove that functionality in the future.