how kitty images reach the terminal: auto (default) picks shm (shared memory) locally outside tmux, file (temp files) in tmux, direct (inline) over ssh. Change it only if images stay blank
--link-rate SIZE
bytes a second the ssh link is assumed to carry until measured, e.g. 20M; playback sending images inline is paced to the link (default 4M, 0: unpaced, unmeasured)
--terminal-cache SIZE
terminal image memory frames played over ssh may keep there, e.g. 512M: a loop’s second pass sends no pixels (default 256M, under kitty’s and Ghostty’s 320 MB; 0: off)
--cache SIZE
memory for decoded images, e.g. 8G or 512M (default 4G, at least 64M)
--chooser-file FILE
o in the browser writes the chosen paths to FILE and exits. See picking files
$XDG_CACHE_HOME and $XDG_STATE_HOME move them. They, and the log
(~/.cache/rega/rega.log, or $REGA_LOG), name the files viewed, so rega
creates them readable by their owner only.
1: for sites where images must stay on the machine holding them. rega refuses to run over ssh, where frames and copied text go to the terminal’s machine, and never copies to the terminal’s clipboard (in tmux, copies stay in tmux’s buffer)
REGA_MAX_MEGAPIXELS
the largest frame rega will load, in megapixels (default 1024); a file’s header can claim any size
LC_TERMINAL
names the terminal behind a tmux on the other side of ssh (ghostty, kitty): turns kitty graphics on there