X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS X-Spam-Check-By: sourceware.org MIME-Version: 1.0 In-Reply-To: <26085849.post@talk.nabble.com> References: <26084169.post@talk.nabble.com> <26084235.post@talk.nabble.com> <26085599.post@talk.nabble.com> <4AE76A96.4050708@cygwin.com> <26085849.post@talk.nabble.com> Date: Wed, 28 Oct 2009 12:46:40 -0400 Message-ID: Subject: Re: Bash - IF Statement From: "Mark J. Reed" To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 You're still sending TOFU. Please stop. On Tue, Oct 27, 2009 at 5:54 PM, briglass111 wrote: > It didn't matter if I believed what I read on the internet or not, I couldn't > get the IF-statement to work, and when I queried a unix user, he wasn't sure Sounds like you need to associate with a better class of UNIX users. :) The point is, bash scripting syntax is not a Cygwin-specific issue, and it would in fact be very hard for Cygwin to screw that up. It's always a good idea to try something on Linux first and see if it really behaves any differently there before complaining that it's broken on Cygwin. -- Mark J. Reed -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple