Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3CEE137D.4060307@lapo.it>
Date: Fri, 24 May 2002 12:18:37 +0200
From: Lapo Luchini <lapo AT lapo DOT it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; it-IT; rv:1.0.0+) Gecko/20020523
X-Accept-Language: it, en, fr, es
MIME-Version: 1.0
To: Corinna Vinschen <cygwin AT cygwin DOT com>
Subject: Re: ssh on FreeBSD
References: <3CB9A0AF DOT F97DD15A AT lapo DOT it> <3CEE009C DOT 3060600 AT lapo DOT it> <20020524115637 DOT E12995 AT cygbert DOT vinschen DOT de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>
>
>>I will post only this time more about this problem.. I really can't 
>>solve it and I don't believe no-one uses freebsd and cygwin here ;)
>>    
>>
>Why not adding the termcap entry for the cygwin terminal to the
>FreeBSD termcap?
>  
>
I solved the issue on many linux using termcap/c/cygwin... but FreeBSD 
doesn't use terminfo AFAIK, only has a file with termcap, which already 
has the following string:

cygwin:\
        :xn@:op=\E[39;49m:Km=\E[M:tc=linux:

instead of

cygwin:\
        :xn@:op=\E[39;49m:Km=\E[M:te=\E[2J\E[?47l\E8:ti=\E7\E[?47h:tc=linux:

But also changing it there is no real difference I can notice: CR still 
"duplicates" lines, PagUp/PagDn still leave characters frompast lines...

-- 
Lapo 'Raist' Luchini
lapo AT lapo DOT it (PGP & X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/