On Fri, Nov 09, 2001 at 08:16:34PM +0100, Roman Neuhauser wrote:
>     thank you for your answer. I don't know if it means anything, but my
>     termcap already contained a rxvt entry, with a comment that it's taken
>     from the rxvt-2.6.3 sources, which is what I use. I rebuilt the database
>     just to be sure, commented out the rxvt.termName line in my .Xdefaults
>     file, and opened a new terminal window (rxvt):
>    
>     roman@roman ~ > grep termName .Xdefaults 
>     ! rxvt.termName: xterm-color
>     roman@roman ~ > echo $TERM
>     xterm
>    
>     Next, I put the two rxvt entries (rxvt-basic and rxvt) from
>     termcap.src.gz in my /usr/share/misc/termcap, and got these two
>     messages upon issuing cap_mkdb:
>     
>     cap_mkdb: record not tc expanded: rxvt|rxvt terminal emulator (X
>      Window System)
>     cap_mkdb: record not tc expanded: rxvt|rxvt terminal emulator (X
>      Window System)
>   
>     Whassup?

offhand (I'm working on Linux now, will try to remember to test this on
FreeBSD) I think it's complaining that the name cited in the "tc="
clause doesn't exist, e.g., "ecma+color":

rxvt|rxvt terminal emulator (X Window System):\
        :NC@:\
        :me=\E[m\017:tc=rxvt-basic:tc=ecma+color:

Also cap_mkdb may also complain that the termcap doesn't begin with a
2-character identifier.  Canonical termcap entries begin that way; termcaps
generated from infocmp don't do that.  (I have a to-do item to add an infocmp
option for this).
 
>     Besides, termcap.src.gz says 'rxvt is normally configured to look for
>     "xterm" or "xterm-color" as $TERM. Since rxvt is not really compatible
>     with xterm, it should be configured as "rxvt" (monochrome) and
>     "rxvt-color"'. What does that mean for me? 

What I do is edit the header-file in rxvt that's hardcoded to "xterm" and
change that to "rxvt" when I compile it.  (I don't recall that being
configurable, and since it's easy to edit I haven't looked to see if there's a
better way).

Likewise, for the various other terminal emulators (I install those all to set
$TERM to be what it "should" be, e.g., xterm-r5, xterm-r6, xterm-xfree86,
kterm, aterm, Eterm, rxvt, since it's simpler to map those _to_ "xterm" on the
remote side if needed than determine which flavor it really is.

That reminds me of a bug that I observed in Mandrake 8.1 (you see, FreeBSD
isn't the only one that can't setup terminfo properly):

        011017 md81 installs xterm-debian as an alias for 'nxterm' and
        'xterm-color', which looks like the 88b-version (so alternate screen
        stuff is a bit retarded).  Actually, 'xterm' looks like the newer
        version, since it uses 1049.
 
This termcap doesn't use the "tc=" clause:

rxvt|rxvt terminal emulator (X Window System):\
        :am:eo:km:mi:ms:xn:xo:\
        :co#80:it#8:li#24:\
        :AL=\E[%dL:DC=\E[%dP:DL=\E[%dM:DO=\E[%dB:IC=\E[%d@:\
        :K1=\EOw:K2=\EOu:K3=\EOy:K4=\EOq:K5=\EOs:LE=\E[%dD:\
        :RI=\E[%dC:UP=\E[%dA:ae=^O:al=\E[L:as=^N:bl=^G:cd=\E[J:\
        :ce=\E[K:cl=\E[H\E[2J:cm=\E[%i%d;%dH:cr=^M:\
        :cs=\E[%i%d;%dr:ct=\E[3g:dc=\E[P:dl=\E[M:do=^J:ei=\E[4l:\
        :ho=\E[H:i1=\E[?47l\E=\E[?1l:ic=\E[@:im=\E[4h:\
        :is=\E[r\E[m\E[2J\E[H\E[?7h\E[?1;3;4;6l\E[4l:\
        :k0=\E[21~: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~:\
        :kD=\E[3~:kI=\E[2~:kN=\E[6~:kP=\E[5~:kb=^H:kd=\E[B:ke=\E>:\
        :kh=\E[7~:kl=\E[D:kr=\E[C:ks=\E=:ku=\E[A:le=^H:mb=\E[5m:\
        :md=\E[1m:me=\E[m\017:mr=\E[7m:nd=\E[C:rc=\E8:sc=\E7:\
        :se=\E[27m:sf=^J:so=\E[7m:sr=\EM:st=\EH:ta=^I:\
        :te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:ue=\E[24m:up=\E[A:\
        :us=\E[4m:vb=\E[?5h\E[?5l:ve=\E[?25h:vi=\E[?25l:\
        :vs=\E[?25h:

-- 
Thomas E. Dickey <[EMAIL PROTECTED]>
http://invisible-island.net
ftp://invisible-island.net

Reply via email to