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 X-Originating-IP: [151.203.219.131] X-Originating-Email: [mgainty AT hotmail DOT com] X-Sender: mgainty AT hotmail DOT com From: "Martin Gainty" To: Subject: Re: Re: Question on Perl (.pl) association Date: Wed, 17 Mar 2004 06:59:09 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-ID: X-OriginalArrivalTime: 17 Mar 2004 11:59:11.0193 (UTC) FILETIME=[42748490:01C40C17] X-IsSubscribed: yes David: I this solution works on windows But how do we get .pl association with CYGWIN Perl? Many Thanks, Martin >From: zzapper > >To: cygwin AT cygwin DOT com > >Subject: Re: Question on Perl (.pl) association > >Date: Wed, 17 Mar 2004 09:44:09 +0000 > >MIME-Version: 1.0 > >Received: from sources.redhat.com ([67.72.78.213]) by mc11-f7.hotmail.com with Microsoft SMTPSVC(5.0.2195.6824); Wed, 17 Mar 2004 01:44:50 -0800 > >Received: (qmail 22365 invoked by alias); 17 Mar 2004 09:44:15 -0000 > >Received: (qmail 22351 invoked from network); 17 Mar 2004 09:44:14 -0000 > >Received: from unknown (HELO main.gmane.org) (80.91.224.249) by sources.redhat.com with SMTP; 17 Mar 2004 09:44:14 -0000 > >Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1B3Xav-0001KK-00 for ; Wed, 17 Mar 2004 10:44:13 +0100 > >Received: from cpc3-oxfd4-4-0-cust194.oxfd.cable.ntl.com ([80.3.247.194]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Mar 2004 10:44:13 +0100 > >Received: from david by cpc3-oxfd4-4-0-cust194.oxfd.cable.ntl.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Mar 2004 10:44:13 +0100 > >X-Message-Info: JGTYoYF78jHvE2pZE6ZN2hEoN6MG+9vJ > >Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm > >Precedence: bulk > >List-Unsubscribe: > >List-Subscribe: > >List-Archive: > >List-Post: > >List-Help: , > >Mail-Followup-To: cygwin AT cygwin DOT com > >Delivered-To: mailing list cygwin AT cygwin DOT com > >Lines: 37 > >Message-ID: > >References: <18840roaobffn DOT dlg AT thorstenkampe DOT de> > >X-Complaints-To: usenet AT sea DOT gmane DOT org > >X-Gmane-NNTP-Posting-Host: cpc3-oxfd4-4-0-cust194.oxfd.cable.ntl.com > >X-Newsreader: Forte Free Agent 1.93/32.576 English (American) > >Return-Path: cygwin-return-89747-mgainty=hotmail DOT com AT cygwin DOT com > >X-OriginalArrivalTime: 17 Mar 2004 09:44:50.0303 (UTC) FILETIME=[7DCA50F0:01C40C04] > > > >On Tue, 16 Mar 2004 23:39:58 +0100, wrote: > > > > >* Martin Gainty (2004-03-16 21:56 +0100) > > >> How does one associate CYGWIN Perl with .pl extensions within CYGWIN > > >> environment? > > > > > >Same as in the Windows environment: "ftype" in connection with "assoc" > > >(or more convenient with "associate" from the ResourceKit). > > > > >On MKS I used to have this in a setup script .profile > > > >(ftype is builtin to Windows Command) > > > >ftype Perl 'c:/usr/local/bin/perl.exe "%1" %*' > > > >The advantage of FTYPE is that it allows you to specify which Perl you > >want used (when you might have several installed, and also to ignore > >the shebang which might be set for a distant server > > > >Better I could use Windows Environment variable PATHEXT > > > > >echo $PATHEXT > >.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.php;.pl > > > >so that I could call a perl script hello.pl > > > >just with "hello" > > > >Haven't got this to work with CYG > > > > > >zzapper (vim, cygwin, wiki & zsh) > >-- > > > >vim -c ":%s/^/WhfgTNabgureRIvzSUnpxre/|:%s/[R-T]/ /Ig|:normal ggVGg?" > > > >http://www.vim.org/tips/tip.php?tip_id=305 Best of Vim Tips > > > > > >-- > >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/ > > > > -- 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/