Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!news.hawaii.edu!ames!usenet.kornet.nm.kr!usenet.hana.nm.kr!jagalchi.cc.pusan.ac.kr!news.kreonet.re.kr!usenet.seri.re.kr!news.cais.net!news.jsums.edu!gatech!news.mathworks.com!fu-berlin.de!news.belwue.de!news.dfn.de!news.uni-jena.de!news.HRZ.HAB-Weimar.DE!News.HTWM.De!news.tu-chemnitz.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Bug in ECHO? Date: 19 Feb 1996 23:21:33 GMT Organization: Private BSD site, Dresden Lines: 17 Message-ID: <4gb0lt$d34@uriah.heep.sax.de> References: <4famj5$4hf@complete.org> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 jgoerzen@complete.org (John Goerzen) writes: > The echo command under FreeBSD is not properly expanding backslash escape > sequences. I have several shell scripts that do not work right because of > this. The echo command in *BSD is not supposed to expand backslashes. It should echo its argument, not interpret them. The functionality you are looking for can be found in printf(1). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)