Xref: utzoo comp.os.misc:371 comp.unix.wizards:5862 Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!lll-tis!ames!ptsfa!hoptoad!academ!uhnix1!sugar!peter From: peter@sugar.UUCP (Peter da Silva) Newsgroups: comp.os.misc,comp.unix.wizards Subject: Re: Command interfaces Message-ID: <1299@sugar.UUCP> Date: 22 Dec 87 13:33:02 GMT References: <1257@boulder.Colorado.EDU> <6840002@hpcllmv.HP.COM> <9555@mimsy.UUCP> <5754@oberon.USC.EDU> Organization: Sugar Land UNIX - Houston, TX Lines: 23 In article <5754@oberon.USC.EDU>, blarson@skat.usc.edu (Bob Larson) writes: > In article <142@piring.cwi.nl> jack@cwi.nl (Jack Jansen) writes: > >I definitely prefer > >for i in *.[ch]; do > > diff old/$i $i >$i.diff > >done > I never had time to dig to deep into my unix manuals for this. It > doen't look any more intuitive to me than the primos example. The fact that half a dozen people so far have come up with this command line should tell you something. Here's how it works: for each file, i, that matches "*.[ch]" diff the copy of that file in "old" with the copy in the current directory, putting the output in a file of the same name but with a suffix of ".diff" appended. Which is what your example does... but less explicitly. -- -- Peter da Silva `-_-' ...!hoptoad!academ!uhnix1!sugar!peter -- Disclaimer: These U aren't mere opinions... these are *values*.