Date: Mon, 30 Aug 1999 11:52:32 -0700 (PDT) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: mph@astro.caltech.edu (Matthew Hunt) Cc: mark@grondar.za (Mark Murray), billf@jade.chc-chimes.com (Bill Fumerola), mharo@FreeBSD.org (Michael Haro), cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/bin/mkdir mkdir.1 mkdir.c Message-ID: <199908301852.LAA66286@gndrsh.dnsmgr.net> In-Reply-To: <19990830082157.A89944@wopr.caltech.edu> from Matthew Hunt at "Aug 30, 1999 08:21:57 am"
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mon, Aug 30, 1999 at 08:19:55AM +0200, Mark Murray wrote: > > > EG- A couple of years ago, someone wanted date(1) to not put a \n at > > the end of its output (for whatever reason), and he added a new -n > > flag to do it. Canonical UNIX method to do this is > > > > $ echo -n `date` > > Which is, of course, not quite the same as omitting the newline. > > The output of date(1) can contain multiple sequential spaces. After > being split into arguments, and recombined by echo(1), they'll be > reduced to one space. > > wopr:~$ date -r 800000 > Fri Jan 9 22:13:20 PST 1970 > wopr:~$ echo -n `date -r 800000`; echo > Fri Jan 9 22:13:20 PST 1970 > > Of course, I don't really have any need to get the output of date(1) > without the newline, but I could do something like this... > > wopr:~$ date -r 800000 | perl -pe 'chomp' > Fri Jan 9 22:13:20 PST 1970wopr:~$ Ever heard of ``IFS=''? Invoking perl to handle what can easily been done within the shell itself is expensive. -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908301852.LAA66286>