From owner-freebsd-current Tue Sep 15 18:17:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27576 for freebsd-current-outgoing; Tue, 15 Sep 1998 18:17:17 -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 SAA27570 for ; Tue, 15 Sep 1998 18:17:14 -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 VAA14257 for ; Tue, 15 Sep 1998 21:16:55 -0400 (EDT) Date: Tue, 15 Sep 1998 21:16:52 -0400 (EDT) From: "David E. Cross" To: freebsd-current@FreeBSD.ORG Subject: /bin/echo and /bin/sh:echo sync-up 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 Ok... I think I will do this myself (sync /bin/echo and the sh built-in echo). I am going to sync them both to be the BSD normal (-n/-e), and I think I will throw in the GNU '-E' option as well. I will also add in an environment variable that will let peopel chosse the SysV if they need it. I don't know a good name for the variable,... current thoughts are 'echoopts' (that you would put '-e' or '-ne', whatever into), or 'SYSV' (that has the advantage of possibly a further scope, wher a person could export SYSV and get a more SYSV-ish environment all arround. Ideas? -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message