At 09:55 22.06.2001 +0100, james crease wrote:
>I still think it odd that the distribution of Perl for Windows doesn't
>mention this problem when using the standard M$ command window.
The problem disappears with Win2000, fwiw.
Aaron Craig
Programming
iSoftitler.com
it's not a perl problem, it's an m$ 'feature' (mainly found under NT lacking
some service packs/upgradss)
for example, on win98 i never had that problem, neither do i have it on
win2k or on my fully sp'd and upgraded winnt4 box
however on a few nt boxes having NOT had all service packs, i'm stuck
In message <[EMAIL PROTECTED]>,
Aaron Craig <[EMAIL PROTECTED]> writes
>At 21:49 20.06.2001 +0100, james crease wrote:
>>I have a perl script which generates many compilation errors which
>>scroll off the DOS window perl is running in. How do I capture (or
>>recover) the lines that have scrolle
At 21:49 20.06.2001 +0100, james crease wrote:
>I have a perl script which generates many compilation errors which scroll
>off the DOS window perl is running in. How do I capture (or recover) the
>lines that have scrolled away?
>--
>james crease
>
Use EditPlus2 as your editor. You can capture
In message <[EMAIL PROTECTED]>, Tim Musson
<[EMAIL PROTECTED]> writes
>Hey james,
>
>Thursday, June 21, 2001, 9:26:34 AM, you wrote:
>
>jc> The version of DOS I have on win98SE doesn't allow for a scroll
>jc> bar as suggested by one comment nor does it have a layout tab to
>jc> set the size of
On Thu, 21 Jun 2001, james crease wrote:
> Thanks to all for suggestions.
> Comments- I suspect Chas above has the likely solution.
> The version of DOS I have on win98SE doesn't allow for a scroll bar as
> suggested by one comment nor does it have a layout tab to set the size
> of the window alt
In message <993124108.25145.2.camel@cowens>, Chas Owens
<[EMAIL PROTECTED]> writes
>The problem is that the error messages are going to stderr instead of
>stdout. The standard DOS shell (command.com or cmd.exe depending on
>your system) doesn't understand how to capture stderr. The solution is
The problem is that the error messages are going to stderr instead of
stdout. The standard DOS shell (command.com or cmd.exe depending on
your system) doesn't understand how to capture stderr. The solution is
to get a better shell. Cygnus (now RedHat) makes cygwin a complete unix
style developm
likely to help as most of the errors are
consequential on the original "real " error, but thanks for the thought.
>
>
>-Original Message-
>From: james crease [mailto:[EMAIL PROTECTED]]
>Sent: 21 June 2001 09:26
>To: [EMAIL PROTECTED]
>Subject: Re: compilati
Thanks I had tried that already and doesn't seem to work at compile
time:-(
In message <00e401c0f9cc$02ee7340$0901a8c0@profit>, Jos I. Boumans
<[EMAIL PROTECTED]> writes
>try capturing the output:
>
>perl foo.pl > outputfile.txt
>
>all that perl spits out should be in the outputfile.txt then
>
try capturing the output:
perl foo.pl > outputfile.txt
all that perl spits out should be in the outputfile.txt then
regards,
Jos Boumans
- Original Message -
From: "james crease" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 10:49 PM
Subject: compilation
11 matches
Mail list logo
