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 Message-ID: <3DA5C8E5.30808@dobrianov.net> Date: Thu, 10 Oct 2002 14:37:25 -0400 From: Ivan Dobrianov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Executing a script that needs DOS path Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Note-from-DJ: This may be spam Sorry if this has been answered a hundred times, but could not find anything the FAQ, doc, or archives. THE PROBLEM: o Say I have some intrepreter xxx.exe, that expects to get started like this xxx c:\home\my_script.xxx ... o I want to automate this process the usual way, by adding this to the begining of the script: #!/c/bin/xxx ... hoping to be able to say: my_script.xxx o *** This fails, because cygwin [or bash] passes the unix path /c/home/my_script.xxx to xxx.exe which it cannot interpret. Is there a solution to this OTHER THAN using a proxy shell that would do the unix-to-dos translation? The reason I don't like this solution is that the shell will glob and eat quotes, making it very hard to process filenames with spaces. Thanks for any hints! -- 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/