Re: -fprint F corrupts output, F, when stderr is closed

2005-07-01 Thread James Youngman
On Fri, Jul 01, 2005 at 12:33:35PM +0200, Jim Meyering wrote: > Here's the patch: Thanks! > (assuming you get lib/stdio-safer.[ch] from coreutils -- > I'll see about getting it into gnulib) I don't. My process only allows me to take pristine gnulib files. Therefore since the module you describ

Re: -fprint F corrupts output, F, when stderr is closed

2005-07-01 Thread Jim Meyering
[EMAIL PROTECTED] (James Youngman) wrote: > On Fri, Jul 01, 2005 at 12:33:35PM +0200, Jim Meyering wrote: > >> Here's the patch: > > Thanks! > >> (assuming you get lib/stdio-safer.[ch] from coreutils -- >> I'll see about getting it into gnulib) > > I don't. My process only allows me to take pristi

complete patch for -fprint vs. closed stderr bug

2005-07-01 Thread Jim Meyering
In case you haven't already gotten to it, here's the patch I sent a few hours ago, but with the import-gnulib.sh part and a ChangeLog: Demonstrate that pre-patched find has the bug: $ find no-such -fprint FF 2>&- || cat FF find: no-such: No such file or directory Demonstrate that it's fixed i

-fprint F corrupts output, F, when stderr is closed

2005-07-01 Thread Jim Meyering
[ Sorry to report a bug to the list, but I dislike filling in web forms. If there were a mail-to-savannah-bug gateway I'd be happy to use it. ] When stderr is initially closed, find's `-fprint F' and `-fprintf F' predicates can corrupt their output file F with diagnostic output intended for t

Re: [patch #3751] Typos and small suggestions to find.texi

2005-07-01 Thread Aaron S. Hawley
The file size difference of 33Kb and 110Kb is from fixing the whitespace and paragraph filling for other lines in the file and not just my edits. Emacs made it easy to find long lines that I could then choose to justify or not. One doesn't want to fill the entire buffer, wholesale, without checkin