We have a simple bash script I wrote to use with the execute command inside of Switch for doing some simple imposing work before sending the job off to a hot folder for our Fiery's. The Bash Script I'm betting I can get it working with more effort, but I'm hoping someone may have a solution or at least a clarification on why it is not working now.
The Shell Script runs as expected, and moves any test file along the flow (just not modified), but in the log for stderr, I have:
Code: Select all
stderr: /Users/ed1prepress2/Documents/Switch_Impose/PdfJam_Impose.bash: line 271: pdfjam: command not found
The command does execute fine if I give it arguments manually in the shell (Outside of Switch), so I know it isn't a simple coding error.
I suspect it has something to do with how the execute command function works, as the user guide indicated :
The "pdfjam" command is a set of shell scripts itself, so I'm wondering if this has to do with the aliases the shell handles automatically, while the execute command does not know where exactly it is located.Switch will execute the command directly in the operating system while Command Prompt and Terminal use a shell. This results in some differences in behavior, the most important one being that you always have to provide the full path to the command line application in Switch, even when this is not necessary in Command Prompt or Terminal!
Any thoughts or suggestions would be appreciated.
Thanks,
Nathan