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
Date: Sat, 5 Apr 2003 11:44:30 -0800 (PST)
From: Eduardo Chappa <chappa AT math DOT washington DOT edu>
To: cygwin AT cygwin DOT com
Subject: Re: nano and TERM
In-Reply-To: <Pine.GSO.4.44.0304051255040.21921-100000@slinky.cs.nyu.edu>
Message-ID: <Pine.OSF.4.53.0304051132060.304051@goedel1.math.washington.edu>
References: <Pine DOT GSO DOT 4 DOT 44 DOT 0304051255040 DOT 21921-100000 AT slinky DOT cs DOT nyu DOT edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

*** Igor Pechtchanski (pechtcha AT cs DOT nyu DOT edu) wrote today:

IP> I'm not sure why pico works, possibly because it has an internal
IP> termcap entry for a dumb terminal and uses that when the
IP> terminfo/termcap database cannot be found.

Pico as built for cygwin uses the termcap entries found in /etc/termcap,
there's no internal termcap to it. Pico (for cygwin) does not use
terminfo. Nor does Pine. My experience as maintaner of Pico (and Pine) is
that Pine/Pico have less problems in terms of control of the screen when
termcap is used (as opposed to terminfo/curses/ncurses).

Pico defaults to some settings (row, colums) when it can not find them,
but advanced screen control is done by the termcap library.

-- 
Eduardo
http://www.math.washington.edu/~chappa/pine/

--
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/