Re: find printing full paths

(I'm not entirely certain this still belongs on both lists... but I'm also not sure that it doesn't.) Bob Proulx wrote: The Wanderer wrote: What I was doing at the time, so far as I remember, was: for i in `ls path/to/directory1/ path/to/directory2/` ; do ls -l $i && $i ; done but that d

Re: find printing full paths

The Wanderer wrote: > What I was doing at the time, so far as I remember, was: > > for i in `ls path/to/directory1/ path/to/directory2/` ; do ls -l $i && > $i ; done > > but that didn't work because the filename printed by the subshell did > not exist in the present directory. Would this have

Re: find printing full paths

Bob Proulx wrote: The Wanderer wrote: For the little it's worth, I also find myself wanting to do something like this from time to time, usually in a context in which find is not a satisfactory alternative - or, at best, in which it would be awkward and potentially difficult to construct a fin

find printing full paths (was: filutils 4.1)

James Youngman wrote: > The Wanderer wrote: > >For the little it's worth, I also find myself wanting to do something > >like this from time to time, usually in a context in which find is not a > >satisfactory alternative - or, at best, in which it would be awkward and > >potentially difficult to co

Re: filutils 4.1

On 6/15/06, The Wanderer <[EMAIL PROTECTED]> wrote: For the little it's worth, I also find myself wanting to do something like this from time to time, usually in a context in which find is not a satisfactory alternative - or, at best, in which it would be awkward and potentially difficult to cons

Re: small compile nit: extern vs static

On 6/15/06, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: Yes, I'm speaking of the CVS HEAD sources, sorry if that wasn't clear. There is an extern declaration in find/defs.h, in the tree obtainable by cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/findutils \ co findutils Sorry, you're right.

[bug #16269] The manual gives an incorrect example

Update of bug #16269 (project findutils): Assigned to:None => jay ___ Reply to this item at: __

[bug #16269] The manual gives an incorrect example

Update of bug #16269 (project findutils): Status:None => Fixed ___ Follow-up Comment #2: Thanks. I've now fixed this in the 4.3.x CVS code. This problem is fixed in the CVS code

[bug #16744] -nowarn produces a warning if specified after non-option

Update of bug #16744 (project findutils): Status:None => Fixed Assigned to:None => jay ___ Follow-up Comment #1: Fixed in 4.3.x (

[bug #16520] find is not finding certain strangely named files

Update of bug #16520 (project findutils): Status:None => Works For Me Assigned to:None => jay Open/Closed:Open => Closed __

[bug #16520] find is not finding certain strangely named files

Follow-up Comment #8, bug #16520 (project findutils): James Youngman wrote: > I would guess that the byte sequence in the filename does not > correspond with a valid sequence of bytes in the character > encoding systenm you have configured for your environment I am pretty sure that was the caus