Re: In scripts suddenly must use perl.exe rather than perl

On 7/10/06, David Christensen [EMAIL PROTECTED] wrote: zzapper wrote: c:/usr/local/bin/perl sdbk.pl $* (hard path to activestate perl) It was my experience that mixing Cygwin and ActiveState Perl was a recipe for frustration. Why can't you just use Cygwin Perl? David I was recently

Reading Term::ReadKey support for ActiveState Perl and Cygwin

Hi all, I've been racking my brains trying to read keystrokes in a Cygwin shell with ActiveState Perl. Has anyone worked out how to read individual keystrokes with a Perl script running in a Cygwin shell or SSH session? We have standardized on ActiveState perl here (as not all servers are

Re: Reading Term::ReadKey support for ActiveState Perl and Cygwin

Yes, I've done some more research and experimentation and determined the lack of STDIN and STOUT in Cygwin makes it impossible to do what I would like with ActiveState Perl. I don't mind Cygwin Perl at all, but here we must use the ActiveState implementation (by policy). Is this situation likely

Environment variables in 1.5.19(0.150/4/2) 2006-01-20 13:28

Hi all, I'm having trouble with environment variables when running commands through ssh. I have applied this fix to my /etc/profile: # When initiating a Cygwin bash session via SSH, Cygwin only registers the environment variables # for the SYSTEM account, not for the individual user's account.