Using workflow variables in Run Script actions

[samuellinde]

I'm trying to get workflows variables to parse in a Run Script action. I.e I want to run "/usr/local/bin/tag -a {var:tag} {var:files}" but the script parser tries to replace the colon with a forward slash.

 

Edit: Found out the answer myself (which was indeed fairly logical when you think about it). When using the recommended "with input as argv" setting, I could access the variables with $tag and $files. :-)

Edited May 26, 2016 by samuellinde

[Andrew]

I'm trying to get workflows variables to parse in a Run Script action. I.e I want to run "/usr/local/bin/tag -a {var:tag} {var:files}" but the script parser tries to replace the colon with a forward slash.

 

 

Workflow variables are set as environment variables within scripts, so you can access them directly regardless of the script mode ({query}, argv, external).

 

Cheers,

Andrew

[FroZen_X]

Workflow variables are set as environment variables within scripts, so you can access them directly regardless of the script mode ({query}, argv, external).

 

Cheers,

Andrew

 

Just out of curiosity Andrew. As we talked about the Problem on twitter, that this doesn't work in applescript, do you think you can make it work at some point?

Right now my workaround is to combine vars via delimiter like here:

{var:filename}:{query}

And then i split it via applescript like this:

set x to "{query}"
set text item delimiters to {":"}
set {filename, destination} to text items 1 thru 2 of x

[Andrew]

 

Just out of curiosity Andrew. As we talked about the Problem on twitter, that this doesn't work in applescript, do you think you can make it work at some point?

Right now my workaround is to combine vars via delimiter like here:

{var:filename}:{query}

And then i split it via applescript like this:

set x to "{query}"
set text item delimiters to {":"}
set {filename, destination} to text items 1 thru 2 of x

 

 

I've been trying to work out why osascript doesn't respect the passed in environment through NSTask like the others do, it seems to be a bug with osascript, but I'll keep working at it!