http://www.perlmonks.org?node_id=972863


in reply to Re^3: Activating a screen saver problems
in thread Activating a screen saver problems

I understood what you meant by "screensaver directory",
I just don't understand why simply giving the entire path isn't good enough (why must be "in" the directory).
But experimenting did show it's necessary to do it your way.
Probably the '/s' part is wrongly interpreted as a directory deepening, do to the other / or \ in the path string.

I'm guessing #!/usr/bin/perl -w is like "use warnings", I'll read about it later ^^.

Thx again
  • Comment on Re^4: Activating a screen saver problems

Replies are listed 'Best First'.
Re^5: Activating a screen saver problems
by golux (Chaplain) on May 29, 2012 at 03:37 UTC
    Hi palkia,

    Sorry if I was confusing; I didn't mean you had to be in the directory. I just did it that way myself because I was lazy, and wanted to experiment with running the screensaver in a command ("cmd") window (so I only had to type the screensaver name, not the full path). But giving the full path is fine, and doesn't seem to conflict with the /s switch when I do it this way (note the space before the /s switch): 

    use strict;
use warnings;
system('C:/winnt/system32/sspipes.scr /s');

    [download]

    And yes, the "-w" part of the "shebang" line, as it's called, is for warnings (again, look at perllexwarn). The rest of the first line is more germane to Linux systems, where it specifies the path (ie. directory) where Perl is located (ie. "/usr/bin/perl"). But on Windows you can safely remove the entire first line, and the script should still run.

    say  substr+lc crypt(qw $i3 SI$),4,5
[reply]
[d/l]
[select]
      Got it.
      You are absolutely right, by adding the space before the /s,
      I'm no longer forced be in the directory itself, and can use the entire path instead.

      Thank you very much for taking the time to detail about such small things with large impact.
      Most appreciated.
[reply]

In Section Seekers of Perl Wisdom