Re: Bash - IF Statement

On Wed, Oct 28, 2009 at 2:10 PM, briglass111 <> wrote: > > What is wrong with you people? What is the desire to continue posting in this > thread? I am a relatively inexperienced cygwin/unix user who had an honest > question and you people got so chafed up by it. If you are so insulted or > annoyed

Re: Bash - IF Statement

move on with your happy and gleeful day. If anything, it provides some search terms for a future potential poster who goes down the same errant path of thinking the white space issue is cygwin-specific. -- View this message in context: http://www.nabble.com/Bash---IF-Statement-tp26084169p26100417

Re: Bash - IF Statement

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

Re: Bash - IF Statement

On Wed, Oct 28, 2009 at 12:46:40PM -0400, Mark J. Reed wrote: >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 us

Re: Bash - IF Statement

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 bett

Re: Bash - IF Statement

Are you sure? > >> A: Because it reverses the logical flow of conversation. > >>> Q: Why is top posting annoying in email? > > -- > Problem reports: http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http:

Re: Bash - IF Statement

. Reformatted. On 10/27/2009 05:34 PM, briglass111 wrote: Andrew Schulman-3 wrote: good job, bash This is the Cygwin list. Please take non-Cygwin-related comments elsewhere. before i knew that bash was white-space picky, i thought this may be a cygwin i

Re: Bash - IF Statement

http://cygwin.com/problems.html > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > > > -- View this message in context: http://www.nabble.com/Bash---IF-Statement-

Re: Bash - IF Statement

> good job, bash This is the Cygwin list. Please take non-Cygwin-related comments elsewhere. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#un

Re: Bash - IF Statement

On Tue, Oct 27, 2009 at 15:15, briglass111 wrote: > > my friend pointed out that the problem is that there needs to be extra > spaces: > > [ "$T" = "y" ]; > > good job, bash I am not sure your comment is praising or bemoaning the bash shell. The shell interpreter needs a space after the square b

Re: Bash - IF Statement

[$T=="y"]; > if "$T"="y"; > if [["$T"="y"]]; > > etc.. > > It says: > y=y: command not found > > Ideas? > -- View this message in context: http://www.nabble.com/Bash---IF-Statement-tp26084169p26084235.html Sent

RE: Bash - IF Statement

briglass111 wrote on Tuesday, October 27, 2009 3:02 PM: > I am trying to write an IF Statement in Bash, but I am having issues. It > doesn't like the following format: > > echo "yes or no?" > read T > > if ["$T"="y"]; > then > echo "YES" > fi > > .. It also doesn't like the

Re: Bash - IF Statement

> echo "YES" > fi > > .. It also doesn't like the following alternatives: > > if [$T="y"]; > if ["$T"=="y"]; > if [$T=="y"]; > if "$T"="y"; > if [["$T"="y"

Bash - IF Statement

[$T="y"]; if ["$T"=="y"]; if [$T=="y"]; if "$T"="y"; if [["$T"="y"]]; etc.. It says: y=y: command not found Ideas? -- View this message in context: http://www.nabble.com/Bash---IF-Statement-tp26084169p26084169.