3 ms·
> Some random program complains that st is unknown/not recognised/unsupported/whatever! I really wish there was a better way to deal with this (I have the same
by stormbrew 12y ago
> Some random program complains that st is unknown/not recognised/unsupported/whatever!
I really wish there was a better way to deal with this (I have the same problem with rxvt-unicode-256color). I'm obviously not going to make install a graphical terminal emulator on some random server I'm logging into.
- vortico 12y agoPut the following in your shell configuration. alias ssh='env TERM=xterm-256color ssh'
- hoeppnertill 12y agotic -s st.info or setting your TERM variable should help.
- stormbrew 12y agoI meant the distribution problem of getting the file to the server. I grant that it's a petty annoyance, but it is still an annoying thing. And logging into a new server always carries with it the question of whether it's worth fixing it permanently when you barely use it. For the machines I regularly use I have terminfo files in my dotfiles git repo.
- Sanddancer 12y agoI'd argue that they should go the route that most terminal programs do and just announce they're xterm, or at least have a config file option for doing so.