Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcsun!unido!nixba!mike
From: mike@nixba.UUCP (Mike Lyons)
Newsgroups: comp.unix.questions
Subject: Re: Stupid UNIX command syntax (Re: Stupidest UNIX Command)
Keywords: uniq, indent
Message-ID: <568@nixba.UUCP>
Date: 6 May 90 23:31:50 GMT
References: <23183@adm.BRL.MIL> <916@emdeng.Dayton.NCR.COM> <747@mwtech.UUCP> <7Z739XAxds13@ficc.uu.net> <1990May5.233549.4987@agate.berkeley.edu>
Reply-To: mike@nixba.UUCP (Mike Lyons)
Organization: Nixdorf Computer GSfBA, Nuremberg, West Germany
Lines: 23

In article <1990May5.233549.4987@agate.berkeley.edu> c60c-3cf@e260-3f.berkeley.edu (Dan Kogai) writes:
>In article <7Z739XAxds13@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>>You mean, the way if you have files named a and b, and you say "uniq ?",
>>it will trash "b"? Indent does it too. It's really a sick idea.
>>
>	But at least indent makes backup!  Uniq just kills it...

Nah, indent will blow away the second file named in a line like "indent a.c b.c"

I once pulled an "indent *.c" on a set of about 30 source files in a 
directory.  Indent complained that the last file name in the list was an
"unknown parameter," simultaneously blowing away the second file from the
list.  No, I didn't have a backup for the 2000+ lines of source, nor did I
even notice it until I tried to do a make right before a deadline. >-(

Peace,
  Mike

-- 
Michael D. Lyons / Nixdorf Computer AG / phone: +49 911 6415 609
Donaustrasse 36 :: D-8500 Nuernberg 60 :: Federal Republic of Germany
EUNET: mike@nixba.uucp  NERV: lyons.nue  OTHERWISE: uunet!linus!nixbur!lyons.nue
I'd change the world for the better...if I could get my hands on the source code