Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <39DA2028.7F9797BB@cygnus.com> Date: Tue, 03 Oct 2000 20:06:32 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.14-SMP i686) X-Accept-Language: de, en MIME-Version: 1.0 To: cygwin Subject: Re: Question if I may References: <4 DOT 3 DOT 0 DOT 20001002234133 DOT 00ae3c30 AT imap DOT coe DOT utah DOT edu> <4 DOT 3 DOT 2 DOT 7 DOT 0 DOT 20001003111017 DOT 00ad3a10 AT imap DOT coe DOT utah DOT 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 AT sources DOT redhat DOT com Red Hat, Inc. mailto:vinschen AT cygnus DOT com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com