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 Date: Wed, 22 Sep 2004 16:47:36 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: problem with cygwin box (termcap?) Message-ID: <20040922204736.GI6266@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200409221956 DOT i8MJusA06757 AT panix1 DOT panix DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409221956.i8MJusA06757@panix1.panix.com> User-Agent: Mutt/1.4.1i On Wed, Sep 22, 2004 at 03:56:54PM -0400, David Arnstein wrote: >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? Cygwin's terminal emulation is not at fault. It works fine locally, after all. I sincerely doubt that either of those programs uses termcap. You need to set up a terminfo entry for cygwin on the remote system. You can use the "infocmp" program to dump the entry and the "tic" program on the remote computer to incorporate it. There may be a way to set this up on the remote computer without being root, too, but I'll leave that to you to research. cgf -- 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/