Message-ID: <451AEBAE.6000703@cs.ucsd.edu>
Date: Wed, 27 Sep 2006 14:22:54 -0700
From: Larry Breyer <lbreyer@cs.ucsd.edu>
User-Agent: Thunderbird 1.5.0.7 (X11/20060911)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: bash 3.1.18 seems seriously broken
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

What changed from bash 3.1.17 to 3.1.18 ?

I blindly performed a cygwin update, rebooted, and attempted startx.
X came up OK but the terminals would not respond to keyboard input.
Looking at the output of startx it became apparent something was
seriously wrong with /bin/sh (/bin/bash).

I got syntax errors on blank lines.

I also found, by adding little debugging stuff, like 'ls $XAPPLRESDIR',
that the shell was quoting env variables.  I was getting "no such file
or directory" on valid paths because the shell was including single
quotes around the path.  At least that's what it looked like.

Really odd.  I solved the problem by reverting to bash 3.1.17.
-- 
Larry Breyer
UCSD Computer Science
(858) 822-4990

--
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/