Date: Sat, 31 Dec 2011 02:56:40 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Edward Martinez <eam1edward@gmail.com> Cc: ??????? ???????? <nm.knife@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: why newline scape sequence does not work in Freebsd's bash Message-ID: <20111231015640.GA38111@owl.midgard.homeip.net> In-Reply-To: <4EFE77D1.3090402@gmail.com> References: <4EFE645B.8010906@gmail.com> <CAHi1JsepvhJaHb%2B1zMssWiConxz9U75%2B8t8Pay2AH68mYrMjXg@mail.gmail.com> <CAHi1JsdOu9oMGqL4fiOM7P0ExCXHA2q=r%2BzGeEihXojAffj2pA@mail.gmail.com> <4EFE77D1.3090402@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Dec 30, 2011 at 06:47:45PM -0800, Edward Martinez wrote: > On 12/30/11 17:06, ??????? ???????? wrote: > > I used ' singe quotes, so double quotes is: > > > > $ FRUIT_BASKET="apples oranges pears" > > $ echo -e "My fruit basket contains: \n $FRUIT_BASKET" > > My fruit basket contains: > > apples oranges pears > > > Thanks for the help, it worked. I find it interesting that FreeBSD's > echo man page does not mention the -e option is needed to > enable backslash escapes. I remembered why it worked on linux > is because i created an echo alias with the -e option. > So i will do the same for FreeBSD. The echo(1) manpage on FreeBSD doesn't say anything about '-e' because that version of echo doesn't have such an option. The echo you were actually using is the one builtin into bash and is described in the bash(1) manpage (including mention of the -e option.) -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111231015640.GA38111>