X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: "Michael Kairys" <kairys AT comcast DOT net>
Subject:  Re: Wish Setup would accept my Perl
Date:  Tue, 11 Dec 2007 07:21:20 -0500
Lines: 46
Message-ID: <fjlvb9$u90$1@ger.gmane.org>
References:  <loom DOT 20071105T183528-568 AT post DOT gmane DOT org> 	 <loom DOT 20071206T171108-921 AT post DOT gmane DOT org> 	 <alpine DOT DEB DOT 0 DOT 82 DOT 0712061353080 DOT 18424 AT pilot DOT trilug DOT org> 	 <loom DOT 20071206T192047-253 AT post DOT gmane DOT org> 	 <loom DOT 20071207T213211-833 AT post DOT gmane DOT org> <183c528b0712071441k4f27cea9lebf6234f592f2eb0 AT mail DOT gmail DOT com>
Mime-Version:  1.0
Content-Type:  text/plain; 	format=flowed; 	charset="iso-8859-1"; 	reply-type=original
Content-Transfer-Encoding:  7bit
In-Reply-To: <183c528b0712071441k4f27cea9lebf6234f592f2eb0@mail.gmail.com>
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

"Brian Mathis" <brian DOT mathis AT gmail DOT com> wrote in message 
news:183c528b0712071441k4f27cea9lebf6234f592f2eb0 AT mail DOT gmail DOT com...

> I think the biggest problem you're having is conceptual.  It's easy to
> view a bash prompt as just a better DOS prompt that gives you unix
> commands in addition to windows command line commands.
> ...
> The solution is to start breaking the habit of using a bash prompt for
> windows commands.  Open a DOS command window and use that (as much as
> it hurts). Any perl run from that command window will use AS perl.
> Even "better", don't run AS perl scripts from a prompt at all,
> double-click on them and start them like any other windows app.  Do
> not try to use AS perl from a bash prompt.  Anything run from a bash
> prompt should use cygwin perl.

Actually I tend to go the other way. I do most of my work in a bash shell 
and if I need to use a Windows command I start a command prompt. (BTW, 
thanks to all of you who pointed out Console2 - I love it!)

However if I were to follow your last advice I would have to convert my AS 
scripts to Cygwin as noted previously. Other parts of this thread have 
discussed the issues I've created for myself, and they are in fact 
relatively minor, except that as I noted I am rather uncomfortable with the 
idea that I must run Perl/Tk under an X server.

But let me ask you this, please: what about running Cygwin programs from 
Windows. Some of the Perl scripts that I run from bash I also run as 
integrated tools from Eclipse, Windows Explorer, etc., and some of them rely 
on Cygwin commands. (The detail is a bit grungy: it's actually a Tk 
interface to SCCS.)

To accomplish this I have put cygwin\bin on my Windows path. What is your 
opinion on that, please?

> You should not have AS perl in your cygwin path -- cygwin should not
> know about it at all.

Yes, I now do not have AS Perl in my Cygwin path.

> I also think this is a bad idea:
> "#!/local/perl/bin/perl finds my AS perl (which is in D:\Local\Perl,
> and D:\Local is mounted on /local)"

Why, please?




--
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/