From owner-freebsd-hackers Sun Nov 9 07:51:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA17094 for hackers-outgoing; Sun, 9 Nov 1997 07:51:17 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from phoenix.its.rpi.edu (phoenix.its.rpi.edu [128.113.161.45]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA17089 for ; Sun, 9 Nov 1997 07:51:13 -0800 (PST) (envelope-from dec@phoenix.its.rpi.edu) Received: from localhost (dec@localhost) by phoenix.its.rpi.edu (8.8.7/8.8.7) with SMTP id KAA06510; Sun, 9 Nov 1997 10:51:18 -0500 (EST) (envelope-from dec@phoenix.its.rpi.edu) Date: Sun, 9 Nov 1997 10:51:17 -0500 (EST) From: "David E. Cross" To: Joerg Wunsch cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Why doesn't /bin/echo use getopt? In-Reply-To: <19971109115007.JB56482@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sun, 9 Nov 1997, J Wunsch wrote: > As James Raynard wrote: > > > Because it's supposed to repeat its arguments instead of parse them? > > (with the exception of -n, of course). > > Tough question: how do you echo a "-n\n" then (without using > printf(1), of course)? The same way you rm(1) a file named -rf/? rm -- -rf/ for echo: echo -- -n\n That would work with getopt(3). -- David Cross ACS Consultant