geeky Perl plea

[metawidget]

Help!

I'm trying to get a Perl script wrapped in Platypus to set its working directory to the current one... it has an example using "$1/.." for sh, but I'm a total novice and don't know how to get perl to either do that right away or fold it into a system() call. I just want the script to run a command from the directory it's sitting in (I can't predict what directory the user will drop it in, but the files the command acts on will be in the right relative spots).

If anyone has an idea how to access what Platypus gives to sh as "$1" from Perl, or another way to do this, I'd be much obliged.

Comments

[pphaneuf.livejournal.com]

The command-line parameters are given in @ARGV, so $1 would be available as $ARGV[0].

[metawidget]

Thanks!

That was it, exactly. You've saved me untold hours of trying to figure out a mapping between two languages I only kind of know.

One meta point for you!

[http://users.livejournal.com/hub_/]

I must admit I have hard time to understand what you want to do.

$1 in Perl is the Regexp back reference from the previous match (can be undefined)

$1 in Shell is the first argument passed to the shell script.

[metawidget]

I needed to know the second fact (that $1 in shell is an argument) plus what the equivalent statement was in perl... I had an example of how to see where the Platypus wrapper was sitting for shell and a script I wanted to wrap in perl.

I now know why $1 resolved to empty space in perl in my case, thanks!

[swestrup]

Took a look at the Platypus site, but its not very informative. Give an example of a piece of perl code that's called from Platypus and we can probably deduce how the interface works.

[metawidget]

The lack of example was my problem (they had drag-and-drop perl examples, but none of the "do stuff nearby" type)... but I think I have a handle on it now.

You're right, the documentation suffered from a cookbook approach where a "Platypus sends this in the first argument" might've been vaguer but more useful.