Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 9 Dec 2004 11:03:35 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: findutils: "find /foo -printf '%P\n'" incorrect Message-ID: <20041209160335.GF11158@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <1102605989 DOT 7018 DOT 13 DOT camel AT mingus DOT array DOT ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1102605989.7018.13.camel@mingus.array.ca> User-Agent: Mutt/1.4.1i On Thu, Dec 09, 2004 at 10:26:29AM -0500, Tim Moorhouse wrote: >I'm not sure when this stopped working, but it was in the last couple of >weeks. > >Suppose I have a /foo/bar/baz file and do a "find /foo -printf '%P\n'". >I'm now getting "foo/bar/baz" as output instead of "bar/baz" - when >formatting the %P option of printf, it seems to be assuming that the >path on the command line is always "/" instead of what was actually >given. This is a bug in find 4.2.10. I've submitted a bug report to the upstream maintainer. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/