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: Tue, 3 Sep 2002 13:06:25 +1000 (EST) From: luke DOT kendall AT cisra DOT canon DOT com DOT au Subject: How do you write scripts with portable filenames? To: cygwin AT cygwin DOT com In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Message-Id: <20020903030623.2413C586E@ivory.research.canon.com.au> "Portable" between Cygwin and Unix systems, that is. I'm thinking of the problems caused in particular by command filenames having extensions on Windows and none on Unix. E.g. if I say "ls x", where X.EXE exists, ls will output x (as long as nocaseglob is set). But "strings x" fails because the file x doesn't exist. Is my goal of writing portable shell scripts doomed? Am I going to have to say "strings x.exe"? :-( Is there any cool Cygwin magic to help with this, like there is in U/Win? luke -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/