Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Oct 2000 20:49:00 -0700
From:      Jamie Norwood <mistwolf@mushhaven.net>
To:        Dan Nelson <dnelson@emsphone.com>
Cc:        Otter <otterr@telocity.com>, freebsd-questions@FreeBSD.ORG
Subject:   Re: Raising PTYs
Message-ID:  <20001002204859.A29344@mushhaven.net>
In-Reply-To: <20001002224551.B23329@dan.emsphone.com>
References:  <20001001210159.A17043@dan.emsphone.com> <HLEDJBJKDDPDJBMGCLPPOEIHCEAA.otterr@telocity.com> <20001002174100.A6585@mushhaven.net> <20001002224551.B23329@dan.emsphone.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I installed the latest ncurses (5.1) and the problem went away... So,
for now, this is my recommendation. I have SecureCRT set to VT100 and
my TERM variabl to vt100. Note screen 3.9.8 hard-sets it's termcap
in your environment:

TERMCAP=SC|screen|VT 100/ANSI X3.64 virtual terminal:\
        :DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:bs:bt=\E[Z:\
        :cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:ct=\E[3g:\
        :do=^J:nd=\E[C:pt:rc=\E8:rs=\Ec:sc=\E7:st=\EH:up=\EM:\
        :le=^H:bl=^G:cr=^M:it#8:ho=\E[H:nw=\EE:ta=^I:is=\E)0:\
        :li#30:co#80:am:xn:xv:LP:sr=\EM:al=\E[L:AL=\E[%dL:\
        :cs=\E[%i%d;%dr:dl=\E[M:DL=\E[%dM:ks=\E[?1h\E=:\
        :ke=\E[?1l\E>:vi=\E[?25l:ve=\E[34h\E[?25h:vs=\E[34l:\
        :us=\E[4m:ue=\E[24m:so=\E[3m:se=\E[23m:mb=\E[5m:\
        :md=\E[1m:mr=\E[7m:me=\E[m:ms:\
        :Co#8:pa#64:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:AX:G0:\
        :as=\E(0:ae=\E(B:\
        :ac=\140\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~..--++,,hhII00:\
        :k0=\E[10~:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\E[15~:\
        :k6=\E[17~:k7=\E[18~:k8=\E[19~:k9=\E[20~:k;=\E[21~:\
        :F1=\E[23~:F2=\E[24~:kb=^H:K1=\EOq:K2=\EOr:K3=\EOs:\
        :K4=\EOp:K5=\EOn:kh=\E[1~:kH=\E[4~:kN=\E[6~:kP=\E[5~:\
        :kI=\E[2~:kD=\E[3~:ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:

Jamie

On Mon, Oct 02, 2000 at 10:45:51PM -0500, Dan Nelson wrote:
> In the last episode (Oct 02), Jamie Norwood said:
> > OK, I searched this down a bit, and mostly found a lot of 'me toos'
> > with no real solutions. The problem is, I am seeing this in both
> > xterm and SecureCRT. However, I can, somewhat, reprodoce it.
> > 
> > It shows up in Mutt if you have in your .muttrc:
> > 
> > set sort=threads
> > 
> > If I take that out, mutt is fine... But I no longer see threads, only
> > individual messages. As one of the key reasons I use Mutt is for
> > threads... I also see it in SLRN. The characters that are seeming to
> > cause the problems are what is used for lines and arrows, whcih I
> > believe are from high ASCII if I recall my BBS days correctly.
> 
> Make sure your TERM variable matches whatever terminal emulation type
> you have set in CRT.  I'm reading mail with sort=threads via CRT right
> now, and the threading characters look perfect (they're also fine if I
> run under screen).  Here's the termcap entry I use for CRT.  I tell CRT
> to do "ansi" emulation, which is afwully close to SCO's console in
> terms of features (i.e. it's not ANSI X3.64, but a whole hodgepodge of
> stuff :).  I also use a font that has line-drawing charaters in the right
> place.
> 
> # CRT term doesn't know cv or ch, does have "Set scrolling region",
> # doesn't have "erase characters", has underline,
> # uses ^E[m to reset colors, has printing mode,
> # eats a newline if at right margin, can't do ACS chars < 32
> cons25-crt|Entry for CRT terminal:\
> 	:cv@:ch@:\
> 	:cs=\E[%i%d;%dr:\
> 	:ec@:\
> 	:us=\E[4m:ue=\E[24m:\
> 	:op=\E[m:\
> 	:po=\E[5i:pf=\E[4i:\
> 	:xn:\
> 	:ac=-\^.v0\333`\004a\260f\370g\361h\261i\025j\331k\277l\332m\300n\305q\304t\303u\264v\301w\302x\263y\363z\362~\371:\
> 	:tc=cons25w:
> 
> -- 
> 	Dan Nelson
> 	dnelson@emsphone.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001002204859.A29344>