From owner-freebsd-current Tue Sep 15 08:46:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01398 for freebsd-current-outgoing; Tue, 15 Sep 1998 08:46:38 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nike.ins.cwru.edu (nike.INS.CWRU.Edu [129.22.8.219]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01392 for ; Tue, 15 Sep 1998 08:46:28 -0700 (PDT) (envelope-from chet@nike.ins.cwru.edu) Received: (chet@localhost) by nike.ins.cwru.edu (8.8.7/CWRU-2.5-bsdi) id LAA11168; Tue, 15 Sep 1998 11:44:16 -0400 (EDT) (from chet) Date: Tue, 15 Sep 1998 11:40:36 -0400 From: Chet Ramey To: cracauer@cons.org Subject: Re: 'bug' in /bin/sh's builtin 'echo' Cc: crossd@cs.rpi.edu, freebsd-current@FreeBSD.ORG, chet@po.cwru.edu Reply-To: chet@po.cwru.edu In-Reply-To: Message from cracauer@cons.org of Tue, 15 Sep 1998 16:27:41 +0200 (id <19980915162741.A7479@cons.org>) Message-ID: <980915154036.AA11163.SM@nike.ins.cwru.edu> Read-Receipt-To: chet@po.CWRU.Edu Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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