Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <200409221956.i8MJusA06757@panix1.panix.com> Subject: problem with cygwin box (termcap?) To: cygwin AT cygwin DOT com Date: Wed, 22 Sep 2004 15:56:54 -0400 (EDT) From: "David Arnstein" Reply-To: arnstein AT pobox DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I launch a cygwin "box" (command window) on my Windows 2000 machine. I run ssh to connect to a shell account running a variant of BSD Unix. Whenever I use the program "less" on that shell account, it complains "WARNING: terminal is not fully functional." Another user has stated that tin (the news reader) complains "tin: Terminal must have clear to end-of-screen (cd) I suspect that these issues are related. Can the termcap entry for cygwin be improved? Or is this truly a limitation of the cygwin box? Thanks for any ideas. -- David Arnstein arnstein AT pobox DOT com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/