Re: find -print output escaping not documented?

James Youngman wrote: > Bob Proulx wrote: > > If stdout is a tty then the newline is mapped to '?'. But it isn't > > mapped if the output is redirected to a pipe or a file. This applies > > to the printf %p format too. > > Yes. This is deliberate in the sense that the code does this > delibera

[bug #40803] ftsfind.1: \- changed to - (hyphen) in the name of an option

Update of bug #40803 (project findutils): Status:None => Invalid Assigned to:None => jay Open/Closed:Open => Closed Summary:

[bug #13303] find should filter out non-printable characters if outputting to tty

Follow-up Comment #7, bug #13303 (project findutils): Bob Proulx suggests that this change may have introduced a POSIX non-compliance. ___ Reply to this item at:

Re: find -print output escaping not documented?

On Fri, Jan 10, 2014 at 8:20 PM, Bob Proulx wrote: > > Undocumented behavior. Here is the test case: > > mkdir /tmp/testdir > mkdir /tmp/testdir/"newline > newline" > > find /tmp/testdir -print > /tmp/testdir > /tmp/testdir/newline?newline > > Note the '?' in the above. No '?' in the below that