Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Shankar Unni" To: Subject: RE: latest version of vi messes up bash for me Date: Tue, 10 Jun 2003 16:41:36 -0700 Message-ID: <00d101c32fa9$d82815b0$0300a8c0@HQSHANKAR> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id h5ANg8e21303 Igor Pechtchanski [mailto:pechtcha AT cs DOT nyu DOT edu] wrote: > The bash man page says > An interactive shell is one started without non-option > arguments and without the -c option whose standard input > and output are both connected to terminals (as determined > by isatty(3)), or one started with the -i option. And that's exactly how I start it. C:\> env CYGWIN=tty bash However, I now see that the effects of this are odd, at best. Sometimes, when I start it this way, the *first* command I type is echoed properly, but the second and subsequent ones are not echoed. And some other times, it comes up from the start as noecho. But then again: C:\> set CYGWIN=tty C:\> bash This works flawlessly. Commands always echo, and I can start and exit vim to my heart's content. Actually, this seems to point out that vim is likely *NOT* the culprit, and that it's a bash weirdness of some sort when it's passed CYGWIN=tty in the envp[] only (and not in the system environment). Is some part of the runtime initializing itself from the system environment, while others look at envp[], perhaps? Interesting.. -- Shankar. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/