screen-users
[Top][All Lists]
Advanced

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

Re: tgetent: warning: termcap entry too long


From: Andy Walker
Subject: Re: tgetent: warning: termcap entry too long
Date: Thu, 19 Feb 2009 10:03:06 -0500

The relavent sections of /etc/termcap appear to be these:

---------------
# Entry for an xterm. Insert mode has been disabled.
vs|xterm|xterm-color|vs100|xterm terminal emulator (X Window System):\
       :am:bs:mi@:km:co#80:li#55:\
       :im@:ei@:\
       :ct=\E[3k:ue=\E[m:\
       :is=\E[m\E[?1l\E>:\
       :rs=\E[m\E[?1l\E>:\
       :eA=\E)0:as=^N:ae=^O:ac=aaffggjjkkllmmnnooqqssttuuvvwwxx:\
       :kI=\E[2~:kD=\177:kP=\E[5~:kN=\E[6~:\
       :k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~:k5=\E[15~:\
       :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:k0=\E[21~:\
       :F1=\E[23~:F2=\E[24~:\
       :kh=\E[H:kH=\EOw:\
       :ks=:ke=:\
       :te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:\
       :tc=vt-generic:

# Some other entries for the same xterm.
v2|xterms|vs100s|xterm small window:\
       :co#80:li#24:tc=xterm:
vb|xterm-bold|xterm with bold instead of underline:\
       :us=\E[1m:tc=xterm:
vi|xterm-ins|xterm with insert mode:\
       :mi:im=\E[4h:ei=\E[4l:tc=xterm:
---------------

As for ldd:

---------------
$ ldd /usr/bin/screen
       linux-gate.so.1 =>  (0xffffe000)
       libncurses.so.5 => /usr/lib/libncurses.so.5 (0xb7f2a000)
       libutil.so.1 => /lib/libutil.so.1 (0xb7f26000)
       libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7ef4000)
       libc.so.6 => /lib/libc.so.6 (0xb7dc1000)
       /lib/ld-linux.so.2 (0x80000000)
---------------

On Thu, Feb 19, 2009 at 5:03 AM, Micah Cowan <address@hidden> wrote:
> Andy,
>
> Does xterm have an entry in your /etc/termcap? Please provide that.
>
> What do you get for "ldd screen"?
>
> The thing that bothers me about this, is that the failure point must be
> at screen, rather than the programs running under it, since the kend/kH
> is failing to be translated from \EOF to screen's \E[4~. The only way
> this would make sense to me is if screen is using a real termcap as
> opposed to ncurses' emulation of it through terminfo: real-world termcap
> implementations are known to do things like truncate the entry if it
> exceeds 1023 bytes.
>
> If the xterm entry in your /etc/termcap is greater than that, and moving
> the definition for kH closer to the top eliminates the problem, then we
> know that termcap is being used (and we need to find out why configure
> is then misdetecting this). Otherwise, it remains a mystery to me why
> \EOF isn't being translated correctly, and no problem with the shells or
> other things running under screen would explain it.
>
> --
> Micah J. Cowan
> Programmer, musician, typesetting enthusiast, gamer.
> GNU Maintainer: wget, screen, teseq
> http://micah.cowan.name/
>




reply via email to

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