![]() But if I'm using sudo it's almost guaranteed for root access! I'll leave this thread open for other solutions though.Ĭopying the file into the system path did indeed solve my issue! But I wondered if there was a package for it instead and ( kovidgoyal#2053 (comment)) - `kitty-terminfo`. > What are my options? I would really rather not copy my termcap file into /usr/share/terminfo since I might not always have root access on my remote machines. > Edit: Looking at the ( ) document, I see that TERMINFO is removed "to guard against shared library spoofing, shell voodoo, and kerberos server spoofing." > Why does the TERMINFO get dropped when my other environment variables stick around? So vim won't display things properly (no colors) and other silly problems (LESS 'Warning terminal is not fully functional"). > When I use sudo -E or sudoedit it looks like the TERMINFO environment variable is getting lost. I put this file in `$HOME/.local/share/terminfo/x/xterm-termite` and set my $TERMINFO environment variable to `$HOME/.local/share/terminfo`. Since this is non-standard I have to copy over the termcap file to remote machines I commonly work on. > I use the termite terminal which uses the termcap file 'xterm-termite'. In case the thread gets removed, here's the content: I only realised today that it was only `sudo` commands that were failing this way. WARNING: terminal is not fully functional ![]() ![]() I'd followed the instructions for using the SSH kitten ages ago, but I've always had trouble with it when SSH-ing to my server, e.g.:
0 Comments
Leave a Reply. |