X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 7 Jul 2008 14:54:29 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Ending space in file names is stripped, "sometimes"? Message-ID: <20080707125429.GA25687@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Jul 7 14:13, Kent Boortz wrote: > > [For some reason this email got stuck in my "not sent" folder] > > Mark Geisert writes: > > Thanks for the cygcheck output, but if the problem is observed only "sometimes" > > maybe you could provide an example? > > Sorry, I was not clear, I did not mean it was "random". > > I meant that 'ls "foo "' complained the directory was not found if the > space was included, while "find" did happily accept "foo", "foo ", > "foo " as argument meaning the same thing, still including the extra > spaces in the output. This is shown in the examples I included. There were no examples in your OP, just a cygcheck output without any further comment. Trailing spaces (and dots) in filenames are silently dropped by Win32 function calls. This explains some of the weird effects when trying to use them. This will change with Cygwin 1.7 which doesn't use Win32 functions for file access anymore. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/