Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!paperboy!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.terminals
Subject: Re: How do I tell curses/terminfo that LF forces a CR/LF??
Keywords: Curses, terminfo, Dasher DG
Message-ID: <14981@smoke.brl.mil>
Date: 25 Jan 91 18:36:53 GMT
References: <1991Jan23.131741.23026@gorm.ruc.dk> <14959@smoke.brl.mil> <1991Jan24.113121.29126@gorm.ruc.dk>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 35

In article <1991Jan24.113121.29126@gorm.ruc.dk> jba@gorm.ruc.dk (Jan B.Andersen) writes:
>I have disabled both "cud" and "cud1" in the terminfo description without
>any luck. It seems to me that no matter what I do, curses will always
>use the LF at the end of each text line to move the cursor down to the
>next line. Can anyone tell me exactly what happens when curses "redraws" the
>screen? Is it doing a "cursor home", "clear screen", "print #LINES lines",
>using the EOL-LF to move into the next line?

Here is a cute technique for finding out exactly what the application
is doing:  Prepare a termcap/terminfo description similar to the
following, using EXACTLY the set of capabilities that is specified for
the TERM type that you have been experiencing problems with:

# Debugging entry -- all printing characters
D1|debug|debugging entry:\
	:ae=<ae>:AL=<AL%d>:al=<al>:am:as=<as>:bl=<bl>:bt=<bt>:bw:CC=<CC>:\
	:cd=<cd>:ce=<ce>:ch=<ch%d>:cl=<cl>:cm=<cm%d,%d>:co#80:cr=<cr>:\
	:cs=<cs%d,%d>:ct=<ct>:cv=<cv%d>:da:db:DC=<DC%d>:dc=<dc>:DL=<DL%d>:\
	:dl=<dl>:dm=<dm>:DO=<DO%d>:do=<do>:ds=<ds>:ec=<ec%d>:ed=<ed>:ei=<ei>:\
	:es:fs=<fs>:ho=<ho>:hs:IC=<IC%d>:ic=<ic>:im=<im>:ip=<ip>:is=<is>:\
	:it#8:K1=\E1:K2=\E2:K3=\E3:K4=\E4:K5=\E5:k0=\Ef0:k1=\Ef1:kA=\EA:\
	:ka=\Ea:kb=\Eb:kC=\EC:kD=\ED:kd=\Ed:kE=\EE:ke=<ke>:kF=\EF:kH=\EH:\
	:kh=\Eh:kI=\EI:kL=\EL:kl=\El:kM=\EM:km:kN=\EN:kP=\EP:kR=\ER:kr=\Er:\
	:kS=\ES:ks=<ks>:kT=\ET:kt=\Et:ku=\Eu:l0=F0:l1=F1:LE=<LE%d>:le=<le>:\
	:li#24:ll=<ll>:mb=<mb>:md=<md>:me=<me>:mh=<mh>:mi:mk=<mk>:mm=<mm>:\
	:mo=<mo>:mp=<mp>:mr=<mr>:ms=<ms>:nd=<nd>:nw=<nw>:pb#4800:pc=<pc>:\
	:pf=<pf>:pO=<pO%d>:po=<po>:ps=<ps>:rc=<rc>:RI=<RI%d>:rp=<rp%.%d>:\
	:rs=<rs>:sc=<sc>:se=<se>:SF=<SF%d>:sf=<sf>:so=<so>:SR=<SR%d>:sr=<sr>:\
	:st=<st>:ta=<ta>:te=<te>:ti=<ti>:uc=<uc>:ue=<ue>:UP=<UP%d>:up=<up>:\
	:us=<us>:vb=<vb>:ve=<ve>:vi=<vi>:vs=<vs>:vt#3:ws#80:

Then set TERM to "debug" and run the application through its paces.
Instead of invisible control actions, you should now get a printable
representation of every output capability being used.  If you still
see an actual newline being output, the application is at fault.