[bug #15167] find . -type d output is not in order

Update of bug #15167 (project findutils): Status:None => Invalid Open/Closed:Open => Closed ___ Reply to this item at:

[bug #15167] find . -type d output is not in order

Follow-up Comment #1, bug #15167 (project findutils): Actually in your example the contents of the directory are not sorted. Instead, ls is sorting them (ls is required to sort its arguments). The find program, on the other hand, is not required to do this. The find program just prints the fil

Re: findutils 4.2.27 on IRIX 5.3

On Wed, Dec 07, 2005 at 04:55:38PM +0100, Georg Schwarz wrote: > Dear developers, > > findutils 4.2.27 does not compile on IRIX 5.3: [...] > cfe: Error: ./mbchar.h: 157: Cannot open file wchar.h for #include [...] > IRIX 5.3 does not have wchar.h. Later versions (1995, I think) of the ANSI C stan

perm.texi from coreutils

A documentation patch that I sent to the coreutils folks about a few typos in perm.texi was applied last month. findutils could update its "Permissions" section of the file by getting the latest version from them. - Findutils version:

Re: updatedb files portable?

Further followup on my mail from yesterday. Ran a few more experiments: A database created by 4.1 on Linux can be read by either 4.1 or 4.2.26 on Linux and Solaris. A database created with 4.2.26 (and --old-format) on Linux can be read by 4.1 and 4.2.26 on linux. However, both 4.1 and 4.2.2

[bug #15167] find . -type d output is not in order

URL: Summary: find . -type d output is not in order Project: findutils Submitted by: None Submitted on: Wed 12/07/05 at 19:44 Category: find Se

findutils 4.2.27 on IRIX 5.3

Dear developers, findutils 4.2.27 does not compile on IRIX 5.3: ... Making all in lib cp ./fnmatch_.h fnmatch.h-t mv fnmatch.h-t fnmatch.h cp ./getopt_.h getopt.h-t mv getopt.h-t getopt.h sed -e 's/@''HAVE__BOOL''@/0/g' < ./stdbool_.h > stdbool.h-t

Re: Quoting of unprintable characters in the output of find

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to James Youngman on 12/7/2005 1:43 AM: > > This means that I'm considering changing the output quoting method for > -ls and -print where the output goes to a tty. Should I also consider > changing -ls and -fls to just print the literal pat

Quoting of unprintable characters in the output of find

At the moment, the -ls and -fls actions always quote 'unprintable' characters, supposedly for compatibility with 'ls' itself. However, 'ls' only actually does this if stdout is a terminal. There is a tension then between aligning the behaviour of -ls with the actual 'ls' in GNU coreutils, and pre

[patch #4683] Spelling corrections in manual find.texi

URL: Summary: Spelling corrections in manual find.texi Project: findutils Submitted by: ashawley Submitted on: Wed 12/07/05 at 03:14 Category: documentation im

[patch #3730] Audit of man pages with manual

Follow-up Comment #2, patch #3730 (project findutils): I'm refreshing myself on the work I had done in February. I recall a patch related to some other fixes but not one for reconciling the differences between the manual and man pages. Looking quickly over my audit notes, the only glaring differ