Subject: Re: echo with sh.exe doesn't understand multiple parameters
From: Bob McGowan <[email-masked]>
To: John Pollock <[email-masked]>
Cc: [email-masked]
Date: Thu, 19 Oct 2000 16:36:32 -0700

On Linux, sh is a link to bash, not ash.  I just checked this on cygwin bash, and it works there the same as you describe.  It is sh as ash that is different.

John Pollock wrote:
> 
> Thanks Bob and others who responded.  FWIW, sh on Linux accepts -e and -n at
> the same time, which is how we managed to run into our trouble (we do
> concurrent builds on Linux and Windows).  But i'll be changing
> our -e -n references to use -e and \c.
> 
> Thanks!
> John
> 
> -----Original Message-----
> From: Bob McGowan [mailto:[email-masked]]
> Sent: Thursday, October 19, 2000 4:18 PM
> To: John Pollock
> Subject: Re: echo with sh.exe doesn't understand multiple parameters
> 
> These are mutually exclusive options.  The -n makes echo emulate the old
> Bourne shell behavior, -e the new.
> 
>    echo -n test
> and
>    echo -e 'test\c'
> 
> Are equivalent.  The other backslash sequences recognized when -e is used
> had no equivalent in older shells.  You had to embed litteral characters,
> where possible.
> 
> Hope this helps.
> 
> John Pollock wrote:
> >
> > With the echo command, using -n or -e alone with sh works fine:
> >
> > $ echo -e blah
> > blah
> > $ echo -n blah
> > blah$
> >
> > but when you try to use both flags at once, sh seems to get confused:
> >
> > blah$ echo -n -e blah
> > -e blah$
> >
> > Is there a workaround?
> >
> > John
> >
> > --
> > Want to unsubscribe from this list?
> > Send a message to [email-masked]
> 
> --
> Bob McGowan
> Staff Software Quality Engineer
> VERITAS Software
> [email-masked]
> 
> --
> Want to unsubscribe from this list?
> Send a message to [email-masked]

-- 
Bob McGowan
Staff Software Quality Engineer
VERITAS Software
[email-masked]

--
Want to unsubscribe from this list?
Send a message to [email-masked]