Preferred way of dealing with the absence of `foot-terminfo` #718

Open
opened 1 month ago by sv · 2 comments
sv commented 1 month ago

DISCUSSION, NOT A BUG.

Is there a "canonical" method of dealing with the foot-terminfo being unknown to a target host?

For example, this works:

alias xssh='env TERM=xterm-256color ssh'

...but error-prone as it requires to remember which host has foot-terminfo already installed.

*DISCUSSION, NOT A BUG.* Is there a "canonical" method of dealing with the `foot-terminfo` being unknown to a target host? For example, this works: ```sh alias xssh='env TERM=xterm-256color ssh' ``` ...but error-prone as it requires to remember which host has `foot-terminfo` already installed.
Owner

You can always copy the terminfo files yourself. If you don't "own" the remote system, copy them to ~/.terminfo/f/{foot,foot-direct}.

Besides that, you don't really have that many options. You can install foot-terminfo on the remote, if the remote distro has that package.

Otherwise you need to override TERM in some way. Apparently, the next release of ssh will have support for per-host TERM variables (in .ssh/config).

Also, the next release of ncurses will include foot terminfo definitions, so once the remote system has been updated to that, it'll automatically have the correct definitions.

You can always copy the terminfo files yourself. If you don't "own" the remote system, copy them to `~/.terminfo/f/{foot,foot-direct}`. Besides that, you don't really have that many options. You can install `foot-terminfo` on the remote, if the remote distro has that package. Otherwise you need to override `TERM` in some way. Apparently, the next release of ssh will have support for per-host `TERM` variables (in `.ssh/config`). Also, the next release of ncurses will include foot terminfo definitions, so once the remote system has been updated to that, it'll automatically have the correct definitions.
sv commented 1 month ago
Poster

You can always copy the terminfo files yourself. If you don't "own" the remote system, copy them to ~/.terminfo/f/{foot,foot-direct}.

That's what I do :)

Apparently, the next release of ssh will have support for per-host TERM variables (in .ssh/config)

Valuable, thanks!

Also, the next release of ncurses will include foot terminfo definitions, so once the remote system has been updated to that, it'll automatically have the correct definitions.

Debian Stable, see you in 2 years time...

> You can always copy the terminfo files yourself. If you don't "own" the remote system, copy them to ~/.terminfo/f/{foot,foot-direct}. That's what I do :) > Apparently, the next release of ssh will have support for per-host TERM variables (in .ssh/config) Valuable, thanks! > Also, the next release of ncurses will include foot terminfo definitions, so once the remote system has been updated to that, it'll automatically have the correct definitions. Debian Stable, see you in 2 years time...
craigbarnes changed title from Preferred way of dealing with the abscence of `foot-terminfo` to Preferred way of dealing with the absence of `foot-terminfo` 1 month ago
dnkl added the
question
label 1 month ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.