Oh, and Nick gets the points :)
Nick Ing-Simmons wrote:
> Robert Johnson writes:
> >
> >> if ($^O eq 'MSWin32') returns true, then the cmd.exe
> system commands
> >> will be available.
> >
> >Other windows system commands do work. Like
> > `rename filename.txt newfile.txt`
> > print `dir
our help, especially Sisyphus :-)
Rob
> -Original Message-
> From: Sisyphus [mailto:[EMAIL PROTECTED]
> Sent: Monday, January 03, 2005 5:55 PM
> Cc: Robert Johnson;
> perl-win32-users@listserv.ActiveState.com;
> [EMAIL PROTECTED]
> Subject: Re: Errors dur
Sisyphus wrote:
Even if you do have a 'type.exe' in your path, I would expect that
there's some way of having `type` find the shell command rather than the
executable file. Sadly, I can't find a way of achieving that - tried
messing with $ENV{PATHEXT}, but that doesn't achieve the desired result
Robert Johnson wrote:
Sisyphus wrote:
Was that the full error statement ? Maybe there was more:
sh: type: filename.txt not found
No. Just "filename.txt not found"
if ($^O eq 'MSWin32') returns true, then the cmd.exe system commands
will be available.
Other windows system commands do work. Lik
Sisyphus wrote:
>
>
> Was that the full error statement ? Maybe there was more:
> sh: type: filename.txt not found
No. Just "filename.txt not found"
> if ($^O eq 'MSWin32') returns true, then the cmd.exe system commands
> will be available.
Other windows system commands do work. Like
`re
Robert Johnson wrote:
Sisyphus wrote:
Robert Johnson wrote:
Hmm. I tried doing a `type filename.txt`, and perl always
returns "filename.txt not found"
Was that the full error statement ? Maybe there was more:
sh: type: filename.txt not found
That's what I get when I enter the command in an MSYS
Sisyphus wrote:
>
> Robert Johnson wrote:
> >
> > Hmm. I tried doing a `type filename.txt`, and perl always
> > returns "filename.txt not found"
> >
> > (note: does exist in the working directory, and
> > entering "type filename.txt" from the MS command window
> > prompt works as designe
Erick Calder wrote:
"type" is an internal command (equivalent to the unix cat) so I'm not sure
you could call it like that from perl... the perl backticks are like a call
to the system() which expects a program to run (actual executable file on
the path), not an internal shell command.
No - you can
Robert Johnson wrote:
Hmm. I tried doing a `type filename.txt`, and perl always returns
"filename.txt not found"
(note: does exist in the working directory, and entering
"type filename.txt" from the MS command window prompt works as designed)
That's bizarre.
Could there be some shell (ie other t
t; Cc: [EMAIL PROTECTED];
> perl-win32-users@listserv.ActiveState.com
> Subject: Re: Errors during dmake test, after building perl 5.8.6
>
>
> Robert Johnson wrote:
> > Here are my results:
> >
Robert Johnson wrote:
Here are my results:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
../ext/IO/t/io_dup.t64 66.67% 2-5
comp/multiline.t62 33.33%
Here are my results:
Failed Test Stat Wstat Total Fail Failed List of Failed
---
../ext/IO/t/io_dup.t64 66.67% 2-5
comp/multiline.t62 33.33% 5-6
io/dup.t
12 matches
Mail list logo
