[ale] Bash question: | in find

[Geoffrey]

Joe wrote:

> Why weird? We're telling echo not to put any newlines anywhere, so
> unless and until "tar" spits out a result that doesn't go to stderr,
> we get a huge list of files, all on one line.  The tar command isn't
> going to emit a newline to stdout when it doesn't find the file we're
> asking for, right?  So the "grep" spits out that line, and the last
> file listed is the one containing the string.  Perhaps ksh emits a
> newline after the tar command for some reason, and bash doesn't?

tar produces a newline after each entry it prints, thus I don't 
understand how it is that all the listed files coming from tar are 
suddenly listed on one file.  Has nothing to do with the echo above it.

> 
> BTW, I used this, and discovered that in Slackware, the libXaw3d.so
> lives in the "l" distro directory, not (as I was expecting) "x" or
> "xap".
> 
> Cheers,
> 
> -- Joe
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
> 
> 

-- 
Until later: Geoffrey		esoteric at 3times25.net

The latest, most widespread virus?  Microsoft end user agreement.
Think about it...

_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale