tobold.org

correct • elegant • free

△ comp.unix.shell △

◅ using sed substitute command

Passwd/Shadow conflict access control ▻

grep behaves differently in find

In article <azqe4.954$oR1.5953@grover.nit.gwu.edu>,
Christopher J. Mattern <syscjm@gwu.edu> wrote:
>{} means "put the filename you found here to
>construct the command to be executed".  It's
>actually unnecessary here, since if there is no
>{} it defaults to putting the filename at the
>end

No `find' I have ever used does this.

Tim.
--
Tim Goodwin   | "If you don't know what closures are, you probably don't
Leicester, UK | want to know what closures are." -- Larry Wall

Original headers:

From: tjg@star.le.ac.uk (Tim Goodwin)
Newsgroups: comp.unix.shell
Subject: Re: grep behaves differently in find
Date: 11 Jan 2000 11:24:32 -0000
Message-ID: <85f3u6$iq8$1@ltpcg.star.le.ac.uk>
References: <850ld7$nle$1@nnrp1.deja.com>
  <ZiN5OMyEOWm6Sso4x8CK2OUbIgeI@4ax.com>
  <azqe4.954$oR1.5953@grover.nit.gwu.edu>

△ comp.unix.shell △

◅ using sed substitute command

Passwd/Shadow conflict access control ▻