X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <26099740.post@talk.nabble.com> Date: Wed, 28 Oct 2009 11:29:33 -0700 (PDT) From: jreidthomps To: cygwin AT cygwin DOT com Subject: Re: Bash - IF Statement In-Reply-To: <26085599.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <26084169 DOT post AT talk DOT nabble DOT com> <26084235 DOT post AT talk DOT nabble DOT com> <26085599 DOT post AT talk DOT nabble DOT com> 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 > before i knew that bash was white-space picky I think most shells are, not just bash > , i thought this may be a cygwin issue because i read a bit about people > saying bash is different in cygwin than in unix where? I've not ran into any instances where cygwin bash varies from unix bash > and i got the if-statement code from a website about unix, and when it > didn't run in cygwin's bash i figured it was a cygwin-specific issue then the website posted invalid code, and your question should perhaps have been directed there. a minute looking at examples on google "bash if else" would give plenty of valid snippets -- View this message in context: http://www.nabble.com/Bash---IF-Statement-tp26084169p26099740.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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