Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10 5/3/83; site oliveb.UUCP Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!whuxl!houxm!ihnp4!zehntel!dual!amd!fortune!hpda!hplabs!oliveb!jerry From: jerry@oliveb.UUCP (Jerry Aguirre) Newsgroups: net.bugs.4bsd,net.unix Subject: Re: Bug in find(1) in 4.2BSD? Message-ID: <193@oliveb.UUCP> Date: Tue, 9-Oct-84 14:28:37 EDT Article-I.D.: oliveb.193 Posted: Tue Oct 9 14:28:37 1984 Date-Received: Thu, 11-Oct-84 08:19:44 EDT References: <2343@ucbvax.ARPA> <29@drivax.UUCP> Organization: Olivetti ATC, Cupertino, Ca Lines: 17 No the csh does not eat {}. Actually I was supprised that it didn't as {a,b}c does have special meaning to the csh. Apparently the shell recognizes that {} cannot be expanded and so leaves it alone. The real problem with the posted line is that there is no space between the {} and the \;. That is: find . -name something -exec ls -l {}\; won't work but find . -name something -exec ls -l {} \; will. Note space ^ Remember that the \; is the terminating argument for the string of arguments beginning with -exec. To be recognized it must be a separate argument. Jerry Aguirre {hplabs|fortune|idi|ihnp4|ios|tolerant|allegra|tymix}!oliveb!jerry