Skip to content

Remote Hosts

Ö. Efe D. edited this page Sep 15, 2026 · 1 revision

Remote Hosts

tron sets TERM=xterm-tron. That terminfo entry describes tron's features: true color, styled underlines, synchronized output, bracketed paste, focus events and more. Remote systems rarely have it, and programs there fail with errors like 'xterm-tron': unknown terminal type.

ssh: handled for you

tron puts a small ssh wrapper first in the shell's PATH. Before the first interactive session to a host:

  1. The wrapper copies the terminfo entry to ~/.terminfo on the host with tic.
  2. It opens your session over the same connection, so you authenticate only once.
  3. It remembers the host in ssh-terminfo-hosts in tron's data directory (~/.local/share/tron on Linux), so later sessions skip the copy.

Hosts without tic, and non-interactive uses like scp or ssh host command, get TERM=xterm-256color instead. Nothing in ~/.ssh/config changes.

docker, sudo and others

Tools that carry TERM into another system, such as docker exec, sudo into a minimal system or a container, still need the entry. Copy it once:

infocmp -x xterm-tron | ssh host 'mkdir -p ~/.terminfo && tic -x -o ~/.terminfo /dev/stdin'

For a container:

infocmp -x xterm-tron > xterm-tron.terminfo
docker cp xterm-tron.terminfo container:/tmp/
docker exec container tic -x -o /usr/share/terminfo /tmp/xterm-tron.terminfo

Or run the tool with a common entry: TERM=xterm-256color docker exec -it container bash.

Using xterm-256color everywhere

To skip the tron entry altogether:

[shell]
term = "xterm-256color"

Programs then see a plain xterm and may not use tron's extra features, such as styled underlines.

Local terminfo

tron compiles its terminfo entry with tic into its data directory once per version and points TERMINFO_DIRS at it, so local programs always find it. Install tic (package ncurses or ncurses-bin) if programs report that xterm-tron is unknown on your own machine.

Clone this wiki locally