Hacker News Reader

Comment by flatiron | Hacker News Reader

1) kitty +kitten ssh myserver

That solves that.

FWIW that doesn't copy user capabilities; for that use:

  infocmp -x xterm-kitty | ssh myserver tic -x -o \~/.terminfo /dev/stdin

Could you explain this a bit more? I'm not sure what `ssh myserver tic -x -o \~/.terminfo /dev/stdin` is trying to do nor that it's correct as you typed it. Should `tic` be `-tic`?

tic is the TermInfo Compiler

The command on the left side of the pipe dumps the terminfo for "xterm-kitty" to stdout

The command on the right side launches ssh to "myserver" and executes tic to compile from stdin and output to the ~/.terminfo directory (which nurses/terminfo will search by default).

So basically it takes a local terminfo entry and copies it to the user-local terminfo path on the remote host.

The command will work for any other terminal too; just replace xterm-kitty with whichever entry you'd like copied.

Thanks!

As much as I like kitty, that shortcut is the only reason I've continued to use it for the past 18 months. Needing to manually fix it every time I connect to a new VM would've otherwise killed the appeal for me. `+kitten ssh` solves it nicely.

I've found that doing TERM=xterm-256color works better for me because of default debian bashrc on remote servers.

I wish I had known about this a year ago. A whole lot less to type than “mkdir -p ~/.terminfo/x ^D scp /usr/share/terminfo/xterm-kitty user@server:~/.terminfo/x/“

it seems to break on sudo. Haven't found a fix for that yet

I just set up this alias:

    alias ssh='TERM="xterm-256color" ssh'

Generally works just fine for me. I tried the kitten approach but I had some issues as well.

thanks it helps

Reply on news.ycombinator.com