Date: Mon, 30 Aug 1999 17:10:19 -0700 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Matthew Hunt <mph@astro.caltech.edu>, Mark Murray <mark@grondar.za> Cc: Bill Fumerola <billf@jade.chc-chimes.com>, "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>, Michael Haro <mharo@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/bin/mkdir mkdir.1 mkdir.c Message-ID: <199908310010.RAA24778@salsa.gv.tsc.tdk.com> In-Reply-To: Matthew Hunt <mph@astro.caltech.edu> "Re: cvs commit: src/bin/mkdir mkdir.1 mkdir.c" (Aug 30, 8:21am)
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 30, 8:21am, Matthew Hunt wrote: } Subject: Re: cvs commit: src/bin/mkdir mkdir.1 mkdir.c } 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 $ echo -n "`date -r 800000`"; echo Fri Jan 9 22:13:20 PST 1970 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?199908310010.RAA24778>