Date: Tue, 15 Sep 1998 11:40:36 -0400 From: Chet Ramey <chet@nike.ins.cwru.edu> To: cracauer@cons.org Cc: crossd@cs.rpi.edu, freebsd-current@FreeBSD.ORG, chet@po.cwru.edu Subject: Re: 'bug' in /bin/sh's builtin 'echo' Message-ID: <980915154036.AA11163.SM@nike.ins.cwru.edu> In-Reply-To: Message from cracauer@cons.org of Tue, 15 Sep 1998 16:27:41 %2B0200 (id <19980915162741.A7479@cons.org>)
next in thread | previous in thread | raw e-mail | index | archive | help
> Also, what happens if \c isn't at the end of the string? The -n > construct seems superiour to me. Everything after the \c should be ignored. > Anyway, please file a PR about this. I'll take care of it when my > Posix documents arrive, which should be in time for the 3.0 release. POSIX.2 says very little about `echo'; it recommends using printf(1) instead. It defines nothing, and allows everything. Specifically, arguments which contain a backslash, or a first argument of `-n', are `implementation defined'. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Chet Ramey, Case Western Reserve University Internet: chet@po.CWRU.Edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?980915154036.AA11163.SM>