Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
Message-ID: <39DA2028.7F9797BB@cygnus.com>
Date: Tue, 03 Oct 2000 20:06:32 +0200
From: Corinna Vinschen <vinschen@cygnus.com>
Reply-To: cygwin <cygwin@sources.redhat.com>
MIME-Version: 1.0
To: cygwin <cygwin@sources.redhat.com>
Subject: Re: Question if I may
References: <4.3.0.20001002234133.00ae3c30@imap.coe.utah.edu> <4.3.2.7.0.20001003111017.00ad3a10@imap.coe.utah.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Bret Jordan wrote:
> Nearly everything works fine.  I can connect from a workstation to the
> server and run the normal shell programs.  However when I try to run any
> command character programs, edit, pmon, emacs, vi, or anything that draws
> data to the command window it dies.  Usually the response is it just hangs
> the connection and sits there.  Then if I look at the actual process on the
> server it shows that the process xyz is running.   It is like it is trying
> [...]

You should use the Cygwin ports of that tools ("vim" from the base
distro for example) since most native Windows applications are not able
to deal with that socket oriented connection used by sshd. Windows
tools like `edit' are using the native Windows console commands most
of the time so they are only able to run in a standard console. While
you are connected to another machine, the communication is quite
different. And don't try to start GUI tools. This will not work, either.

Hope, that helps,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                        mailto:cygwin@sources.redhat.com
Red Hat, Inc.
mailto:vinschen@cygnus.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com