perl interpreter automatically exit windows so how I can saw the result of script?

A

Alont

in my WINDOWS XP, I can open *.pl file and perl interpreter
automatically start and execute *.pl file but it automatically exit
too, so I can't saw the result of script, how to set perl interpreter
stay on the command line?
the guide haven't tell me the answer:
Win95/NT
The Win95/NT installation, when using the ActiveState installer for
Perl, will modify the Registry to associate the .pl extension with the
perl interpreter. If you install Perl by other means (including
building from the sources), you may have to modify the Registry
yourself. Note that this means you can no longer tell the difference
between an executable Perl program and a Perl library file.

Your fault as a Government is My failure as a citizen
 
P

Paul Lalli

in my WINDOWS XP, I can open *.pl file and perl interpreter
automatically start and execute *.pl file but it automatically exit
too, so I can't saw the result of script, how to set perl interpreter
stay on the command line?
the guide haven't tell me the answer:
Win95/NT
The Win95/NT installation, when using the ActiveState installer for
Perl, will modify the Registry to associate the .pl extension with the
perl interpreter. If you install Perl by other means (including
building from the sources), you may have to modify the Registry
yourself. Note that this means you can no longer tell the difference
between an executable Perl program and a Perl library file.


Maybe, just maybe, you should wait a few minutes before asking the same
question again. Usenet is not instantaneous. This question has been
answered, with a couple different answers, in the original thread.

Paul Lalli
 
S

Shawn Corey

Try adding this to your script:

END{<STDIN>}

This way the results don't disappear until you press ENTER.
 
G

Gibbering Poster

Alont said:
in my WINDOWS XP, I can open *.pl file and perl interpreter
automatically start and execute *.pl file but it automatically exit
too, so I can't saw the result of script, how to set perl interpreter
stay on the command line?

You could always put '<>' at the end of your script...
 
G

Greg Bacon

: Try adding this to your script:
:
: END{<STDIN>}
:
: This way the results don't disappear until you press ENTER.

I like to use something similar to the following:

END { system "pause" unless $ENV{PROMPT} }

That way, I don't see the pause in a command window.

I'd like to know of a workaround that would cause the window to
linger when there are syntax errors, a use fails, etc.

Greg
 
J

Jeff 'japhy' Pinyan

I like to use something similar to the following:

END { system "pause" unless $ENV{PROMPT} }

That way, I don't see the pause in a command window.

I'd like to know of a workaround that would cause the window to
linger when there are syntax errors, a use fails, etc.

Easy: make that END { ... } the first line of your code.

--
Jeff "japhy" Pinyan % How can we ever be the sold short or
RPI Acacia Brother #734 % the cheated, we who for every service
RPI Corporation Secretary % have long ago been overpaid?
http://japhy.perlmonk.org/ %
http://www.perlmonks.org/ % -- Meister Eckhart
 
A

A. Sinan Unur

Alont said:
in my WINDOWS XP, I can open *.pl file and perl interpreter
automatically start and execute *.pl file but it automatically exit
too, so I can't saw the result of script, how to set perl interpreter
stay on the command line?
the guide haven't tell me the answer:

Learn how to use Windows XP, why don't you?

Download the "Command Prompt Here" powertoy from Microsoft (google for it).
Then, you can open a cmd shell window anywhere you want in explorer. Run
you Perl scripts from the command line instead of double clicking on them
unless the scripts are designed to interact with you using a GUI. This goes
for all programs, not just for Perl scripts.
 
J

John Bokma

Learn how to use Windows XP, why don't you?

Download the "Command Prompt Here" powertoy from Microsoft (google for
it). Then, you can open a cmd shell window anywhere you want in
explorer. Run you Perl scripts from the command line instead of double
clicking on them unless the scripts are designed to interact with you
using a GUI.

Or just run and do their work and no interacting nor reporting is required.
 
A

Alont

I'm sorry, really sorry, I'll never do that again :)

at Thu, 19 Aug 2004 13:10:24 -0400
Paul Lalli said:
Maybe, just maybe, you should wait a few minutes before asking the same
question again. Usenet is not instantaneous. This question has been
answered, with a couple different answers, in the original thread.


Your fault as a Government is My failure as a citizen
 
A

Alont

good idea, thank you :)

at Thu, 19 Aug 2004 13:32:59 -0400
Shawn Corey said:
Try adding this to your script:

END{<STDIN>}

This way the results don't disappear until you press ENTER.


Your fault as a Government is My failure as a citizen
 
A

Alont

in fact, before forward friend tell me how to stay on command line
through a perl sentence, I know "Run your Perl scripts from the
command line instead of double clicking on them", but I'm a lazy man,
I want "double clicking" If I don't have to stroking in the command
line again and again....
to use Windows or other tools have different way, I just want find a
way suit me.

at 19 Aug 2004 19:21:41 GMT
A. Sinan Unur said:
Learn how to use Windows XP, why don't you?

Download the "Command Prompt Here" powertoy from Microsoft (google for it).
Then, you can open a cmd shell window anywhere you want in explorer. Run
you Perl scripts from the command line instead of double clicking on them
unless the scripts are designed to interact with you using a GUI. This goes
for all programs, not just for Perl scripts.


Your fault as a Government is My failure as a citizen
 
S

Sherm Pendley

Alont said:
I want "double clicking" If I don't have to stroking in the command
line again and again....

A long time ago, in a galaxy far, far away, Windows command.com had a
"history" feature. Pressing F3 would bring up the previous command so
you could repeat it without having to re-type it.

I don't know if it still works though. Windows and I parted company some
years ago.

sherm--
 
A

A. Sinan Unur

A long time ago, in a galaxy far, far away, Windows command.com had a
"history" feature. Pressing F3 would bring up the previous command so
you could repeat it without having to re-type it.

I don't know if it still works though. Windows and I parted company
some years ago.

Actually, that still exists. However, cmd.exe has a reasonable history
buffer (like doskey, but you don't actually have to load it) and also has
directory and file name completion. Microsoft's "Command Prompt Here"
utility adds the ability to right click on any directory in explorer and
open a cmd.exe shell in that directory (helps those who have not moved
their home directory from the default

c:\Documents and Settings\user id\My Documents

to a more reasonable place such as C:\Home\user (Microsoft's TweakUI
utility makes it easy to change the location of such 'special'
directories).
 
A

A. Sinan Unur

[ Please stop top-posting ]

in fact, before forward friend tell me how to stay on command line
through a perl sentence, I know "Run your Perl scripts from the
command line instead of double clicking on them", but I'm a lazy man,
I want "double clicking" If I don't have to stroking in the command
line again and again.... to use Windows or other tools have different
way, I just want find a way suit me.

Well, changing all your scripts to pause at completion is far more work
than using the command line.
 
A

Alont

really! I found the cmd.exe can store keystroking, just use "top
arrow" key to call back,

at Thu, 19 Aug 2004 23:50:22 -0600
 
A

Abhinav

Alont said:
how to set Forte Agent automatically move cursor to the bottom?

1. Check out the FAQs for Forte

2. Before you ask where they will be, google for them. In the highly
unlikely scenario that you cannot find them , google the group
news.software.readers.

3. If you still cannot find it (and even if you can) please hold down the
Control Key and press (and release) the "End" Key to go the the bottom of
the post.

4. Please see the sig (courtesy CBFalconer) for more details as to why I am
suggesting the above. :)

HTH

Abhinav
 
A

Alont

Abhinav said:
1. Check out the FAQs for Forte

there's impossible to solve this problem or I change My client
program. maybe Forte Agent isn't the best reader, I'll try other one
 
C

Chris Cole

there's impossible to solve this problem or I change My client
program. maybe Forte Agent isn't the best reader, I'll try other one

Did you actually try step 2? The 3rd hit in google gave this link:
http://www.faqs.org/faqs/off-line-readers/usenet/forte-agent/

This also shows that there is a newsgroup dedicated to Forte. Try asking
them.

You really need to start working things out for yourself as people will
soon get tired of you not showing any initiative in trying solve problems
before bothering us about it.

[snip]
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,484
Members
44,903
Latest member
orderPeak8CBDGummies

Latest Threads

Top