From owner-freebsd-current Tue Sep 15 11:57:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06489 for freebsd-current-outgoing; Tue, 15 Sep 1998 11:57:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06484 for ; Tue, 15 Sep 1998 11:57:42 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from eggbeater.cs.rpi.edu (crossd@eggbeater.cs.rpi.edu [128.213.8.32]) by cs.rpi.edu (8.9.1/8.9.1) with SMTP id OAA06890; Tue, 15 Sep 1998 14:52:14 -0400 (EDT) Date: Tue, 15 Sep 1998 14:52:11 -0400 (EDT) From: "David E. Cross" To: Martin Cracauer cc: Joe Moss , chet@po.cwru.edu, freebsd-current@FreeBSD.ORG Subject: Re: 'bug' in /bin/sh's builtin 'echo' In-Reply-To: <19980915194623.A7225@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Sep 1998, Martin Cracauer wrote: > This one doesn't specify a -e option (in fact it specifies that echo > should take no options at all), everything behaves as if -e was > specified and all switches are echoed. I can hardly accept that as > something to follow. With '\c', you don't need '-n' any more. This is already the way our own /bin/echo works, and that has not seemed to have broken anything. It also has the support of a 'standard', and most (all?) of the commercial UNIX providers following it (anyone want to try on HP-UX and OSF/Digital UNIX?). The change to make is *trivial*, in the 'builtin' echo.c in sh you need to uncomment the line "#define eflag 1" (on a side note, our 'ls' does not support the '-n' flag; this would be me volenteering to fix if no one else is interested in doing so) -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message