Path: utzoo!attcan!telly!lethe!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!axion!vision!ukpoit!paul
From: paul@ukpoit.co.uk (Paul Wood)
Newsgroups: comp.os.minix
Subject: Re: MacMinix config.h LINEWRAP option
Message-ID: <1654@ukpoit.co.uk>
Date: 21 Dec 90 10:34:16 GMT
References: <1639@ukpoit.co.uk> <1925@ria.ccs.uwo.ca>
Reply-To: paul@ukpoit.co.uk (Paul Wood)
Organization: iT - The Information Technology Business Of The Post Office
Lines: 29
Summary:
Expires:
Sender:
Followup-To:

In article <1925@ria.ccs.uwo.ca> webber@csd.uwo.ca (Robert E. Webber) writes:
>In article <1639@ukpoit.co.uk> paul@ukpoit.co.uk (Paul Wood) writes:
>
>.In fact when I executed the following:
>.    find / -name '*.[ch]' -exec grep LINEWRAP {} \;
>.                              the only line found was the one listed above.
>
>Actually, you probably want to do a search on *.[csh] when trying to track this
>sort of thing, since who knows what evil lurks in the .s files.  Also, a -print
>on the end of the find is helpful for those times when something is actually
>found.

I think you missed the point, the -print is not necessary. The above command
looked for LINEWRAP in all .c and .h files and only found the config.h entry.
Thats what the command was meant to do, and thats what it does. If I'd found
that LINEWRAP was used in more places, then I would have investigated further.

Adding a -print would cause every .c and .h filename to be printed. If I went
away to cook a meal (which I did), then by the time I got back to the screen
any evidence would have probably scrolled off the top of the screen. This is
not what I wanted. A command should do what you want it to do, no more, no less.

I do take your point however about .s files. I'll remember that for the future.

Paul Wood           | UUCP Mail:  paul@ukpoit.co.uk   |
31 Buttermere Drive | Bang-Style: ...!ukc!ukpoit!paul |
Dronfield Woodhouse | Voice:      +44 246 418031      |
Sheffield           |
England S18 5PX     |