From owner-freebsd-ports  Tue Aug 13 16:49:22 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id QAA20753
          for ports-outgoing; Tue, 13 Aug 1996 16:49:22 -0700 (PDT)
Received: from sunrise.cs.berkeley.edu (root@sunrise.CS.Berkeley.EDU [128.32.38.121])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id QAA20747
          for <ports@freebsd.org>; Tue, 13 Aug 1996 16:49:20 -0700 (PDT)
Received: (from asami@localhost) by sunrise.cs.berkeley.edu (8.7.5/8.6.12) id QAA01619; Tue, 13 Aug 1996 16:48:23 -0700 (PDT)
Date: Tue, 13 Aug 1996 16:48:23 -0700 (PDT)
Message-Id: <199608132348.QAA01619@sunrise.cs.berkeley.edu>
To: robert@superior.net
CC: ports@freebsd.org, ache@astral.msk.su
In-reply-to: <199608130119.VAA14218@nimbus.superior.net> (message from Robert Blayzor on Mon, 12 Aug 1996 21:19:07 -0400 (EDT))
Subject: Re: NcFTP2 bug under 2.1.5
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * I recently installed 2.1.5 and it has been working well.  I have found that
 * one program has been causing me some problems.  NcFTP 2.3.0 has some curses?
 * problems when running under the new 2.1.5?  Can someone shed some light on
 * this for me?  I have even installed the port from the ports-2.1.5 and it
 * does the same thing.  I just want to know if there is any apparant reason
 * why when you go into Ncftp there are some cursor movement problems, apparantly
 * it looks like some key mapsing are off?!

Andrey, do you have any comments on this?

Satoshi