Re: problem with find/grep

2004-10-13 Thread Christopher Faylor
On Wed, Oct 13, 2004 at 07:43:33PM -0700, Joshua Daniel Franklin wrote: >On Tue, 12 Oct 2004 12:04:11 -0600, Mark Paulus <[EMAIL PROTECTED]> wrote: >> Thanks. I was not aware of the -print0 option. This is >> what I love about *n*x: Always something new to learn, >> or another way to find a solu

Re: problem with find/grep

2004-10-13 Thread Joshua Daniel Franklin
On Tue, 12 Oct 2004 12:04:11 -0600, Mark Paulus <[EMAIL PROTECTED]> wrote: > Thanks. I was not aware of the -print0 option. This is > what I love about *n*x: Always something new to learn, > or another way to find a solution. What! Do NOT use -print0! It will null-terminate EVERY LINE! -- Unsu

Re: problem with find/grep

2004-10-12 Thread Brian Dessent
Mark Paulus wrote: > > Another issue I've run into with find, but typically when I pipe > it to xargs is that directories/files with spaces in the names cause > all kind of disruption. Add "-print0" to your find arguments and "-0" to your xargs arguments and that problem will disappear. Brian -

Re: problem with find/grep

2004-10-12 Thread Mark Paulus
Thanks. I was not aware of the -print0 option. This is what I love about *n*x: Always something new to learn, or another way to find a solution. On Tue, 12 Oct 2004 13:14:12 -0400, Christopher Faylor wrote: >On Tue, Oct 12, 2004 at 11:00:35AM -0600, Mark Paulus wrote: >>Another issue I've r

Re: problem with find/grep

2004-10-12 Thread Igor Pechtchanski
On Tue, 12 Oct 2004, Mark Paulus wrote: > Another issue I've run into with find, but typically when I pipe > it to xargs is that directories/files with spaces in the names cause > all kind of disruption. Not related to this thread, and actually not Cygwin-specific. Use "find ... -print0 | xargs

Re: problem with find/grep

2004-10-12 Thread Christopher Faylor
On Tue, Oct 12, 2004 at 11:00:35AM -0600, Mark Paulus wrote: >Another issue I've run into with find, but typically when I pipe >it to xargs is that directories/files with spaces in the names cause >all kind of disruption. So use "find -print0 | xargs -0". cgf -- Unsubscribe info: http://cyg

Re: problem with find/grep

2004-10-12 Thread Mark Paulus
Another issue I've run into with find, but typically when I pipe it to xargs is that directories/files with spaces in the names cause all kind of disruption. On Tue, 12 Oct 2004 12:25:15 -0400 (EDT), Igor Pechtchanski wrote: >On Tue, 12 Oct 2004, Daniel Miller wrote: >> On linux systems, I typic

Re: problem with find/grep

2004-10-12 Thread Daniel Miller \(IMI\)
> On Tue, 12 Oct 2004, Daniel Miller wrote: > > > On linux systems, I typically to global searches with a command such as: > > > > find . -name "*.[ch]*" -exec grep -H -n stuff {} \; > > > > and this works nicely. However, when I try the same command under Cygwin > > (from a 4NT prompt, not Ba

Re: problem with find/grep

2004-10-12 Thread Igor Pechtchanski
On Tue, 12 Oct 2004, Daniel Miller wrote: > On linux systems, I typically to global searches with a command such as: > > find . -name "*.[ch]*" -exec grep -H -n stuff {} \; > > and this works nicely. However, when I try the same command under Cygwin > (from a 4NT prompt, not Bash), I get "f

problem with find/grep

2004-10-12 Thread Daniel Miller
On linux systems, I typically to global searches with a command such as: find . -name "*.[ch]*" -exec grep -H -n stuff {} \; and this works nicely. However, when I try the same command under Cygwin (from a 4NT prompt, not Bash), I get "find: missing argument to '-exec' ". I tried a vari