Ugh, top-posting... Reformatted. On Wed, 10 Jan 2007, Kevin T Cella wrote:
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Igor Peshansky > Sent: Wednesday, January 10, 2007 9:06 AM > To: Kevin T Cella > Cc: [EMAIL PROTECTED] <http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Thanks. > Subject: Re: activestate perl on cygwin > > > On Mon, 8 Jan 2007, Kevin T Cella wrote: > > > > > I understand the trouble with using Activestate perl on cygwin is > > > the path conversion problem. Searching online I found the following > > > wrapper script useful for most perl commands: > > >[snip buggy script] > > > > > > An example of one that does not work is as follows: > > > > > > perl -e 'print join "\n", @INC, "\n";' > > > > > > For some reason, the script above strips the single quotes from the > > > command and therefore does not execute the command properly. Please > > > advise. > > > > The reason the script above strips the single quotes from the command > > is because it's buggy. > > [snip] > > > > However, none of these issues are Cygwin-specific (with a possible > > exceptions of the typo and using "cygpath -m" instead of "cygpath -w" to > > save yourself the trouble of the extra backslash translation). Any good > > tutorial on bash should show you how to properly quote the arguments. > > You may also want to search the Cygwin list archives, where this exact > > issue comes up once in a while (usually in the context of paths with > > spaces). > > Offer an alternative. As I mentioned in my original post, I got this > script online. In using it I found it was not sufficient, I started this > thread in the hopes that someone would provide me with a better wrapper > script. I did. <http://cygwin.com/ml/cygwin/2007-01/msg00270.html>. > Instead I got a bunch of replies about how it is a bad idea to > use Activestate with cygwin. My scripts are written to make my life on > Windows easier, so that means using Windows specific code to automate > common tasks. Ideally I'd prefer to stay in a pure Linux environment, > but for reasons I do not need to go into, I am stuck with Windows. It > was my understanding that the intent of this mailing list was to offer a > place to discuss issues involving cygwin and develop solutions to those > problems. Seeing as I do not have a whole lot of free time to research a > better solution, I hoped a quick answer would be provided via this > medium. While I appreciate the suggestions that have been made on this > thread, I want to install two copies of the perl interpreter or port my > existing scripts to cygwin as that appears to be the compromise. Are > there any other ideas? Rant aside, there is nothing Cygwin-specific about writing such a wrapper script. As I said, any good bash tutorial would have contained enough information for you to write one. Since this is not a bash support list, discussion of techniques for making such scripts work is off-topic. Besides, it's been discussed to death at least 3 times that I recall -- and it's all in the archives of this very list. The script in my message above has definitely been posted before, and even in a similar context. In fact, that discussion is the 5th match when searching the list archives for "activestate wrapper", and the 1st (yes, first) match when Googling for "activestate wrapper site:cygwin.com inurl:ml" (or even for "activestate wrapper cygwin"). That's why we have the web archives -- to hopefully avoid rehashing the same issues over and over again. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED] ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Freedom is just another word for "nothing left to lose"... -- Janis Joplin -- 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/