[EMAIL PROTECTED] (Rob Dixon) wrote:
> We Unix people find we Windows people very strange
:)
...
> test.pl < test.txt
> and
> type test.txt | perl test.pl
>
> are just two (increasingly weird) versions of
>
> perl test.pl test.txt
>
We Unix people want to rip out the operating system
som
Mark Lobue wrote:
> > -Original Message-
> > From: LoBue, Mark [mailto:[EMAIL PROTECTED]
> > Sent: Monday, July 21, 2003 9:26 AM
> > To: '[EMAIL PROTECTED]'
> > Subject: STDIN and STDOUT on Windows
> >
> >
> > Hello,
> >
&
> -Original Message-
> From: LoBue, Mark [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 21, 2003 9:26 AM
> To: '[EMAIL PROTECTED]'
> Subject: STDIN and STDOUT on Windows
>
>
> Hello,
>
> I normally use perl on a unix platform, but I needed to
Hello,
I normally use perl on a unix platform, but I needed to run a quick utility
on a Windows PC. Normal stdin and stdout doesn't seem to work, take this
simple program:
#
use warnings;
use strict;
while (<>) {
print;
}
On Windows, if I run:
type test.txt | te
--- Michael Fowler <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 10, 2001 at 10:28:14AM -0700, Paul wrote:
> >
> > --- Paul <[EMAIL PROTECTED]> wrote:
> > >
> > > --- Bob Mangold <[EMAIL PROTECTED]> wrote:
> > > > exec(' myperl.pl 2>&1 ' ) ?
> > > >
> > > > ok, this works, but what the heck is it do
On Tue, Jul 10, 2001 at 10:28:14AM -0700, Paul wrote:
>
> --- Paul <[EMAIL PROTECTED]> wrote:
> >
> > --- Bob Mangold <[EMAIL PROTECTED]> wrote:
> > > exec(' myperl.pl 2>&1 ' ) ?
> > >
> > > ok, this works, but what the heck is it doing. i've never seen that
> > > syntax.
> >
> > lol -- it's no
--- Paul <[EMAIL PROTECTED]> wrote:
>
> --- Bob Mangold <[EMAIL PROTECTED]> wrote:
> > As mentioned eariler...
> >
> > --- Craig Moynes/Markham/IBM <[EMAIL PROTECTED]> wrote:
> > You mentioned in the earlier email that you were calling your perl
> > script
> > via 'exec' (as I remember).
> > Co
--- Bob Mangold <[EMAIL PROTECTED]> wrote:
> As mentioned eariler...
>
> --- Craig Moynes/Markham/IBM <[EMAIL PROTECTED]> wrote:
> You mentioned in the earlier email that you were calling your perl
> script
> via 'exec' (as I remember).
> Could you not use something like
> exec(' myperl.pl 2>&1
As mentioned eariler...
--- Craig Moynes/Markham/IBM <[EMAIL PROTECTED]> wrote:
You mentioned in the earlier email that you were calling your perl script
via 'exec' (as I remember).
Could you not use something like
exec(' myperl.pl 2>&1 ' ) ?
ok, this works, but what the heck is it doing. i've
--- Bob Mangold <[EMAIL PROTECTED]> wrote:
> > Are you sure it's STDERR? Some write directly to ther terminal
> > screen...
>
> I checked through the module code and it definitely says 'print
> STDERR ...'.
Well, unless they've done some shinanigans further up the code, that's
pretty conclusive
> Are you sure it's STDERR? Some write directly to ther terminal
> screen...
>
I checked through the module code and it definitely says 'print STDERR ...'.
> What is this module?
The module is 'bioperl' (used for genetic analysis).
__
Do You Ya
--- Bob Mangold <[EMAIL PROTECTED]> wrote:
> > Does anybody know why he shouldn't do the following?
> >
> > *STDERR = *STDOUT;
> >
>
> This is what I orignally tried, and is didn't really work. I think my
> problem lies in the fact that I am hoping to make the change in a
> module that I am 'u
> Does anybody know why he shouldn't do the following?
>
> *STDERR = *STDOUT;
>
This is what I orignally tried, and is didn't really work. I think my problem
lies in the fact that I am hoping to make the change in a module that I am
'use'ing. So I tried all of the suggestions, but it seemed tha
--- Bob Mangold <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I sent an email yesterday, but never heard anything. Maybe it was the
> word 'php' in the subject, but let me just simplify and ask another
> way.
>
> Is there a way to automatically direct all STDERR output to STDOUT. A
> module I have in
On 10 Jul 2001 04:45:56 -0700, Bob Mangold wrote:
> Hello,
>
> I sent an email yesterday, but never heard anything. Maybe it was the word
> 'php' in the subject, but let me just simplify and ask another way.
>
> Is there a way to automatically direct all STDERR output to STDOUT. A module I
> hav
>Hello,
>I sent an email yesterday, but never heard anything. Maybe it was the word
>'php' in the subject, but let me just simplify and ask another way.
>Is there a way to automatically direct all STDERR output to STDOUT. A
module I
>have installed automatically creates STDERR output, but I want t
ge -
From: "Bob Mangold" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 7:45 AM
Subject: STDIN and STDOUT
> Hello,
>
> I sent an email yesterday, but never heard anything. Maybe it was the word
> 'php' in the subject, but let
e: Tue, 10 Jul 2001 04:45:56 -0700 (PDT)
Subject: STDIN and STDOUT
> Hello,
>
> I sent an email yesterday, but never heard anything. Maybe it was the
> word
> 'php' in the subject, but let me just simplify and ask another way.
>
> Is there a way to automaticall
e: Tue, 10 Jul 2001 04:45:56 -0700 (PDT)
Subject: STDIN and STDOUT
> Hello,
>
> I sent an email yesterday, but never heard anything. Maybe it was the
> word
> 'php' in the subject, but let me just simplify and ask another way.
>
> Is there a way to automaticall
Hello,
I sent an email yesterday, but never heard anything. Maybe it was the word
'php' in the subject, but let me just simplify and ask another way.
Is there a way to automatically direct all STDERR output to STDOUT. A module I
have installed automatically creates STDERR output, but I want that
20 matches
Mail list logo
