Files
nix-config/home/base/gui/terminal
Ryan Yin e4c2548a93 refactor: replace redundant mkForce with plain values and mkDefault
Each of these overrode a value nothing else set at a higher priority:

- qemu-guest: btrbk, hardwareTools and cloud-init have no competing
  definition on the guests.
- mdns: nixpkgs' sunshine module sets avahi.publish.* with mkDefault.
- computer-use: i18n now sets the time zone with mkDefault.
- darwin terminal: the shared ghostty/kitty font sizes are now mkDefault.
- shoukei: sunshine is mkDefault false in remote-desktop.nix, zram's
  memoryPercent is mkDefault 50; supportedFilesystems now merges instead
  of discarding the fsType entries other modules add.
- youko: nothing enables docker.
- nixpak: pasta.enable and sockets.pipewire are mkDefault in the shared
  modules, sockets.pulse already was.

Every NixOS host's toplevel drvPath is unchanged; on fern and frieren the
terminal font sizes and time zone evaluate to the same values.

Assisted-by: Claude Code (claude-opus-5-5)
2026-11-01 10:14:27 -06:00
..

Terminal Emulators

I used to spend a lot of time tweaking terminal emulators to match my taste. Now tuios gives me a consistent experience across all of them.

Currently, I only use the most basic features of terminal emulators, such as true color, graphics protocol, etc. Other features such as tabs, scrollback buffer, select/search/copy, etc, are all provided by tuios!

My current terminal emulators are:

  1. ghostty: My default terminal emulator, configured in ghostty.nix. Cross-platform, GPU-accelerated, and supports the Kitty graphics protocol.
  2. kitty: My secondary terminal emulator, configured in kitty.nix. Also supports the Kitty graphics protocol.

'xterm-kitty': unknown terminal type when ssh into a remote host or sudo xxx

https://sw.kovidgoyal.net/kitty/faq/#i-get-errors-about-the-terminal-being-unknown-or-opening-the-terminal-failing-or-functional-keys-like-arrow-keys-don-t-work

https://wezfurlong.org/wezterm/config/lua/config/term.html

kitty set TERM to xterm-kitty by default, and TUI apps like viu, yazi, curses will try to search in the host's terminfo(terminal capability data base) for value of TERM to determine the capabilities of the terminal.

But when you ssh into a remote host, the remote host is very likely to not have xterm-kitty in its terminfo, so you will get this error:

'xterm-kitty': unknown terminal type

Or when you sudo xxx, sudo won't preserve the TERM variable, it will be reset to root's default TERM value, which is xterm or xterm-256color in most linux distributions, so you will get this error:

'xterm-256color': unknown terminal type

or

Error opening terminal: xterm-kitty.

NixOS preserve the TERMINFO and TERMINFO_DIRS environment variables, for root and the wheel group: nixpkgs/nixos/modules/config/terminfo.nix

For nix-darwin, take a look at https://github.com/LnL7/nix-darwin/wiki/Terminfo-issues

Solutions

Simplest solution, it will automatically copy over the terminfo files and also magically enable shell integration on the remote machine:

kitten ssh user@host

Or if you do not care about kitty's features(such as true color & graphics protocol), you can simply set TERM to xterm-256color, which is built-in in most linux distributions:

export TERM=xterm-256color

If you need kitty's features, but do not like the magic of kitten, you can manually install kitty's terminfo on the remote host:

# install on ubuntu / debian
sudo apt-get install kitty-terminfo

# or copy from local machine
infocmp -a xterm-kitty | ssh myserver tic -x -o \~/.terminfo /dev/stdin