Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 To: cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ Path: not-for-mail From: Shankar Unni Subject: Re: Bridge between windows and Cygwin to use awk on windows files Date: Wed, 11 Sep 2002 09:51:56 -0700 Lines: 19 Message-ID: <3D7F74AC.5000000@cotagesoft.com> References: NNTP-Posting-Host: adsl-63-193-31-178.dsl.snfc21.pacbell.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1031763108 15510 63.193.31.178 (11 Sep 2002 16:51:48 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 11 Sep 2002 16:51:48 +0000 (UTC) User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en Igor Pechtchanski wrote: > You can already access all of your windows files with cygwin: > - from within bash/tcsh/sh: > $ cat /cygdrive/c/Temp/blah.txt | awk -e '...' In most cases, you can directly refer to the Windows filename natively: $ awk -e "..." c:/Temp/blah.txt No need for a "bridge". Remember to use forward slashes. The cygpath thing is useful in scripts (or if you want to normalize slashes), but is tedious to type at the command line each time. The only exception that I know of is "tar", which treats (for its output file argument) "c:/path" as "/path on hostname c".. -- Shankar. -- 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/