[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MakeTermcap weirdness

From: Michael Schroeder
Subject: Re: MakeTermcap weirdness
Date: Tue, 29 Mar 2005 18:03:17 +0200
User-agent: Mutt/

On Tue, Mar 29, 2005 at 04:44:08PM +0200, Nikolai Weibull wrote:
> Two things with MakeTermcap bugs me:
> 1.  Why does it
>       strcpy(Term, "TERM=screen");
>     if $SCREENCAP is set?

Hmm, I don't see why it shouldn't do that.

> I guess one solution to 2 is to add
> terminfo xterm-256color "" Co\#256:AB=\E[48;5;%p1%dm:AF=\E[38;5;%p1%dm
> to ones .screenrc, but what I'd really want is to have TERMCAP not being
> set at all, as some applications wrongly check for it before checking
> the terminfo database.

Yes, I'm also in favor of dropping $TERMCAP but didn't dare to do
so for now. Hmm, lets ask the list if there are strong opinions against
dropping it. (It would be an option in config.h, of course.)

All those terminal capaility issues are quite sad, it should have
been designed completely different. xterm & vim do it right, vim
uses an escape sequence to ask xterm about its capabilities. In other
words, the terminfo entry should be stored inside of the terminal.

(A first step would be if tools like ssh would "forward" the terminfo
entry if one logs into another host...)


Michael Schroeder           address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]