Date: Mon, 14 May 2012 13:51:22 -0400 From: Robert Simmons <rsimmons0@gmail.com> To: freebsd-hackers@freebsd.org Subject: Re: csh builtin command problems Message-ID: <CA%2BQLa9AmRszntmMboEPS1t4tSO31qScXxy=G35uyB6NU72KxtA@mail.gmail.com> In-Reply-To: <1337017511.1503.70.camel@revolution.hippie.lan> References: <CA%2BQLa9DGKQjJPsdkU=eQb08xdMeg11rhDjv721wg9qCRLaO5Fw@mail.gmail.com> <1337017511.1503.70.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 14, 2012 at 1:45 PM, Ian Lepore <freebsd@damnhippie.dyndns.org> wrote: > On Wed, 2012-05-09 at 21:34 -0400, Robert Simmons wrote: >> I'm trying to use sysv style echo in /bin/csh and I've hit a wall as >> to how to get it to work. >> >> The following does not have the outcome that I'm looking for: >> >> # echo_style=3Dsysv >> # echo test\ttest > test >> # cat test >> testttest >> >> I want this: >> >> # echo test\ttest > test >> # cat test >> test =A0 =A0test >> >> Any thoughts? > > What I see on 8.3 is this: > > % set echo_style=3Dsysv > % echo test\ttest > testttest > % echo "test\ttest" > test =A0 =A0test > % > > So it seems from this very minimal test that the implementation of echo > is correct, but the parsing of the command line in csh requires that the > \t in the arg be protected with quotes. =A0(I don't normally spend any > longer in csh than it takes for a .cshrc to launch bash, and even that's > only on systems where I don't control /etc/passwd to just use bash > directly.) Thanks. I should have tried double quotes. That works.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2BQLa9AmRszntmMboEPS1t4tSO31qScXxy=G35uyB6NU72KxtA>