X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 3 Aug 2008 14:36:49 -0500 (CDT) From: tmcd AT panix DOT com To: cygwin AT cygwin DOT com Subject: Re: bash shell interface broken after install on Vista In-Reply-To: <4895F9A7.1030103@ca.rr.com> Message-ID: References: <4895F9A7 DOT 1030103 AT ca DOT rr DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Sun, 3 Aug 2008, Barry Gold wrote: > 1. Nearly all commands appear to complete without doing anything. > This includes "ls", "cat", "vi". > The following commands work properly: > echo > true > false ($? == 1) > dirs > if...then.fi > test That I can address: they are shell builtins. That is, they are recognized by bash and processed by the bash program itself without forking or otherwise involving another process. I find it hard to imagine that anything in bash could work if those commands didn't. Since you just installed Cygwin and didn't configure it much, have you considered just uninstalling and reinstalling from a new mirror? -- Tim McDaniel; Reply-To: tmcd AT panix DOT com -- 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/