On Sun, Mar 19, 2006 at 11:52:13AM -0500, Thomas Dickey wrote: > On Sun, 19 Mar 2006, Daniel Jacobowitz wrote: > >1. Open rxvt-unicode on host A. This host has rxvt-unicode > > installed, and presumably has a termcap entry for it. > >2. SSH to host B. This older host does not. > > For this case, we can't solve his problem (simply because differences in > function keys, etc., mean there is in general no well-defined subset to > fall back to).
Sure; however, my experience is that most terminal emulators support at least a useful subset of xterm. The fact that they don't map 100% is precisely the reason why I don't want to go ahead and say TERM=xterm everywhere. However, if I log in to a host where rxvt-unicode isn't in termcap (or whatever), it'd be great if ncurses could just walk some environment variable until it finds a name that it does, in fact, know. That can't be done currently, which means that every time I log in to a host that does not have an rxvt-unicode termcap entry, I need to say "export TERM=xterm", or I get stuff like [EMAIL PROTECTED]:~$ top 'rxvt-unicode': unknown terminal type. [EMAIL PROTECTED]:~$ Other applications, like 'less' and 'vim', do give me some full-screen interface, but one that doesn't do proper scrolling, colors, or anything similar. > For the usual case (fallback to existing values) it's certainly doable > since xterm does _that_. That's very nice, but not very useful. It's not the terminal emulator that needs to fall back, it's the ncurses-using application that would need to do so. -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
