delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/12/12/20:58:40

From: vischne AT ibm DOT net
Subject: Re; One way to get around the cygwin terminal problem
12 Dec 1997 20:58:40 -0800 :
Message-ID: <199712130426.EAA81212.cygnus.gnu-win32@out2.ibm.net>
Mime-Version: 1.0
To: gnu-win32 AT cygnus DOT com DOT Sergey DOT Okhapkin (sos AT buggy DOT prospect DOT com DOT ru)

vischne AT ibm DOT net wrote:
>
> In other words, with some work, it is possible to get a professional
> looking and acting terminal application using the cygwin Unix
> environment but bypassing the cygwin terminal window.

It's a bad idea to replace stdout with direct console writings. You
application, for example, will not work in a telnet session or in xterm
window.

I don't see the point of an xterm window if you are running a Unix
environment under Windows 95.  Simply calling up bash.exe ought to
generate the equivalent of an xterm window.  But, running lynx or slrn
or midnight commander in the current version of a cygwin Windows/xterm
window just doesn't work right.

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019