Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Originating-IP: [203.213.50.70] From: "Gareth Pearce" To: References: <3DBE1680.8090705@mailandnews.com> <5.1.0.14.2.20021029073133.01fe3b00@pop3.cris.com> Subject: Re: export CYGWIN=tty Date: Wed, 30 Oct 2002 06:32:58 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: X-OriginalArrivalTime: 29 Oct 2002 19:32:48.0850 (UTC) FILETIME=[F6D5A320:01C27F81] > Larry, Daniel, > > I don't routinely use the "tty" option of the CYGWIN variable, but when > I've experimented with it, I've seen symptoms like those reported by Daniel > if I set the tty option after a shell is started and then run a program > such as Vim that changes the tty modes. When the program exits, it appears > the shell reestablishes tty modes unaware that CYGWIN has had tty added to > it and those modes are inappropriate in that case (in particular, echoing > is disabled, as Daniel reported). Indeed - this is probably why the users guide explicitly states that the tty variable must be set before starting cygwin. On boot is my preference. Gareth -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/